60

The feedback up until January 3rd, 2023 has been catalogued and handed over to the product team. Any further feedback or bug reports should be posted as a new question.


TL;DR: The inbox improvements we previously announced are now live (as of November 29th, 2022 13:30 UTC).


Thank you to our beta testers!

A huge thank you to moderators who helped us beta-test these inbox changes! Your feedback was invaluable, and we could not be here without you.

New features

This post will provide a short overview of the new features, focusing especially on a few special cases not covered in the previous post. The changes will be rolled out to all sites, unless mentioned otherwise in the feature list below.

We will post an update here when the changes will be released.

  • Marking notifications as read/unread:

    • On all Stack Exchange top bars, except for the ones on Area 51 and the chat sites, the inbox dropdown will support individually marking messages as read/unread (or marking them all read at once), without needing to open the notification in a new tab/window.
    • Opening up the inbox will no longer automatically mark all messages as being read.
    • Note: opening the inbox in chat will automatically mark all messages as being read until the changes will be applied there.
  • Filtering to only show unread messages: All Stack Exchange pages, except for the inbox that is on the chat rooms listing, Area 51 pages, and stackexchange.com, will support filtering to only show unread messages in the inbox.

  • New design: On all Stack Exchange pages, except for the inbox that is on the chat rooms listing and Area 51 pages, the inbox will have a new design, updated to accommodate new buttons and improve readability.

  • Real-time inbox refreshing:

    • All Stack Exchange pages, except for the inbox that is on the chat rooms listing, Area 51 pages, and stackexchange.com, will support real time refreshing of the inbox content.
    • If a new notification arrived while the inbox was opened, the user will have an option to refresh its content manually with a refresh button.
    • We avoid an immediate refresh not to disturb the users while they work on their notifications. This option is also available while working with multiple tabs open at the same time.
  • Unread messages in the global inbox: The global inbox page will now highlight the unread items. It is also possible to mark the notifications as read by opening them in the global inbox.

Inbox popup overview

FAQ

Are you planning to bring these inbox improvements to chat as well?

Yes, we plan to update the inbox on all Stack Exchange pages (including chat) to the new style. While 100% compatibility on all sites will be hard to achieve, disabling the new functionality on chat pages is just a temporary solution.

Can I keep the current inbox functionality?

No. However, depending on the feedback, we may introduce the option to keep the current behavior of marking all notifications as read when the inbox is opened. If you want us to implement this as an option, please let us know!

Is this the final version of the inbox?

No, this is our first inbox-related release. We have a backlog of inbox-related issues that we gathered during both internal and beta testing. We plan to incrementally improve the MVP after the public release of the feature, based on the community feedback and product needs.

How should we share feedback on these changes?

If you have any questions, suggestions, or other feedback regarding the inbox improvements we've described here, please post it in an answer below. We'll be gathering feedback until the end of December 2022, after which we ask you to share any bug reports/feature requests by posting a separate question.

9
  • 14
    I'd like to remind folks of our request to post your feedback and questions in answers below. In order to keep things organized, comments that should be answers will be removed from time to time. Nov 28, 2022 at 13:54
  • 1
    In case anyone's wondering why all but two answers have not been responded to by staff since early December, the team is currently focusing on the Staging Ground release. Dec 29, 2022 at 10:25
  • 2
    Since this is a large thread, if you are thinking of posting something and have not read existing posts to see if a similar post has already been made, you can try searching them using the search bar with "inquestion:384148 is:answer ...".
    – starball
    Dec 30, 2022 at 19:03
  • 2
    I've gone through and catalogued all the feedback on this post already for the product team; we'll be going through it and prioritizing it to address in the next week or two. Any additional feedback on the inbox (bug reports/feature requests) should be posted as a separate post instead.
    – V2Blast
    Jan 3, 2023 at 5:57
  • @V2Blast have this been forgotten? There is no activity for two months. (usually the devs put status tags as edits to the bug reports or features in the answers.) Mar 5, 2023 at 8:28
  • 1
    @ShadowWizardChasingStars: Not forgotten, just sort of put on hold for a bit. The devs working on this have been busy lately kicking off Staging Ground beta 2. Once the dust has settled a bit, they should have more time to dedicate to going through the bugs and feature requests from this thread (which we're already tracking internally).
    – V2Blast
    Mar 8, 2023 at 20:27
  • @V2Blast thanks, I'll ask again in three months. Mar 9, 2023 at 7:14
  • @V2Blast maybe lock the question, if additional feedback should be posted elsewhere?
    – M--
    Jun 29, 2023 at 15:31
  • You might want to upvote the post that proposed 12 years ago the possibility to mark notifications as unread: Enable marking a response as "unread"
    – root
    Jul 5, 2023 at 23:19

51 Answers 51

77

However, depending on the feedback, we may introduce the option to keep the current behavior of marking all notifications as read when the inbox is opened. If you want us to implement this as an option, please let us know!

I already kinda did, but I don't mind letting you know again. So yes, please give me the option to mark all as read by just opening the inbox. If I really want to keep something and be annoyed by the indicator, I can then manually mark something as unread.

15
  • 26
    if it's a toggle, they'll just disable it in a few years because only 13k people used it
    – Kevin B
    Nov 28, 2022 at 19:40
  • 2
    Is the one extra click now required to do this really too much? i.stack.imgur.com/lTQzi.png There isn't really a way for them to allow setting individual items as unread if every time you open the inbox it sets everything to read automatically.
    – TylerH
    Nov 29, 2022 at 15:42
  • 16
    @TylerH “Double-click” vs. “click, move mouse, click, move mouse, click” is a rather significant increase in the amount of interaction. 95% of the time when I want this, it’s because I’ve already seen the comment because I was already on the relevant page, so I just double-click. I would absolutely turn this on if available.
    – KRyan
    Nov 29, 2022 at 16:14
  • Would be nice if it was some form of checkbox/toggle next to the mark all as read rather than a profile settings thing
    – Kevin B
    Nov 29, 2022 at 16:57
  • 1
    @TylerH even if everything is marked read by using the "mark all as read" button now, you can still mark individual items as unread again. So I'm not entirely getting what you mean by "There isn't really a way for them to allow setting individual items as unread if every time you open the inbox it sets everything to read automatically.", as that to me seems very much possible? I just only may need to keep something unread in like 0,05 percent of all notifications I get, so I personally much prefer extra clicks/movement to be limited to those cases and not the 99,95% of the time I don't need it
    – Tinkeringbell Mod
    Nov 29, 2022 at 18:02
  • 5
    @Tinkeringbell If they made it so that opening the inbox menu marked everything as read, then even if you went and marked some items unread again, the next time you open your inbox menu, they'd be marked read. So not only would you have to keep marking them as unread each time you access the inbox, you also have to remember which ones are unread to go and mark them as unread again. Which also isn't possible after a certain point when they get pushed off the menu and into the /inbox network page.
    – TylerH
    Nov 29, 2022 at 18:39
  • @TylerH ah, like that. Well the post itself said that if asked, they might provide, so I assume they can somehow mark the ones that were manually marked "unread" to stay that way, and not be dismissed when opening the inbox :) But yeah, it makes sense that this is a technical thing to keep in mind when building :)
    – Tinkeringbell Mod
    Nov 29, 2022 at 18:41
  • Personally I like the notion of just removing the red number/indicator when you open it, while leaving the color difference on each individual item... I'm fairly confident most people who open and close to 'mark as read' as a convenience measure are more concerned about the red indicator on their top bar rather than actually marking every item as read within the menu. I agree there's certainly some middle ground available for improvement here.
    – TylerH
    Nov 29, 2022 at 18:43
  • 2
    @TylerH While I realize the quote says “when the inbox is opened,” but it also says “the current behavior”—the current behavior is to mark them all as read when the inbox is closed. That eliminates the concern about previously-marked-unread items being shown as read the next time you open the inbox (it does imply that you’d have to mark them as unread over and over unless there’s logic to skip manually-marked-unread items, as Tinkeringbell suggests, but still, that’s “annoying” rather than “useless”).
    – KRyan
    Nov 29, 2022 at 20:40
  • @KRyan I don't see a difference between doing it when you open vs doing it when you close (and the current behavior is now "don't mark them all as read unless you click mark them all as read", which is instantaneous); the end result is still "next time I open the inbox menu, all my previously-marked-as-unread messages are now marked as read. The point here is what is unread should persist as unread until you either perform a 'mark individual item as read' action or perform a "mark all as read" action. Neither opening the inbox nor closing it count as such an action, nor should they.
    – TylerH
    Nov 29, 2022 at 21:14
  • 4
    I don't really care that the message stays marked as unread until i mark it, what i care about is getting rid of the red dot on my header notifying me of things i've literally already read and responded to. If it'd stop notifying me of comment replies to posts i'm literally currently looking at/reading it wouldn't be so bothersome.
    – Kevin B
    Nov 30, 2022 at 16:36
  • 3
    @Tinkeringbell "so I assume they can somehow mark the ones that were manually marked "unread" to stay that way" - don't make that assumption. Doing this will be a much bigger change than giving an option to restore the old functionality (open the inbox, all are read). Dec 1, 2022 at 21:06
  • 3
    @KevinB "If it'd stop notifying me of comment replies to posts i'm literally currently looking at/reading it wouldn't be so bothersome" - that sounds like something that would be better in it's own answer below, and not in the comments here (forgive me if it is already there). Dec 1, 2022 at 21:07
  • i don't feel it's worth my effort
    – Kevin B
    Dec 1, 2022 at 21:10
  • 4
    Please add this back! It may be opt-out feature, but having to click "mark as read" to remove the red dot is extremely annoying. Alternatively, add an option to hide that mark forever instead (less preferable for me, but still better than 3 clicks for nothing) Dec 4, 2022 at 20:37
