pleroma-fe issueshttps://git.pleroma.social/pleroma/pleroma-fe/-/issues2022-12-19T22:42:42Zhttps://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/1142Marking too many notifications as read takes obnoxious amount of time2023-04-03T20:22:06ZHJMarking too many notifications as read takes obnoxious amount of timeIf you had FE open for a while and you have like 100+ notifications, pressing "Read!" will hang the UI for couple seconds, most likely due to too many statuses being updated at same time, probably need to stagger updates by chunking themIf you had FE open for a while and you have like 100+ notifications, pressing "Read!" will hang the UI for couple seconds, most likely due to too many statuses being updated at same time, probably need to stagger updates by chunking themMentions/posts/notifications improvementshttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1141Improve "unknown" state for mentionlinks2023-04-03T20:21:51ZHJImprove "unknown" state for mentionlinksRight now mention links can be glitchy because of real-time update for users related to mention, we can mitigate this by deducing some information based on mention content alone and make it look like "known" with dummy data.
* Derive us...Right now mention links can be glitchy because of real-time update for users related to mention, we can mitigate this by deducing some information based on mention content alone and make it look like "known" with dummy data.
* Derive username from mention link content
* Derive hostname from mention link content or url
* Put a dummy avatar if user has that enabledMentions/posts/notifications improvementshttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1128New Feature: Show Posts in threads per default2023-04-03T20:28:14ZJakob SchürzNew Feature: Show Posts in threads per defaultI know, pleroma is a microblogging-plattform...
But is there a possibility to make a users-choice setting to show threads not single posts per default?
So a user can choose, if he wants to see discussion-thread or microblogging single ...I know, pleroma is a microblogging-plattform...
But is there a possibility to make a users-choice setting to show threads not single posts per default?
So a user can choose, if he wants to see discussion-thread or microblogging single messages.
Is it a big thing or just a lightweight implementation-job?Mentions/posts/notifications improvementshttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1127Option to replace new @ SVG with instance logo, tangent on post size bloat2023-04-03T20:27:42ZplebOption to replace new @ SVG with instance logo, tangent on post size bloatThe 2.4.2 Pleroma update brough the new SVG @ to the masses, and it does look neat.
An option to replace them with instance favicons would be even neater.
As an aside why are all svg's inlined?
It makes sense to save a http request for...The 2.4.2 Pleroma update brough the new SVG @ to the masses, and it does look neat.
An option to replace them with instance favicons would be even neater.
As an aside why are all svg's inlined?
It makes sense to save a http request for a one off side bar logos, but 1.2K next to every mention seems overly cache unfriendly, not to mention the 7 other SVG's for buttons on every post.
I get that gzip over the wire is cheap, but zip bombs are cheap to send too, exploding ram requirements.
The new update has feels uncomfortably sluggish for some reason, JS heap seems to balloon like no release before it browsing threads.Mentions/posts/notifications improvementshttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1119Try to follow the browser font-size2023-10-31T11:27:28ZHaelwennTry to follow the browser font-sizeCurrently PleromaFE font-size is harcoded to 14px, which can end up as big or small depending on people. (like it leans towards large for me and leans towards small for some others to maybe even too small).
I think it should follow the ...Currently PleromaFE font-size is harcoded to 14px, which can end up as big or small depending on people. (like it leans towards large for me and leans towards small for some others to maybe even too small).
I think it should follow the browser font-size, similarly to how it mostly follows the browser font-family.
Might also be neat to add font-sizing to the fonts tab on themes (based on percentages/em so it's scaling on the browser-defaults?) so one could have things like text being smaller than the interface.Mobile experience improvementshttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1107add support for "poll ended" notfication type2023-04-03T20:26:12ZHJadd support for "poll ended" notfication typeexample:
```
{
"account": {...},
"created_at": "2021-08-18T14:03:54.000Z",
"id": "703382",
"pleroma": {
"is_muted": false,
"is_seen": false
},
"status": {...},
"type": "poll"
}
```example:
```
{
"account": {...},
"created_at": "2021-08-18T14:03:54.000Z",
"id": "703382",
"pleroma": {
"is_muted": false,
"is_seen": false
},
"status": {...},
"type": "poll"
}
```Mentions/posts/notifications improvementshttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1095Virtual scrolling doesn't handle situations with TONS of muted posts2023-04-03T20:25:07ZHJVirtual scrolling doesn't handle situations with TONS of muted postsExample:
![image](/uploads/9402751fa27cf8447f8b9b2c4f6639a7/image.png)
Same happens when posts are hidden completely (!1394).Example:
![image](/uploads/9402751fa27cf8447f8b9b2c4f6639a7/image.png)
Same happens when posts are hidden completely (!1394).Performance improvementshttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1093Accessibility of external post links degraded2023-04-03T20:24:47ZBradleyAccessibility of external post links degradedI recently learned that newer versions of Pleroma have moved the external post button to the menu instead of leaving it visible. I use this feature constantly and this seems like a strange decision. The fact that local versions of extern...I recently learned that newer versions of Pleroma have moved the external post button to the menu instead of leaving it visible. I use this feature constantly and this seems like a strange decision. The fact that local versions of external posts will be periodically deleted makes this button very important if you want to share links that won't be dead in a few months. You also can't open several quickly in a row when they're hidden in a menu. Not only is there an extra click required to make the button visible, but if you open a second menu, the first one will close. You can't have multiple external post buttons visible anymore. This was useful for something like qutebrowser's rapid hints mode where you can quickly open many visible links in new tabs. It was also easier to copy post links via link hints when the buttons were all visible.Mentions/posts/notifications improvementshttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1042Use serviceworksers to show notifications or support mobile chrome2023-10-31T11:26:44ZHJUse serviceworksers to show notifications or support mobile chromehttps://shigusegubu.club/notice/A3HOnOaN0TsgxBvqHA
supposedly mobile chrome doesn't work with `new Notification()` and forces you to use serviceworkers to do it.
Might as well implement is so that multiple tabs don't generate same noti...https://shigusegubu.club/notice/A3HOnOaN0TsgxBvqHA
supposedly mobile chrome doesn't work with `new Notification()` and forces you to use serviceworkers to do it.
Might as well implement is so that multiple tabs don't generate same notifications?Mobile experience improvementsHJHJhttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/965DRAFT: Settings sync implementation plan2023-04-03T20:08:30ZHJDRAFT: Settings sync implementation plan1. Prerequisites
* ~~**Add highlighting settings that are different from default**~~
* Add versioning and migrations of settings - lock down current version as v0, v1 should just add version number, v2 will add profiles with simp...1. Prerequisites
* ~~**Add highlighting settings that are different from default**~~
* Add versioning and migrations of settings - lock down current version as v0, v1 should just add version number, v2 will add profiles with simple migration turning current settings into a "default profile". All settings must be turned into a snapshot so that logged in users won't get unexpected behavior due to changed behavior.
* ~~Add save timestamp to settings (see above)~~
* Reset to default button to the top.
* Change the way anon settings work - don't save settings for anon users (i.e. not logged in), show dialog box if user change something in settings, something like "You changed some settings, do you want to save them?". Shouldn't affect logged in users.
2. Multiple profiles support - just complete separate profiles, no connection between them. Each session keeps track of which profile it uses.
3. Save/load to file
4. Settings sync basic
* Notification on top about settings sync landing
* Should try to fetch data from server, compare it to what's stored and if it's different - suggest making a new profile, overwriting existing one, using remote one or disabling the sync entirely. Nothing should be stored until user takes action, notification should reflect that there is a conflict to be resolved.
* Some barebones "show difference" UI should be implemented.
* ~~Sync could be disabled or enabled at any point, process should go as above~~
This should be sufficient for most basic usage, further improvements for advanced use could be done afterwards:
* ~~subprofiles that are partial profiles - override specific settings only, i.e. different themes on different machines or hiding attachments on some machines but not others.~~
# Update 17/10/2022
Currently we implemented sever-side settings that are automatically kept in sync and are using some sorts of Conflict-free replicated data types, those are completely separate from normal settings, and already used for stuff like pinned navigation items.
The idea would be to migrate most settings there, either completely (i.e. wordfilter) or hybrid-like (probably most other settings). Hybrid-like means that FE can still store its own local settings... locally, so that you could override your "common" settings on specific device/session.Settings UX improvementhttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/760Auto-retry post if network connection fails2023-04-03T20:52:09ZfeldAuto-retry post if network connection fails![image](/uploads/1b5d688386554e9d1db1b02381375601/image.png)
I seem to get this enough. I think it's from roaming WiFi/LTE and WiFi/Ethernet on my phone and macbook. We could do maybe 3 max attempts before displaying this error.![image](/uploads/1b5d688386554e9d1db1b02381375601/image.png)
I seem to get this enough. I think it's from roaming WiFi/LTE and WiFi/Ethernet on my phone and macbook. We could do maybe 3 max attempts before displaying this error.2.4.0https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1303Theme3: shoutbox is transparent2024-03-28T01:16:41ZtusooaTheme3: shoutbox is transparent<!--
please use one of the templates if applicable, otherwise - type out here
in free-form
-->
![image](/uploads/ee124f260d531f57c61a041e4e54e927/image.png)
![image](/uploads/60f81640a7b7b2ca3823abb89a0c6983/image.png)<!--
please use one of the templates if applicable, otherwise - type out here
in free-form
-->
![image](/uploads/ee124f260d531f57c61a041e4e54e927/image.png)
![image](/uploads/60f81640a7b7b2ca3823abb89a0c6983/image.png)https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1302Theme3: cannot preview theme2024-03-28T01:14:47ZtusooaTheme3: cannot preview theme<!--
please use one of the templates if applicable, otherwise - type out here
in free-form
-->
Switching from Pleroma Dark to Pleroma Light, and the preview does not update until you hit Save.<!--
please use one of the templates if applicable, otherwise - type out here
in free-form
-->
Switching from Pleroma Dark to Pleroma Light, and the preview does not update until you hit Save.https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1301Theme3: --badgeNeutral is not set2024-03-28T01:16:32ZtusooaTheme3: --badgeNeutral is not set<!--
please use one of the templates if applicable, otherwise - type out here
in free-form
-->
`badgeNeutral` is present in src/services/theme_data/theme2_keys.js and src/services/theme_data/pleromafe.js but `--badgeNeutral` variable i...<!--
please use one of the templates if applicable, otherwise - type out here
in free-form
-->
`badgeNeutral` is present in src/services/theme_data/theme2_keys.js and src/services/theme_data/pleromafe.js but `--badgeNeutral` variable is not set on body elementhttps://git.pleroma.social/pleroma/pleroma-fe/-/issues/1300admin "Limit search to local content" saving "false" as string and breaking s...2024-03-17T20:15:51Zlamplamp@owo69.meadmin "Limit search to local content" saving "false" as string and breaking searchhappening on 7ee55da4
reproduce:
1. set this to false: ![image](/uploads/3cf8a2ba09ddce59ad84a38ad0dc421f/image.png)
2. try to search
3. find no user and status results and CaseClauseError in server log because case matches `false` but ...happening on 7ee55da4
reproduce:
1. set this to false: ![image](/uploads/3cf8a2ba09ddce59ad84a38ad0dc421f/image.png)
2. try to search
3. find no user and status results and CaseClauseError in server log because case matches `false` but value is `"false"`
4. Re-set the value to false in admin-fe ![image](/uploads/2ea32c246316b309b51587aa4c34fc09/image.png)
5. search works normally
related: https://git.pleroma.social/pleroma/pleroma-support/-/issues/105https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1295Subject being a span with `font-style: italic` is against semantics and break...2024-02-19T01:20:05ZBlair NoctisSubject being a span with `font-style: italic` is against semantics and breaks East Asian charactersCurrently the post subject is represented as a `div.StatusBody > div.body > div.summary-wrapper > span.summary` that [has](https://git.pleroma.social/pleroma/pleroma-fe/-/blob/bdf46eca5ae73b0f12b755774cd901854c814522/src/components/statu...Currently the post subject is represented as a `div.StatusBody > div.body > div.summary-wrapper > span.summary` that [has](https://git.pleroma.social/pleroma/pleroma-fe/-/blob/bdf46eca5ae73b0f12b755774cd901854c814522/src/components/status_body/status_body.scss#L27)
```css
/* src/components/status_body/status_body.scss */
.StatudBody .summary {
font-style: italic;
}
```
Quote the [user guide](https://docs-develop.pleroma.social/frontend/user_guide/posting_reading_basic_functions/) (emphases mine):
> Subject line also known as CW (Content Warning) could be used as a **header to the post** and/or to warn others about contents of the post having something that might upset somebody or something among those lines. Several applications allow to hide post content leaving only subject line visible. **Using a subject line will not mark your images as sensitive**, you will have to do that explicitly (see above).
Another word for subject in this context is title or heading. In HTML that means `<h1>` to `<h6>`. The use of italics may be a historical inheritance when it acted solely as a content warning where italics are appropriate, I guess. Even in that sense I'd argue a heading is good enough.
It's also noteworthy that italics, often "mis"-called 斜体 (lit. slanted/sloped font) because of its sloped appearance, completely _ruins_ Chinese and other East Asian characters, due to the fact that, because of their complexity and construction and artistic principles, it's unacceptable to slant them, so quotes are traditionally expressed with another typeface or simply indented; and modern computer typesetting/rendering software, based on Latin scripts, have an italics -> oblique -> automated oblique system, where East Asian typefaces, with obviously no italics or oblique variants, are "automatically obliqued" and look terrible.
It's probably better to use a `<h2>` (considering multiple `<h1>`s is discouraged).https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1294don't make my screenreader cursor jump when I expand hidden content, e.g. con...2024-03-27T22:40:08ZPatryk Kdon't make my screenreader cursor jump when I expand hidden content, e.g. content warningscurrently, if I open up something with a content warning, my screenreader cursor jumps, and I need to scroll by headings back to the post or thread element, which is impossible when you want to read a whole thread.
-->currently, if I open up something with a content warning, my screenreader cursor jumps, and I need to scroll by headings back to the post or thread element, which is impossible when you want to read a whole thread.
-->https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1293Notification Blip for Shoutbox2024-02-19T01:18:56ZDeviant EyesNotification Blip for Shoutbox# Behavior suggestion/Feature request
Could we PLEASE add a notification dot to the shoutbox? I think it would actually get use if it had one. I never use it because I never know when there's activity on it. Having a notification dot ap...# Behavior suggestion/Feature request
Could we PLEASE add a notification dot to the shoutbox? I think it would actually get use if it had one. I never use it because I never know when there's activity on it. Having a notification dot appear on it would fix that.
![image 2.png](/uploads/8c917976742510bc48d84f26e79975ad/image_2.png) ![image.png](/uploads/58d91cb026cb3bc0150036b3dfdb919a/image.png)https://git.pleroma.social/pleroma/pleroma-fe/-/issues/1290Videos do not fit correctly on mobile Safari in modal view2024-02-19T01:18:47ZfeldVideos do not fit correctly on mobile Safari in modal view![image](/uploads/39519b971c8291ca93e31d2d9d42c1a7/image.png)
There are pixels at the top cut off and some native video player controls up there are missing as a result. The images are rendered correctly ~~as you can see it's resized t...![image](/uploads/39519b971c8291ca93e31d2d9d42c1a7/image.png)
There are pixels at the top cut off and some native video player controls up there are missing as a result. The images are rendered correctly ~~as you can see it's resized to fit below the [X] in the upper right~~ as seen here:
![A32410B0-F587-4201-B0A3-592EEB9A2857_1_102_o](/uploads/1592048a0abec5641c0b748b8cfa8b1d/A32410B0-F587-4201-B0A3-592EEB9A2857_1_102_o.jpeg)