pleroma-fe issueshttps://git.pleroma.social/pleroma/pleroma-fe/-/issues2023-04-03T00:26:17Zhttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1211New follow requests since upgrading not visible2023-04-03T00:26:17ZMoon ManNew follow requests since upgrading not visibletwo issues technically. I updated pleroma-fe to latest development. I clicked on follow requests. none were visible.
as of today, now they are visible. But only the ones prior to updating. I verified that there were new ones in the data...two issues technically. I updated pleroma-fe to latest development. I clicked on follow requests. none were visible.
as of today, now they are visible. But only the ones prior to updating. I verified that there were new ones in the database.
I still have an older version of development branch on a subdomain, it could always see the old pending requests but also could not see the new ones.
I can do whatever needed to facilitate debugging of this.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1210default nsfw cover image no longer works2023-04-03T20:04:46Ztusooadefault nsfw cover image no longer worksIt seems that the webpack5 migration changed the hash somehow. And if backend is bundled with develop fe (or is not bundled at all), the image will fail to show up. We should have an `import()` fallback in place instead.It seems that the webpack5 migration changed the hash somehow. And if backend is bundled with develop fe (or is not bundled at all), the image will fail to show up. We should have an `import()` fallback in place instead.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1205Migrate from Webpack to Vite?2022-09-26T17:09:32ZSean KingMigrate from Webpack to Vite?Aside from it being the [recommended build toolchain at the framework level for Vue 3](https://v3-migration.vuejs.org/recommendations.html#new-framework-level-recommendations), there is some legitimate reasons to use Vite over Webpack:
-...Aside from it being the [recommended build toolchain at the framework level for Vue 3](https://v3-migration.vuejs.org/recommendations.html#new-framework-level-recommendations), there is some legitimate reasons to use Vite over Webpack:
- It improves the development server startup time by:
- using esbuild to pre-bundle dependencies
- using native ESM to serve source code and perform hot module replacements
- Despite using Rollup instead of esbuild to bundle for production (for now), it has some good bundle optimizations such as code splitting and async chunk loading optimization
I tried using [the `webpack-to-vite` tool from OriginJS](https://originjs.org/en/guide/tools/webpack-to-vite/). And it didn't go as smoothly as expected. And I encountered a strange error with `src/i18n/messages.js` not being able to import `langCodeToJsonName` with an error starting with `SyntaxError: ambiguous indirect export:`.
There's some documentation out there I've found. But unfortunately, there's no tutorials on how to migrate from Webpack to Vite that I could understand. And Vue School only has an article on [migrating from Vue CLI to Vite](https://vueschool.io/articles/vuejs-tutorials/how-to-migrate-from-vue-cli-to-vite/). Because I think our case is so complex, we may need to look deeper and think about how to approach this properly if we are to do this.
**Edit:** From my research, the Vue CLI service is built on top of Webpack (the current version of it uses Webpack 5.54.0). Maybe I could try first migrating it to Vue CLI and then to Vite? I'll give this some thought. I honestly think we need to wait until after the 2.5 release to start looking into this further.
**Sources:**
- https://vitejs.dev/guide/why.html
- https://vitejs.dev/guide/features.html#build-optimizations
- https://v3.cli.vuejs.org/guide/#cli-servicehttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1204Have a link to `/phoenix/live_dashboard/`2022-09-16T11:59:01ZIljaHave a link to `/phoenix/live_dashboard/`Apparently we have a dashboard at `https://instance.tld/phoenix/live_dashboard/` which admins can access. It's not very discoverable. Maybe we can have an extra icon for it next to the admin-fe one. Should only be visible to admins ofc.Apparently we have a dashboard at `https://instance.tld/phoenix/live_dashboard/` which admins can access. It's not very discoverable. Maybe we can have an extra icon for it next to the admin-fe one. Should only be visible to admins ofc.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1202Migrate from Vuex to Pinia for store management?2023-04-04T20:47:15ZSean KingMigrate from Vuex to Pinia for store management?Vue3 is [recommending Pinia over Vuex for store management](https://v3-migration.vuejs.org/recommendations.html#state-management). Pinia is basically a defacto implementation of what had been planned for Vuex 5. And there is [quite some ...Vue3 is [recommending Pinia over Vuex for store management](https://v3-migration.vuejs.org/recommendations.html#state-management). Pinia is basically a defacto implementation of what had been planned for Vuex 5. And there is [quite some differences to note](https://pinia.vuejs.org/introduction.html#comparison-with-vuex-3-x-4-x) such as mutations no longer being a thing.
Thankfully, there is a [migration guide](https://pinia.vuejs.org/cookbook/migration-vuex.html). But like with migrating to Vue 3, I doubt this will be 100% easy.
**Note:** We will likely have to wait until [we really refactor our stores](https://git.pleroma.social/pleroma/pleroma-fe/-/issues/995#note_94783).https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1201Regression: Default theme shows for short while when loading2022-09-11T12:52:46ZIljaRegression: Default theme shows for short while when loadingWhen I load pleroma-fe (on ilja.space), I get the default pleroma theme for a short while. I noticed it on b2f51b7c. When reverting to b13d8f7e I don't have the issue.
![2022-09-11_07-10-14](/uploads/5bc704cf825262fbfbc23eb0a21e16f1/202...When I load pleroma-fe (on ilja.space), I get the default pleroma theme for a short while. I noticed it on b2f51b7c. When reverting to b13d8f7e I don't have the issue.
![2022-09-11_07-10-14](/uploads/5bc704cf825262fbfbc23eb0a21e16f1/2022-09-11_07-10-14.mp4)https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1200Image zoom persists across attachment "page changes"2023-04-03T20:11:03ZHélènepleroma-dev@helene.moeImage zoom persists across attachment "page changes"![firefox_2022-09-08_02-27-47](/uploads/900018d9d65c4c9ea2982ba6b85761f5/firefox_2022-09-08_02-27-47.mp4)![firefox_2022-09-08_02-27-47](/uploads/900018d9d65c4c9ea2982ba6b85761f5/firefox_2022-09-08_02-27-47.mp4)https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1199"Reply to" previews are sometimes detached or appear in wrong/unreadable spots2022-09-06T22:51:36ZHélènepleroma-dev@helene.moe"Reply to" previews are sometimes detached or appear in wrong/unreadable spotsSeems to mostly happen when Pleroma-FE got loaded recently, seems to disappear on some re-hover and then becomes impossible to reproduce again.
![image](/uploads/cb129b873622d758ddfd99ac85c67c83/image.png)Seems to mostly happen when Pleroma-FE got loaded recently, seems to disappear on some re-hover and then becomes impossible to reproduce again.
![image](/uploads/cb129b873622d758ddfd99ac85c67c83/image.png)https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1198Checkbox items in moderation menu have disappeared2022-12-19T22:42:42ZHélènepleroma-dev@helene.moeCheckbox items in moderation menu have disappeared| Pleroma-FE stable | Pleroma-FE develop |
| ------ | ------ |
| ![image](/uploads/1b4ab1b6fa732149dbdfdd08aabae156/image.png) | ![image](/uploads/d3ac1ed35fbf325533819d6d2f0c0414/image.png) || Pleroma-FE stable | Pleroma-FE develop |
| ------ | ------ |
| ![image](/uploads/1b4ab1b6fa732149dbdfdd08aabae156/image.png) | ![image](/uploads/d3ac1ed35fbf325533819d6d2f0c0414/image.png) |2.5.0https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1197Scrolling "too fast" makes it so that nothing renders instead of just the scr...2023-04-03T20:10:36ZHélènepleroma-dev@helene.moeScrolling "too fast" makes it so that nothing renders instead of just the scrolled column not renderinghttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1187Docs: Installing new/custom pleroma-fe lists old way2023-04-03T21:48:30ZIljaDocs: Installing new/custom pleroma-fe lists old waySee https://docs-develop.pleroma.social/frontend/HACKING/#replacing-your-instances-frontend-with-custom-fe-build
The problem with this way is that you'll overwrite files like your tos and other things you may have changed.
There's a fr...See https://docs-develop.pleroma.social/frontend/HACKING/#replacing-your-instances-frontend-with-custom-fe-build
The problem with this way is that you'll overwrite files like your tos and other things you may have changed.
There's a front-end management system now that can be used. See https://docs-develop.pleroma.social/backend/configuration/cheatsheet/#frontend-management
Pleroma will first fetch files from static_dir, then from the frontends folder, then from priv. That way you can safely drop in a new fe without overwriting files like tos. It's also possible to keep different fe's next to each other and easily switch between them (e.g. to test a feature for a while, but then you want to easily switch back later).
Docs should note this new way of installing fe'shttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1184Poor readability of the user card due to profile banner usage2023-04-03T20:13:43ZFristiPoor readability of the user card due to profile banner usageMirrored from https://akkoma.dev/AkkomaGang/pleroma-fe/issues/128
---
One of the things that has always irked me about pleroma-fe, is how the profile banner is used as a background for the whole user card. This can cause problems with ...Mirrored from https://akkoma.dev/AkkomaGang/pleroma-fe/issues/128
---
One of the things that has always irked me about pleroma-fe, is how the profile banner is used as a background for the whole user card. This can cause problems with readability of the user bio, depending on the combination of image and theme used.
Take my own profile for example:
![on a dark theme](https://cdn.subcon.town/files/dark.png)
![on a light theme](https://cdn.subcon.town/files/light.png)
Especially on the light theme, the username and handle are poorly readable due to the combination of the image and black text. It's somewhat better with the dark theme, though not great either. The problem only gets worse once you start considering themes with lower contrasts.
I would suggest changing the user card so that the profile banner is actually used as a banner, like in other microblogs like mastodon and misskey. This will also make it easier for a user to get their profile to look more consistent across the different microblogs.
On a side note, if we're to redesign the user card, we might also take into account making it look better in notifications, since it currently is just a squashed mess:
![User card in notifications](https://cdn.subcon.town/files/notif.png)
I'm currently working on a little something to move some of the buttons into the top-right menu to free up more space, but I think this could also be far more condensed if the user card as a whole got a little redesign.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1181undesired jump-to-top behavior2023-04-03T00:32:52ZNaia Ōkamiundesired jump-to-top behaviorissue is detailed here:
https://www.youtube.com/watch?v=x925Qi0w0uI&feature=youtu.beissue is detailed here:
https://www.youtube.com/watch?v=x925Qi0w0uI&feature=youtu.behttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1169Configurable? notification expiry time2023-04-03T00:33:46ZAmolithConfigurable? notification expiry timeOne of my biggest annoyances with PleromaFE is that desktop notifications ignore my notification daemon's default expiry time and disappear after only a couple seconds.
I prefer to dismiss notifications manually because I like to finish...One of my biggest annoyances with PleromaFE is that desktop notifications ignore my notification daemon's default expiry time and disappear after only a couple seconds.
I prefer to dismiss notifications manually because I like to finish what I'm doing before shifting my attention to the notification; by the time I've finished what I'm focused on, I usually only have time to read a couple words which means I need to go back to my browser and find the tab to finish reading it, rather than just reading the notification itself.
It would be nice if the expiry time was configurable with an option to disable expiry, but I would also be satisfied with just an option to disable the expiry and defer dismissal to the OS.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1163Settings modal loads very slowly2023-04-03T20:16:36ZtusooaSettings modal loads very slowlyCurrently, backend-related settings are burst-fetched when the user opens the settings modal.
![A burst of GET requests](/uploads/a2a159d82de37622233be6906e900168/Screenshot_20220508_225726.png)
It contains at least:
- styles.json
- ...Currently, backend-related settings are burst-fetched when the user opens the settings modal.
![A burst of GET requests](/uploads/a2a159d82de37622233be6906e900168/Screenshot_20220508_225726.png)
It contains at least:
- styles.json
- all predefined themes in it
- domain blocks
- mfa
- user blocks/mutes
- the avatars of the users in the lists
I think they should be fetched only when we switched to that tab, at least.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1155Relationship not displayed when clicking a mention link to navigate to user page2023-04-03T20:16:59ZtusooaRelationship not displayed when clicking a mention link to navigate to user pageIf you click on a mention link of a user without having expanding their user card, and the page has not loaded any posts by that user, going to the user page will not correctly display the relationship with that user. It is left in a dan...If you click on a mention link of a user without having expanding their user card, and the page has not loaded any posts by that user, going to the user page will not correctly display the relationship with that user. It is left in a dangling state.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1152addNewStatuses efficiency2023-04-03T20:21:18ZtusooaaddNewStatuses efficiencyhttps://git.pleroma.social/pleroma/pleroma-fe/-/blob/develop/src/modules/statuses.js#L156
this function calls `sortTimeline(timelineObject)` which contains a simple sort. I am skeptical about the efficiency of this. could we maybe bench...https://git.pleroma.social/pleroma/pleroma-fe/-/blob/develop/src/modules/statuses.js#L156
this function calls `sortTimeline(timelineObject)` which contains a simple sort. I am skeptical about the efficiency of this. could we maybe benchmark this?
see also https://stackoverflow.com/questions/1344500/efficient-way-to-insert-a-number-into-a-sorted-array-of-numbershttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1149Shoutbox would not reconnect automatically after internet connection drops2023-04-03T20:15:07ZtusooaShoutbox would not reconnect automatically after internet connection drops0. Open pleroma-fe
1. Network drops (e.g. disconnect from inet or device put to sleep)
2. Wait
3. Reconnect internet
The shoutbox would not reconnect automatically after 3.0. Open pleroma-fe
1. Network drops (e.g. disconnect from inet or device put to sleep)
2. Wait
3. Reconnect internet
The shoutbox would not reconnect automatically after 3.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1148spinners aren't animated2023-04-03T20:13:15ZHJspinners aren't animatedcaused by fontawesome updatecaused by fontawesome updatehttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1145admin dashboard2023-05-08T21:59:23Ztusooaadmin dashboardBased on last week's meeting, we want to finally port admin-fe stuff to pleroma-fe.
removed "soapbox-fe-like" because obviously we can do much more than thatBased on last week's meeting, we want to finally port admin-fe stuff to pleroma-fe.
removed "soapbox-fe-like" because obviously we can do much more than that