55

Mark all notifications from a post as read after opening only one.

Sometimes I get a notification because a followed question is edited, has a comment and a new answer and maybe even closed which are 3-4 different inbox messages, but I only really need to open one.

Can we have a setting to mark all notifications from a single post as read when one is opened?

9
  • 13
    Honestly I would argue this is a bug because if the same user comments twice, only the most recent comment is shown, but both comments count toward the notification count bubble, and you have to click 'mark all as read' to get the bubble to go away.
    – TylerH
    Nov 29, 2022 at 15:47
  • 5
    It should however group those notifications together, so that it's clear there are multiple ones and all of them will be marked as read. Otherwise it'll be very confusing when following multiple active discussions.
    – Bergi
    Nov 30, 2022 at 0:21
  • 5
    To clarify, you are asking for "click on a notification for a single question, mark all the notifications for that question as read, but not for notifications on answers on the same page"? In this case, would there still be value to indicate on page load what were the comments that had notifications that were just marked as read? Dec 1, 2022 at 21:08
  • @YaakovEllis if I've understood you correctly, yes. Dec 2, 2022 at 3:31
  • 2
    the inbox makes me go insane. 3 notifications from same post. I have to click 3 times so everything is unread.
    – user226651
    Dec 19, 2022 at 13:39
  • I agree it feels like a bug. It doesn't make any sense that the red number of notifications will be different from the number of notifications shown to you when you expand it. And if this answer is implemented directly, it's very likely to miss the new comments or answers on the page, or waste time hunting for them, when you're opening the only one in the inbox that is shown to you.
    – minseong
    Mar 5, 2023 at 15:14
  • 3
    now, when marking the newest notification as read, all related notifications are also marked as read. I hope that solves the problem!
    – marrados StaffMod
    Jun 29, 2023 at 9:01
28

/

Is there keyboard binding for marking messages as read? If not, can one be implemented in the future?

Some times I am already looking at the post where I got a reply. Since I already know what the notification is telling me about, I can just press i -> Esc to open and close the inbox drawer and clear the notification.

I would like to keep being able to use the keyboard when possible and not reach for my mouse. And especially for clearing several notifications, I would prefer to avoid clicking a lot in quick succession. Working with a keyboard is more comfortable than clicking a lot.

2
  • 7
    We are planning to add keyboard bindings for mark-all-read, refresh inbox (when it is available). Might also be good to have one for "mark all messages read for the current post" (though that one will be a bit trickier). Nov 28, 2022 at 13:59
  • 2
    @YaakovEllis I'd be happy with something like "mark read for post 1, 2, 3...x". Right now i -> 1 will open the first notification item. Maybe something like i -> Shift + 1 (or other modifier) can clear the notification.
    – VLAZ
    Nov 28, 2022 at 14:01
24

If you scroll the Inbox scrollbar all the way to the bottom, all of the items disappear; I'd expect the last few items to remain on the screen. Scrolling back up re-displays the items.

