codidact
Clicking Inbox Does Nothing
Describe the bug I just registered on Codidact. My Inbox button shows 1 notification. But i can't view it. When i click the Inbox button, nothing happens.
To Reproduce Steps to reproduce the behavior:
- Register as new user on Codidact
- Login
- See notification "1" on inbox button.
- Click the inbox button.
- Nothing happens.
Expected behavior Notification list should open.
Screenshots
Desktop (please complete the following information):
- OS: Windows
- Browser: Chrome
- Version: Version 108.0.5359.99 (Official Build) (64-bit)
Additional context Failed in Chrome Incognito too
Sorry for the inconvenience. This is a known bug (which I'll find and link after typing this comment), but the workaround is: if you click in the white area anywhere around the icon and blue circle, it'll open. There's something wrong with the detection on the symbols directly, but the white bounding box responds.
The bug is in co-design (the framework); looks like it's been fixed there but hasn't been propagated yet: https://github.com/codidact/co-design/issues/72 . Fix should be coming soon, I hope! Here's a related meta post, which we'll update when the fix makes it to production: https://meta.codidact.com/posts/287466.
Thx for the update.
On Fri, Dec 9, 2022 at 8:31 AM Monica Cellio @.***> wrote:
The bug is in co-design (the framework); looks like it's been fixed there but hasn't been propagated yet: codidact/co-design#72 https://github.com/codidact/co-design/issues/72 . Fix should be coming soon, I hope! Here's a related meta post, which we'll update when the fix makes it to production: https://meta.codidact.com/posts/287466.
— Reply to this email directly, view it on GitHub https://github.com/codidact/landing-page/issues/116#issuecomment-1344513336, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMV6UUOIEADUE5FXS6YC2E3WMNNF3ANCNFSM6AAAAAASZQQHLA . You are receiving this because you authored the thread.Message ID: @.***>
According to https://meta.codidact.com/posts/287466 this has been fixed (and I can confirm the button works correctly for me). Can this issue be closed?
