Cocoa (
momijizukamori) wrote in
dw_beta2022-09-08 05:30 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Inbox Redesign
This post is for feedback for the redesigned inbox! As this is a redesign rather than a port, 'it's different' isn't useful feedback - please let me know how that difference is impacting you!
In particular, I'd like feedback from phone/tablet users, and from people who regularly get inbox messages in languages that use different character sets than English (languages that use Cyrillic, various East Asian languages, etc) - a lot of the elements of the redesign were meant to address problems with these.
EDIT: A proposal for alternate button interaction, to cut down on the number of action buttons for people with JS on (no-JS would still get a slightly cluttered view):
In particular, I'd like feedback from phone/tablet users, and from people who regularly get inbox messages in languages that use different character sets than English (languages that use Cyrillic, various East Asian languages, etc) - a lot of the elements of the redesign were meant to address problems with these.
Fixed Issues
- 'Unread' message filter missing from the navigation sidebar
- All entries are showing up collapsed, even unread ones.
- Odd word-breaking behavior in subjects and messages
- Action/navigation buttons are no longer in the footer as well
- Spacing between subject and timestamp
- Have to click on the checkbox rather than anywhere on the message to select it
- Expand/collapse does not work on read messages
- 'Delete all for this entry'/'Mark all read for this entry' does not work
- Selected messages aren't highlighted
- Intermittant weirdness/failures when using the in-message comment moderation tools
- The bottom message on one page is duplicated at the top of the next page
- Clicking a link in a message also causes that message to get marked as selected.
- Missing link to the beta comm in the header
- No confirmation dialogue for 'Delete All'
- Deleting messages via JS causes expanded/collapsed status to reset on other messages on the page.
- Current page button color is incorrect in all site schemes
- Not enough space between compose button and manage/refresh links
- Following reply link does not mark message as read
- Actions doesn't work with JS off
- Links in read messages aren't muted in color
- Images embedded in inbox notifications overflow badly
Fixed But Not Live
Known Issues
- Navigation buttons reflow in a kind of ugly way on some screen sizes
- Not enough space between action buttons
- Mark All Read button doesn't update text on press
- No warning when you've hit the max number of flagged messages (just silent failure)
- Left-clicking on message actions is slow and does not always correctly redirect.
Possible Tweaks
- Separate filters for comments and entries
- Wording for buttons
EDIT: A proposal for alternate button interaction, to cut down on the number of action buttons for people with JS on (no-JS would still get a slightly cluttered view):
- if nothing is selected, the two buttons are 'Mark All Read' and 'Delete All'
- if anything is selected, 'Delete All' becomes 'Delete Selected'
- if anything selected is read, 'Mark All Read' becomes 'Mark Read' (or possibly 'Mark Selected Read') - a mix of read and unread marked would get this
- if all selected are read, 'Mark All Read' becomes 'Mark Unread' (or 'Mark Selected Unread'
no subject
Oooh I bet something is going wrong the the JS, and you're getting dumped into the non-JS workflow instead.
(I assume you have JS enabled, at least, if you weren't having this before - though if you do selective script-blocking, the JS file in a different path now)
I'll see if I can reproduce!
no subject
no subject
Oh! JS = Javascript. If you don't know if you've done anything with it, you almost certainly haven't, so this is most likely a bug on our end that I'll have to do some digging into.
no subject
no subject
no subject
no subject
But I'll keep you posted. At least I'm not getting 502 error messages at this point -- I had a mess of those earlier today.
I probably should have mentioned also that I have an open support ticket, #46454.
no subject
Oh, the page change info is good to know! That could be it - I'll investigate some more.
Hopefully Mark's tweaks earlier will keep the 502s away.
no subject