blank Inbox after scrolling to the bottom

  • Browser: Google Chrome, Version 107.0.5304.122 (Official Build) (64-bit); can also reproduce with Microsoft Edge, Version 107.0.1418.62 (Official build) (64-bit)

  • OS: Windows 10 Enterprise

  • Screen resolution: 1920 x 1080

9
  • 1
    can you please add your browser, OS, and approximate screen resolution (wide/narrow, etc)? Nov 29, 2022 at 14:01
  • 1
    I have also noticed this bug. Opera 93.0, macOS 10.14.6, either wide or narrow. Nov 29, 2022 at 14:20
  • @YaakovEllis I can reproduce with same browser and OS but it doesn't look like a specific browser issue. When you scroll all the way down, you don't see the empty page? Nov 29, 2022 at 14:21
  • 6
    Can reproduce as well. It seems like it might have something to do with the margin-top: 100% on the .inbox-se-link-new class on the last child <li> of the rendered list (that houses the "Go to full inbox" link).
    – Cᴏʀʏ
    Nov 29, 2022 at 15:41
  • 1
    Reproduced in Firefox 107.0 on Windows 10 (1920x1080 resolution)
    – TylerH
    Nov 29, 2022 at 15:47
  • 7
    Chrome, Brave and Firefox on Ubuntu 22.04 (all up-to-date, from deb) - confirmed on all three. Doesn't depend on screen width. Repro's even on phone emulation via devtools. li.inbox-item.inbox-se-link-new.js-see-all-inbox-items (last li of notifications, containing "Go to full inbox" link) is what's causing the shift; removing margin-top: 100% from it fixes the issue. Nov 29, 2022 at 17:25
  • Can repro on Mac Mojave, Safari 15
    – Tetsujin
    Nov 30, 2022 at 12:47
  • @YaakovEllis FYI, see above comment where someone tracked down the cause for the bug. Nov 30, 2022 at 13:05
  • can repro on MAC ventura MS Edge. Dec 1, 2022 at 11:58
23

Remember my preference for all/unread (top-left)

When I switch from 'All' to 'Unread' in the top-left, that state is maintained for the lifetime of the page, but not after a refresh.

I pretty much don't care about notifications that I've already read. I prefer the unread view as the default.

If this setting was persistent, then unread could stay as my default state after I changed it once.

23

A minor request: the wording "mark all read / unread" looks a bit off. Can it be updated to read "mark all as read / unread"? The latter is much more common than the current choice — see the Gmail, Outlook, or GitHub Notifications' wording for a couple of major examples. Keeping the wording consistent across products and services for common actions ensures a smooth user experience.

3
  • 2
    I agree with this, to me reading "mark all read" implies doing something with the read items rather than marking all items as read Nov 29, 2022 at 18:09
  • 1
    yup, indeed, @WhatsThePoint. Since in "mark all read" the last word is an adjective, first of all, it implies a noun should follow it (for example, "items"), and that implies an action should follow it (for example, "for deletion" / "as unread"). A correct phrase the current wording would look something like this: "mark all read items as unread", a shortcut for which is precisely the proposed wording: "mark all as unread" :) Nov 29, 2022 at 18:46
  • 1
    And so it is done. Good suggestion - I believe the original intent was to make the button slightly shorter, but the clarity of the message is more important.
    – marrados StaffMod
    Jan 31, 2023 at 9:32
21

