22

After I open the inbox by clicking on the navbar icon, clicking on it again used to just close the inbox.

Today, the second click redirects me to my full-page inbox, https://stackexchange.com/users/<userid>/<username>?tab=inbox.

The workaround is to press Escape to close the inbox (although this doesn't clear the unread count). Another workaround is to install SOUP

In the console is this error from full.en.js?v=9830c055969f:1:

Uncaught TypeError: Cannot read properties of undefined (reading 'count')
    at g.setUnread (full.en.js?v=9830c055969f:1:19841)
    at g.setUnread (full.en.js?v=9830c055969f:1:34432)
    at g.setUnread (full.en.js?v=9830c055969f:1:14055)
    at g.markAsRead (full.en.js?v=9830c055969f:1:19669)
    at g.markAsRead (full.en.js?v=9830c055969f:1:34182)
    at g.markAsRead (full.en.js?v=9830c055969f:1:14055)
    at g.markAsRead (full.en.js?v=9830c055969f:1:18279)
    at g.markAsRead (full.en.js?v=9830c055969f:1:32156)
    at g.markAsRead (full.en.js?v=9830c055969f:1:14055)
    at g.toggle (full.en.js?v=9830c055969f:1:15386)
setUnread   @   full.en.js?v=9830c055969f:1
setUnread   @   full.en.js?v=9830c055969f:1
(anonymous) @   full.en.js?v=9830c055969f:1
markAsRead  @   full.en.js?v=9830c055969f:1
markAsRead  @   full.en.js?v=9830c055969f:1
(anonymous) @   full.en.js?v=9830c055969f:1
markAsRead  @   full.en.js?v=9830c055969f:1
markAsRead  @   full.en.js?v=9830c055969f:1
(anonymous) @   full.en.js?v=9830c055969f:1
toggle  @   full.en.js?v=9830c055969f:1
toggle  @   full.en.js?v=9830c055969f:1
(anonymous) @   full.en.js?v=9830c055969f:1
dispatch    @   jquery.min.js:3
r.handle    @   jquery.min.js:3
Improve this question
11
  • 2
    Out of sudden frustration I found this post - my Inbox is now BROKEN - clicking the icon to close it, like I always do, suddenly starts navigating to the "view all" page. This is horrid - please roll it back!!
    – Stu
    Commented Oct 27, 2022 at 16:59
  • @Stu You can use the Escape key to close the inbox.
    – Barmar
    Commented Oct 27, 2022 at 17:01
  • 1
    @Barmar - why do I suddenly need to change the way I work and have always worked? I'm using the mouse, not the keyboard!!
    – Stu
    Commented Oct 27, 2022 at 17:01
  • 2
    @Stu It's just a workaround until they fix it.
    – Barmar
    Commented Oct 27, 2022 at 17:02
  • @Barmar Ah ok - so this is not by design then? Sorry, Still seething with frustration lol ;)
    – Stu
    Commented Oct 27, 2022 at 17:03
  • @Stu Yes -- don't you see the error message in the question? That's preventing the code that enables the second click processing.
    – Barmar
    Commented Oct 27, 2022 at 17:05
  • @Barmar Yes I do now I've taken the time to properly read it 😎 fwiw I see the same in the console too.
    – Stu
    Commented Oct 27, 2022 at 17:07
  • 3
    This might be related to the planned inbox improvements, though as far as I know nothing should be changing for the public just yet. We'll look into it. Also potentially related: New inbox notifications have broken keyboard shortcuts, Notification counter doesn't go away anymore after clicking outside the window
    – V2Blast
    Commented Oct 27, 2022 at 17:19
  • This was indirectly useful as I was unaware of SOUP which I've installed for chrome - the console error is still there but at least it prevents the navigation so usability is restored 🤗‎
    – Stu
    Commented Oct 27, 2022 at 17:23
  • 1
    @V2Blast too bad weekend just beginning, meaning waiting at least three more days until someone will be able to take a look. Thanks for the heads up anyway, and if possible try to nudge someone in high enough floor to have some policy "Do not push partial changes to production" as this keeps happening. (Partial changes leaking to production before features are published, sometimes developers do it on purpose to test directly on production as was the case with Saves, that were "alive" for weeks before being actually published.)
    – Shadow Wizard
    Commented Oct 28, 2022 at 6:40
  • 1
    @ShadowTheKidWizard: I think all of the bugs that have been reported are already in the process of being fixed (or have fixes ready and just need to be reviewed/tested before they go live).
    – V2Blast
    Commented Oct 28, 2022 at 16:09

1 Answer 1

Reset to default
5

We just pushed the fix for the issue. During the implementation of the new inbox features we had to touch existing code, too, and unfortunately we caused this bug.

Thank you very much for the report and even more for your patience. We're sorry you've experienced those issues and hope that the planned improvements will make up for it!

Improve this answer
2
  • Unsure if related to this but when I navigate to a post via clicking the link in my inbox, after a few seconds a lot of errors appear in the console, Uncaught (in promise) {message: 'A listener indicated an asynchronous response by r…age channel closed before a response was received'}
    – Stu
    Commented Oct 28, 2022 at 18:52
  • 2
    @Stu I don't see that. Check if it's related to extensions. I see lots of net::ERR_BLOCKED_BY_CLIENT errors that are due to blocking ads.
    – Barmar
    Commented Oct 28, 2022 at 19:15

You must log in to answer this question.

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