In the spirit of the promise made in Providing a JavaScript API for userscripts back in December 2021, will an effort be made to provide userscript authors with a way to hook into the inbox? If not, please, at least ensure that the logical units of the feature have ids (or js-* classes depending on the team's preferred style) set on them so we do not have to rely on brittle CSS selectors that are subject to break at any point.

3
  • 3
    hooks into the inbox are a longer-term goal - if you have specific hooks you'd like to see, please list them here. In the meantime, happy to put js-* classes on any element of interest. They should all be there, if one is needed, let us know please. Nov 29, 2022 at 12:45
  • 1
    That's great to hear, @YaakovEllis - let me examine the version that just went live. When I come up with a list of what areas are of key importance, I'll surely add the suggestions to the post. Extending the top menu bar has traditionally been a pain point for script developers, so having some hooks at least in the long run will go a long way. Heck, if nothing else, that would mean we would be able to easily prototype features we'd like to see implemented :) Nov 29, 2022 at 15:22
  • 3
    At a cursory glance, the markup is pretty good, actually (major thanks - items, wrappers, and controls all have appropriate classes) - that basically leaves us thinking about the stable API (exposing the controller to the StackExchange global, maybe?) only. Need to read through the source code first, though - will get back to ya'll with suggestions. Nov 29, 2022 at 15:27
20

Explicitly indicate the number of comments in the notification, so that the numbers add up

Currently, when multiple comments are made on a single post, the notification number will be incremented once for each comment, but the actual dropdown will consolidate those into a single notification from the time it was last opened/marked read. For instance, if one post of mine got three comments and another one of mine got two, the inbox number will be incremented by 5 but only two entries will show in the list (for each of the two posts).

It would be nice if each notification entry that's actually multiple consolidated into one would show the number of notifications that have been consolidated. I often get confused when opening the list which said there are five unread notifications but only seeing one, two, or three ones actually listed, and it makes for poor UX. Showing the number would more clearly indicate how they add up.

3
  • 6
    Yes! Although I would rather see them all as individual notifications, grouped in a tree, that you could choose to mark as read/unread all at once or individually.
    – TylerH
    Nov 29, 2022 at 15:49
  • Came to MSE to report this as a bug, especially because once you click on that one consolidated notification and read the comment, another unread notification will appear in the dropdown and this will continue until you've clicked each of the new unread notifications for comments on the same post in turn.
    – WBT
    Jan 11, 2023 at 22:14
  • 1
    now, when marking the newest notification as read, all related notifications are also marked as read. For now we're not planning to add a number of consolidated notifications in the inbox, but I agree it'd be nice to have. I hope that solves the problem!
    – marrados StaffMod
    Jun 29, 2023 at 9:04
18

After playing around with it for a couple of hours I have to say I really like it!

It's a welcome improvement to something that was always an annoyance, so thank you to the team for implementing.

One enhancement I'd personally like is for where you have several new notifications all linking to the same question - for example, notifications about several new comments and/or one or more new answers on the same question, I'd prefer to have all notifications that relate to this same question marked as read when I click on any of them.

One rather big annoyance is that if I select to show only new messages, this is not remembered - if I refresh the browser window it's back to showing all. Can this setting not be saved, it's a bit redundant otherwise?

And a very minor niggle (no biggie) is when choosing to view only unread messages, I wonder if the window could be sized appropriately – i.e., if no new messages, then don't show a large blank area but increase its size until it reaches the max (could it be user-draggable like an answer text box?).

3
  • 4
    Thanks for the positive feedback! We definitely have "figure out a better way to handle merged notifications" on our list of things to address, as well as remembering th euser's setting for filter. Nov 29, 2022 at 19:05
  • 2
    This sounds very similar to my feature-request! Great minds and all that! Nov 30, 2022 at 7:55
  • @YaakovEllis please come to the conclusion that the best way to handle it is to not merge at all
    – minseong
    Mar 5, 2023 at 15:18
18

Mark notification as read if opened in new tab by any means (including right click menu -> open in new tab).

If one left clicks on an unread item, the relevant post/comment/whatever is opened and the item is marked as read (at least sometimes, not sure what the exact conditions are...).

Can we please get the same behaviour if we open the item in a new tab (e.g. by right clicking and selecting "open link in new tab")? At the moment, this just opens the relevant post in a new tab, but the item stays unread and one needs to open the inbox yet another time to mark the item as read...

7
  • 5
    We spent some time on this in the dev process, and have it working for left-click, ctrl-left-click (open in new tab), and middle-click (open in a new tab). The challenge with "right click - open in new tab" is that there is no way to only catch it for "open in new tab" but not for the other right click menu options. So it is all-or-none with right click, and we chose not to mark as read then, because there are other legitimate uses of right click that dont include opening a new tab, and there are 2 other new tab options available (ctrl-left and middle). Dec 1, 2022 at 7:00
  • @YaakovEllis Middle click is not easily available via touchpad and having to use use the keyboard just to open a notification in a new tab is annoying. Can there a setting to enable right click to mark as read? Or an mechanism via the api to mark a specific inbox item as read? Then we could simply build our own inbox which would work as we need it to work. Dec 1, 2022 at 9:10
  • 6
    Seems trivial to do if a parameter is attached to the URL. The same way clicks from the side bar are tracked by adding lq=1 (for linked) or rq=1 (for related). In a similar fashion, links from inbox messages parameter can indicate "mark a message as read after requesting this URL". Then it would not matter which mode of opening the page is used.
    – VLAZ
    Dec 1, 2022 at 13:52
  • 1
    @VLAZ This would be awesome! And would also work from self-build inboxes! Dec 1, 2022 at 13:54
  • 1
    Wouldn't it be far more useful to mark notifications as read at the visiting page without extra parameters? Why should i have to click on a notification in the inbox to cause it to be read when I load the page it's pointing at outside of the inbox? 99% of the time notifications i get are for things on pages I'm already on.
    – Kevin B
    Dec 1, 2022 at 15:45
  • 3
    Came here to report exactly this. Drives. Me. Nuts. Right-Click > Open in new tab is my usual flow for dealing with notifications. Dec 3, 2022 at 14:28
  • 1
    @KevinB perhaps. It's a possible way to do it. However, then you might miss that something happened on the page if you didn't see the notification but just navigated there for another reason. Especially on long Q&As on Meta, it's very easy to miss if a comment or even a new answer was posted. I'd rather not clear out all the notifications for, say, 7 comments on 3 different posts and two new posted answers just because I went to check something in the question.
    – VLAZ
    Dec 5, 2022 at 13:00
16

? ?

Clicking "mark as read" on a collapsed multiple notifications item should mark all of them as read or mark the shown one as read and show a previously hidden unread item.

Currently, this is what happens:

  1. Get multiple notifications from a single post (say, 3).
  2. The inbox icon has 3 in red circle, and when I open it, there is a single collapsed unread item.
  3. Click "mark as read" on it. Now all items shown are marked as read, but the inbox icon still indicates 2 unread items.
  4. When I close and open the inbox, then it shows another unread item from the same post.

I think the behavior at step 3 should be changed to one of the following:

  • all associated items are marked as read (and the inbox counter decremented by that amount);
  • only the shown item is marked as read, and the next unread item from the same post shows up immediately.
1
15

My impression is that with the old design, when I was notified about an unread chat message, reading it would turn off the inbox notification for it.

Not so with the new design. It notifies me of an "unread" chat message even after I have read it and even replied to it.

In some more detail, this is different from the "bring back the old behavior" requests in that I think this use case is separate, and easier to reason about:

If there is a notification balloon in chat, I have an unread message, and the inbox should notify me about that.

If there is not a notification balloon in chat, that message is now by definition not unread.

For some more context, I have several browser tabs open with the chat rooms I'm participating in. So I basically never click an inbox notification to be taken to an unread chat message because that would duplicate a tab I already have open.

2
  • 2
    You need to click the inbox item or the envelope icon near it in order to mark it as read, that's a new functionality. (Before all items were marked read when you just opened the inbox.) Dec 1, 2022 at 14:27
  • 6
    Indeed, but when there was a single message I was notified about and it was a chat message, reading that message in chat was enough. The hassle to mark each chat message read twice is unwelcome and unnecessary.
    – tripleee
    Dec 1, 2022 at 14:30
14

"Read" notifications are literally grayed-out, making the entire box gray.
This feels completely out of place, it's the darkest element on the page (on Meta and light mode SO):

enter image description here

I'd prefer it to have some opacity, for example:

enter image description here

(Crossposted from my SO Meta question after I found this announcement)

3
  • 1
    Personally, I would go about this in a different way: All read messages show normally (like the 2nd one you have, without bold), but the unread ones have an highlighted background (and maybe bold text). Dec 5, 2022 at 12:40
  • 1
    That also works, yea!
    – Cerbrus
    Dec 5, 2022 at 12:41
  • 1
    It's a feature, not a bug. Yes, I also said about this on the original announcement. And no, IMO the opacity makes some strain to the eyes. @IsmaelMiguel This is exactly what I proposed, to keep the old design which is consistent, more unique and not trying to be GMail.
    – EvgenKo423
    Dec 11, 2022 at 16:37
13

Update the cached count of notifications once the dropdown is opened

Sometimes, a stale number of unread notifications will show in the dropdown, which happens when one or more notifications received since the number was loaded have been marked read from a different instance of the site (another window or tab on the same device, or a different device) but the number in the first instance hasn't had a chance to update. Perhaps it didn't receive the WebSocket ping that updates the number (because, e.g., the device was put to sleep, briefly lost its Internet connection, or the browser put the tab to sleep to save resources), or perhaps the user's browser loads in a cached version of the page with a stale count.

In that case, when I open the dropdown (successfully), the actual current state of my notifications being read/unread are loaded in, but the number on the button still reads the old stale number. This creates a UX inconsistency where the number displayed doesn't match the actual number.

Currently, the only workaround I've tested is to click the button to mark all notifications as read. In the case I've encountered, where it showed a number of 1 but the actual dropdown showed nothing unread, clicking that updated the number and made it disappear. However, this causes undesired effects if one has deliberately left unread notifications. Another workaround is to fully reload the page, but this is a bad solution for someone on a slow connection or one that imposes a heavy data cap.

When the dropdown is opened and the current live status of unread and read notifications is loaded, can the number shown in the button please be updated to show the actual count in case it was stale since the last load?

1
  • 2
    I encounter this frequently when I have multiple Stack Exchange tabs open. A call to /topbar/inbox appears to be made on first click of the inbox on a given page, which loads a fresh copy of the notifications pane content, but the actual notification number does not update to match its state, creating a mismatch. GIF version
    – zcoop98
    Dec 19, 2022 at 18:04
13

Expand the filtering functionality

I think an option to filter for certain SE network(s) would be helpful. I keep an eye on my Stack Overflow notifications, but I miss them on the other networks from time to time. Having that option would make it easier for me to circle back to them.

If you decided this is a valid request, then you may want to implement a filter for different types of notifications, i.e. comments, chat, etc. while you're at it.

3
  • 1
    That can be done however I don't think inbox is so big that it can accomodate a filter. If we insert a filter inbox will look like a lot in very less space in my opinion. Nov 28, 2022 at 15:50
  • 2
    @JitendraSingh I think from the UI standpoint, a lot can be done to make it minimalistic yet easy to navigate. Off the top of my head, add a small button on top which will open the filter as an overlay on top of the notifications so it doesn't spill all over the page.
    – M--
    Nov 28, 2022 at 16:08
  • 1
    @JitendraSingh I think a row of site icons, like the one that appears in Achievements dropdown when you get rep on multiple sites, would work great. After loading notifications you could build a site list and display icons only for those sites that are currently in the Inbox.
    – EvgenKo423
    Dec 12, 2022 at 9:22
12

At least on StackOverflow, I noticed that I have to manually mark the notification as read which is kind of annoying. Previously once I open the messages menu, the unread count notification automatically went away.

enter image description here

Is there a setting using which we can revert to previous behavior?

4
  • 5
    See the answer to "Can I keep the current inbox functionality?" in the announcement: "No. However, depending on the feedback, we may introduce the option to keep the current behavior of marking all notifications as read when the inbox is opened. If you want us to implement this as an option, please let us know!"
    – V2Blast
    Nov 29, 2022 at 17:26
  • 7
    @V2Blast - Thanks and yes please. I would very much like to have that option. Right now it is an annoying distraction and IMHO once I have clicked on the message icon on the top button bar, I think the job is already done. Having to explicitly mark a message as read is an additional step for me which is not adding any value regarding my interaction with the site. Nov 29, 2022 at 17:30
  • 1
    The added value is when you see new messages but don't interact with them (like reading the full comment, viewing the answer to a followed question, etc), then you will probably want to look at them later. With the new functionality it is easy to see which items you have not 'completed' yet. Once you do interact (i.e., click on the message) then it is marked as read automatically. This is the same as for example an e-mail inbox, when you open your inbox it does not cause all new emails to be marked as read.
    – Marijn
    Nov 30, 2022 at 9:58
  • 1
    @Marijn If i want to interact with a thing i will remember, if i dont remember it was probably not so important. I get it that SE wants more interaction but honestly I dont. It would have been many many times useful if i had just stopped to react to other people. I mean if somebody wants a clarification fine but really anything more ask a question.
    – joojaa
    Dec 1, 2022 at 19:52
12

I find the new design quite confusing, because the bottom button Go to full inbox is white. As such it gives me the impression, that the blue-grayish items are actually unread, because they have a different colour, and the white (unread) items are read. The bold-face font does not really help either and the icons are too far on the right, so it takes a second glance to confirm.

I think it could already help, to colour the bottom button in the same background colour as the rest of the design.

Edit: I also just noticed that this contrasts directly with the Achievements tab, which uses white as a background colour for read items, and the blue-ish/grayish tint for new items.

Please fix this :)

enter image description here

1
  • Yes, I also said about this on the original announcement. As for the buttons, it's rather confusing because they have no borders – a huge problem of many modern designs. If you make it gray, it would still blend with gray items.
    – EvgenKo423
    Dec 11, 2022 at 17:21
12

Add a way to sort unread items to the top

Currently, both read and unread notifications are sorted in the order they were received — it is, of course, expected behavior (and one can always filter out read items), but it would be great to be able to split the notifications inbox modal in two groups: read and unread items.

Grouping unread items allows one to quickly determine what else needs attention without the need to scroll back-n-forth through the list (which can be pretty long for active users) searching for items that might still require attention.

As a precedent, there is an "inbox type" setting in the Gmail web interface:

screenshot of the Gmail web interface "inbox type" setting

We could have something similar: either as a dropdown with sort options or as a profile preference (how it is implemented is not particularly important).

2
  • 1
    Is there a reason the current filter to show only unread items is insufficient for this purpose?
    – V2Blast
    Dec 15, 2022 at 2:56
  • @V2Blast the need to context-switch, mostly. Currently, you can only toggle between "all", which has items sorted by date (thus, sometimes making it a bit hard to find unread items quickly, especially for an active user like myself), and "unread", which obviously leaves out read items (thus necessitating another switch back to "all" once a user is done with checking unread items. Having a way to get the best of both worlds would be nice - it's far from a critical FR, just a QoL thing. Dec 15, 2022 at 11:50
10

As an occasional user and mod on a small site, most of my notifications are comments on answers and such where I basically interact by opening the inbox, reading the comment, deciding if I want to do something, and then leaving the site.

I get that you want to get more engagement to the site, and this functionality seems pretty useful for the highly engaged users who have lots of notifications and want to interact with them. But for me, this just adds another click - one I don't want to make.

Please bring back the old functionality as an option for people like me - and frankly it should be the default option. This method is too difficult to discover for new users - the "mark a notification as read" button (the little envelope) is not intuitive - and new users are the ones who will find this the least useful.

From my point of view, the alternative is for me to add custom CSS to remove the red bubble entirely, which will have the opposite impact of what you're hoping, interaction-wise.

5
  • 1
    Just clicking on the message should also mark it as read (and also redirect). You should only need to click on the envelope if you want to toggle the read status without redirecting. Nov 30, 2022 at 20:05
  • 2
    @YaakovEllis Understood, but I usually don't click on it. When I say read I mean I use the inbox as my content - so many of my comments are trivial things that I can dismiss and ignore. Open the inbox, glance, close inbox is my workflow.
    – Joe
    Nov 30, 2022 at 20:29
  • It would be nice if there were some statistics (ideally from before the change) how often people actually open the inbox but not click on (all) the unread items. I suspect most people do actually click on the inbox items. For myself many comments I get are >100 characters and therefore cut off in the inbox, so even if I only want to read the comment and do nothing with it I need to click on the item. For short items I usually also click because I'm interested in what happens with a followed question or I want to reply to or upvote someone's comment.
    – Marijn
    Nov 30, 2022 at 21:15
  • 2
    I wonder how much this remark will be heard - mine is similar - on a thread that's dedicated to this subject. Seems to me the people coming here are going to be weighted on having interest in this feature. How is SE going to account for statistical self-selection bias? You need to be a pretty savvy user to know stackexchange meta, not <your site's> meta is where you can expect feedback and dialog about the framework's UI. I don't mind this feature at all, as long as it is not the option I am forced to use. If I can toggle a setting that says, "do as before", I am happy. Nov 30, 2022 at 21:58
  • 2
    @Joe the workflow for your scenario right now is to use the read all button. We hope to add keyboard shortcuts as well, and are considering a personal preference to revert to "mark all as read on open". Dec 1, 2022 at 7:03
10

If all of my messages are marked as "Read" and I click on the option "Inbox (Unread)" I see the following:

screenshot of the open notifications modal with empty space taking up most of its height

Can we have a message something like "No unread messages" or "All messages have been read by you" or something like that instead of this white space? Also, just like the other answer stated, please change the "Go to full inbox" background colour as it makes the appearance worse.

1
  • 2
    Agreed. Although I'd prefer a positive message, along the lines of "All messages have been read" or "You're up to date", rather than the double-negative. Also pointing out that the big white space is what it looks like when waiting for messages to load - so it can be misleading. Dec 6, 2022 at 7:57
9

Very inconsistent count for the Refresh button when toggling the state of a message.

When changing from read to unread or vice versa it some times changes the count for the "Refresh (<number of unread messages>)" button, other times it does not.

I cannot find any consistency in it. See this short video, See how marking a message unread will only some times show "Refresh (1)". And marking a message unread will only some times change to "Refresh (0)".

Video showing toggling one message as read or unread repeatedly which only some times leads to an updated Refresh button.

Does not seem to be related to just clicking many times. Happens even if you click one time. Some times you get no update:

Video showing toggling only one message as unread once. The Refresh button does not show up.

Other times it does work on the first click:

Video showing toggling only one message as unread once. The Refresh button shows up with a count of one.

2
  • 1
    Noticed this too, from what I can gather, when you mark it as unread, the code thinks there is new message, so showing the "Refresh" button. Dec 1, 2022 at 14:31
  • 1
    @ShadowTheKidWizard yes. I feel like the Refresh button showing up is probably the real bug here. But it's also inconsistent when it does that.
    – VLAZ
    Dec 1, 2022 at 14:33
9

No-one's going to upvote this right at the bottom of the list, but I have to say after a week of giving this a chance…

I absolutely hate the new behaviour.

It has seemingly forgotten the entire advantage of tabbed browsing.

Clicking the envelope doesn't open the message, clicking the message header doesn't mark it as read. This does not work. I have to read it, then mark it as read. Not even the most basic mail app falls this short.

It's just adding more clicks for no benefit, imnsho.
Yet another new paradigm to learn. Two separate interactions for each message.
I just want the count to go away as soon as I start to interact with it & each to mark itself read if I click it to open in a new tab. I send every new message out to a new tab, then go through them. I don't need to then have to go back to the menu to tell it I'm reading the things I already asked it to read.

18
  • 2
    Sorry to hear that it hasn't been working for you. But...clicking the message opens it and marks it as read. Clicking the envelope marks it as read without opening it. If this is not working for you, then there is a local error with the execution of the script for you. Please give your browser version, etc (as it works fine for me on all browsers where I try it). The only type of "open" action that right now wont mark it as read is "right click > open in new tab". But middle click or ctrl-click should mark it as read while opening it on a new tab. Dec 4, 2022 at 19:12
  • @YaakovEllis - I'm on Mac Mojave, Safari 14.1.4 [which I'm aware is technically out of date]. I always 'open in new tab', never click though in the same tab, so I guess that's the bug I'm hitting. I just tried variants on a theme of 'open' & as far as I can see, only 'send my current tab to the new URL' dismisses the message & header count. I only had one message - yours above - in the queue when I tried that.
    – Tetsujin
    Dec 4, 2022 at 19:20
  • 2
    Our challenge with handling "right click > open in a new tab" is that there is no way in the browser (that we were able to discover) to know that this is what you did after you right-clicked. We were left with either "every right click marks as read, no matter what you did (or even if you did nothing)", or "right click does not at all mark as read". Dec 4, 2022 at 19:22
  • 2
    Now - someone else above complained about the same thing - that this is their primary way to mark as read (this being the only option on many tablets). And it is something that we have to consider - whether it is fair to users to mark as read for any right-click. Dec 4, 2022 at 19:23
  • 1
    We are also considering trying to address this (though not right away) with functionality that would mark all inbox items read relating to the question/answer being opened (and preferably also indicate on-screen what the previously-unread items had been). This feels like a superior solution to me as it doesn't require guessing the intention of the reader on a right-click, and also takes care of all related inbox items at the same time. But it will have to wait it's turn for implementation. Dec 4, 2022 at 19:25
  • I'm not 'technically' right clicking. I'm using a 3rd party mouse with a non-standard button config, but what it's actually sending to the OS is as though I Cmd/clicked a link. This in itself is a 'valid' macOS/Safari command, set in prefs as 'open link in new tab'. I'm aware that feels like it adds complexity, but I have tested a true Cmd/click & the behaviour is identical.
    – Tetsujin
    Dec 4, 2022 at 19:26
  • 1
    One usage pattern that is now possible that I have tried and often use now, is to just have one tab open. Open the inbox, click on an item, it loads in the same tab and is marked as read. You no longer have to open up lots of other tabs (since the inbox marks all the messages as read right away, and this is the way to use it). You can go one by one. Dec 4, 2022 at 19:26
  • 1
    "I have tested a true Cmd/click & the behaviour is identical" - then this is probably a quirk with your particular browser. In all that I have tested, ctrl-click marks it as read. Disclaimer: I develop on a windows machine, and ever since Apple stopped offering Safari on Windows, I have had no way to test Safari (though others on the team can do so , and I'll try to enlist their help on this when we are able to get to it). Dec 4, 2022 at 19:28
  • I appreciate it's a potential working method - but years of habit have nbeen that if I have a tab, it needs my attention - maybe now, maybe tomorrow; but I do cycle through them to see if they have any unannounced activity, which they often do. It's become a simple 'Open I want to know, closed, fugettaboudit' with the very occasional 'following' for something I feel may move long term, but not this week.
    – Tetsujin
    Dec 4, 2022 at 19:30
  • @YaakovEllis - [sorry, keep forgetting to tag you] Mac does't use ctrl/click except to open the contextual menu [an alternative to right click for those used to trackpads] so it's not something I can test on this platform. Also, no middle click [which I think is a nix thing? can't test]. --- Lemme just jump onto this from Chrome [whilst holding up garlic & religious symbols;) … OK, that behaves differently… but not enough to persuade me to ever use it, sorry:\ So, it appears something is non-standard, but I don't have the expertise to tell what.
    – Tetsujin
    Dec 4, 2022 at 19:39
  • @YaakovEllis Have you considered adding some parameter to the url as suggested by VLAZ in this comment meta.stackexchange.com/questions/384148/… ? Dec 4, 2022 at 19:40
  • 2
    This is starting to feel like the 'Tested with Internet Explorer' days :\
    – Tetsujin
    Dec 4, 2022 at 19:40
  • 1
    @Tetsujin, ahem: "I'm on Mac Mojave, Safari 14.1.4 [which I'm aware is technically out of date]. We do test on the browsers that we support. Dec 4, 2022 at 19:46
  • 1
    @samcarter_is_at_topanswers.xyz adding a parameter is something else that we are considering. We would prefer not to as historically we have tried to avoid this, as it can leak into other things (even if we clear the param on the client or through a redirect). But is is another option. Dec 4, 2022 at 19:48
  • 2
    @Tetsujin anyway - even though your browser is not supported, it is still a scenario that we would like to support. I appreciate your trying it out and taking the time to give feedback. And hope that we will eventually be able to have it addressed to your liking. Dec 4, 2022 at 19:53
9

Accessibility of the filter components

Right now, the clickable area of the filter functionality is very small.

This is the clickable area for the dropdown; it’s only the arrow on its own, when I would have expected the full “Inbox (all)” text to be clickable since that’s what I am switching :

Clickable area on the arrow for the dropdown]

Similarly, within the drop down the clickable area is also smaller than I would have expected. It’s only the text that is clickable:

Clickable area within the dropdown]

I would have expected here that the area where the checkmark icon is being displayed is also clickable. This would help being able to select the other options since in my first attempt, I clicked a few pixels too far to the left of “Unread” and nothing happened.

2
  • 2
    Thank you for your idea! We adjusted the clickable area as per your suggestion.
    – marrados StaffMod
    Jan 31, 2023 at 10:37
  • @marrados Thanks a lot, it’s much better now 😊
    – poke
    Feb 3, 2023 at 20:01
8

Safari 15.5, Mac OS 12.4

Clicking on the message to open the notification's linked post does not mark the message as read, only clicking the envelope (or clicking "mark all read") does.

4
  • 1
    Would it be possible to check in the dev console (F12) and see if you get any console errors when you try this. And on the network tab, see if you have any calls being made to /topbar/mark-inbox-as-read? Nov 30, 2022 at 20:08
  • 1
    WebSocket connection to 'wss://qa.sockets.stackexchange.com/' failed: WebSocket is closed due to suspension.
    – Joe
    Nov 30, 2022 at 20:27
  • 1
    Though, it just started working - did you fix it? :)
    – Joe
    Nov 30, 2022 at 20:27
  • 2
    we didnt change anything Dec 1, 2022 at 6:57
8

Description:

Someone replied to one of my answers. I see a red 1 on my inbox icon. I click on the inbox icon and I see the new message listed along with others I've already read. I click on the link to the new message and get taken to the new comment below my answer. That all seems correct.

However, despite having now seen and read the new message by clicking on its link in the inbox dropdown, the red 1 is still being shown and the message is still shown as unread.

If I click on the "new" message link a second time then finally the red 1 goes away and the message is listed as read.

I would expect the message to appear as read after clicking its link in my inbox the first time. It should not take two views of the same message to mark it as read.

I can of course click on the little envelope icon to the right of the message instead of clicking on the message a second time to mark it as read but that shouldn't be necessary either.

This issue has happened for each new message I've received today since this change went live.


Updated Info on this issue:

This morning I refreshed my browser on stackoverflow.com. The inbox icon had a red 3 on it. I clicked on the mailbox icon and while there was a red 3, the inbox only showed one new message (from this post). I clicked the envelope icon and the red 3 changed to a 2. I clicked the link for the new message and was taken here. I clicked the inbox icon and now I see the message I clicked (marked as read) and a second message from this post (marked as unread). This time I just clicked the unread message link and I was taken back to the comments below this post. The red 2 changed to a 1. So one more time I clicked on the inbox icon and now I see the two read messages I've just clicked on and now a third unread message for this post. Finally I click on the 3rd message link and there's no more red number but now I see only one recent message from this post (marked as read).

This is so confusing. Let me try to summarize what I've seen so far:

  1. It seems while viewing meta.stackexchange.com that clicking the link for an unread message does correctly mark the message as read and reduce the red number on the inbox icon.
  2. For me, while on the main stackoverflow.com site, clicking the link for an unread message does not mark the message as read nor does it reduce the red number on the inbox icon. A second click on the same link does mark it as read and it does reduce the red number on the inbox icon. Clicking the envelope icon next to an unread message does correctly mark the message as read.
  3. Getting multiple messages about the same post results in undesired behavior. The red number shows the total number of new messages but the inbox only shows one new message initially. Clicking the new message link results in one additional message for the post appearing in the inbox. This repeats until all new messages for that post have been clicked. At which point the inbox shows only one (read) message for the post.
8
  • 2
    If you click on the "read" envelope, wait half a second, and then click on the message, does the same thing happen? Or is the "read" status on the second page accurate now? Nov 30, 2022 at 6:23
  • 1
    I'll have to try that on the next message I get. But no one should have to do two clicks to get the inbox status updated correctly. I'll reply when I can.
    – HangarRash
    Nov 30, 2022 at 6:59
  • 2
    ok, thanks. Also be sure to do a hard refresh as well when you get a chance. Nov 30, 2022 at 8:39
  • 1
    @YaakovEllis - this, to me, is an unwanted behaviour. The act of clicking the link to visit the message should in itself be the signal to mark it as read & clear the indicator number [assuming only one message] or reduce the count if multiple.
    – Tetsujin
    Nov 30, 2022 at 13:10
  • 1
    To be clear, clicking the link to visit the message does send a "message-read" to the server. This is how we designed it to work. This is how it works for me (I haven't been able to repro this). I am trying to figure out why it isn't working for this user Nov 30, 2022 at 16:04
  • @YaakovEllis I just added a new section to the end of my post with new details. It seems different sites (stackoverflow.com vs meta.stackexchange.com) behave differently.
    – HangarRash
    Nov 30, 2022 at 16:33
  • 2
    @YaakovEllis - I now see my issue is part of the 'open in new tab' behaviour mentioned elsewhere, which doesn't refresh the count.
    – Tetsujin
    Dec 1, 2022 at 7:51
  • @YaakovEllis Is there a formal place to submit bug reports on these inbox issues? After 6 weeks I am getting really frustrated dealing with these inbox bugs many times a day. Thanks.
    – HangarRash
    Jan 14, 2023 at 5:08
7

So I'm on a question that I've left a comment on and someone responds to my comment with an @. I read the comment, respond, and move on to another tab. That new tab now has a notification informing me of the comment I just responded to. I'm not positive, but I'm pretty sure the old inbox did this too, however with the old inbox this was at least clearable with double clicking the icon. Now, I have to click the icon, wait for the inbox to open and load, then find the "mark all as read" button and click it. I understand it's just a simple extra step, but it's not so simple when the dialog isn't instant, it's just getting in the way.

If it would stop notifying me of things I've already dealt with it wouldn't be getting in my way nearly every time I get a notification.

3
  • 1
    "I'm not positive, but I'm pretty sure the old inbox did this too" it did, yes.
    – VLAZ
    Dec 3, 2022 at 7:33
  • 2
    But the old inbox marked things as dealt with if you had opened the inbox and chosen not to do anything about them, so a spurious notification (or an uninteresting one) cost no extra time beyond viewing it in the drop-down and then clicking away. That was the correct behaviour; the new inbox doesn't respect my choice to ignore something.
    – kaya3
    Dec 5, 2022 at 21:14
  • @kaya3 100%. I'd prefer the old functionality where it'd go away much easier. however, I'm pretty sure there's next to no chance we'll get that back. so... maybe we can instead get it to just ping us less for things we've obviously already seen to lessen the interruption.
    – Kevin B
    Dec 5, 2022 at 21:19
6

When clicking entries in the "unread" filter, sometimes the entry disappears and the link doesn't get opened.

This has happened to me for primary-click (open in same tab) and middle-click (open in new tab).

In certain scenarios, this doesn't happen. I haven't figured out the exact details on when it happens. I'll keep experimenting and listing my findings.

2
  • 1
    Yeah, happens to me too. Strangely, doing that for an unread notification on the All filter both marks as read and opens the tab, but on the Unread filter it marks as read without opening the tab.
    – Michael
    Nov 30, 2022 at 19:14
  • "Sometimes"? I've never had this fail to happen; the entry always disappears without opening the link when in "unread" mode. (My browser of choice is Brave) Feb 3, 2023 at 0:52
6

Opening a message using keyboard shortcut does not mark it as read.

Steps to reproduce:

  1. Have one unread message. You can just toggle the top one to be unread.
  2. Press I for Inbox -> 1 to go to the first message (or 2, 3, etc for other messages).

Expected: Opening a message marks it as read. Actual: It does not. However, left-clicking with the mouse does mark the message as read when opening it.

2
  • 3
    Thank you for reporting it! We have it in our backlog - it wasn't included in the first release, but we will implement it. We also plan to add keyboard shortcuts for all the new actions.
    – marrados StaffMod
    Dec 13, 2022 at 10:19
  • Was it ever fixed? Jun 17, 2023 at 6:43
5

Change All/Unread (top-left) to a better control than a dropdown menu

Why is this control a dropdown menu when there's only 2 options? It takes 2 clicks to change something that should only take 1.

The clickable area is also very small which is bad for accessibility.

It would be better as some kind of toggle control.

5
  • 1
    There are already requests to allow for more options (for example, site filtering). IMO, better leave it as is and let SE expand on the dropdown. Nov 29, 2022 at 14:31
  • @OlegValteriswithUkraine I don't see any request that would strictly involve adding additional dropdown options. If there are more that make sense, then fine. I can't think of any.
    – Michael
    Nov 29, 2022 at 14:36
  • this one :) Nov 29, 2022 at 14:42
  • 2
    @OlegValteriswithUkraine I read that one. I can't really see how a dropdown control would work for site-based filtering without having an option for literally every site, which sounds awful. The current control is for "read-ness". It wouldn't work to cram sites or types into it. If there is a third "read-ness" state you can think of, then fair enough
    – Michael
    Nov 29, 2022 at 14:44
  • The clickable area was expanded to include the "INBOX (ALL)" text, so that part of your answer has been addressed. Your other point is still valid, though.
    – V2Blast
    Jul 19, 2023 at 0:43
5

«Go to full inbox» partially visible on mobile Chrome (iPadOS):

enter image description here

2
  • 1
    It's not visible at all when opening the inbox on my screen — it only shows up when I scroll down a little.
    – Laurel
    Dec 1, 2022 at 0:36
  • 1
    Same problem in Firefox (Ubuntu). Seems like a newly introduced bug, yesterday it was not like this as far as I remember.
    – Marijn
    Dec 1, 2022 at 12:04

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .