All modal popups tend to flicker the screen. This could be made to feel more intuitive.
The rest of the GUI seems very nice and smooth so this is something that makes any UI interaction that involves the popups seem unfinished.
Lmk if you need more info.
- 9 replies
- CChristian Scheuer @chrscheuer2019-04-25 08:38:36.604Z
I think what I meant is that it makes it feel like the site is slower than it actually is. It flickers on popup open, and it seems "stuck" for a little while when closing the popup. Everything else on the site seems to happen before I can even blink my eyes :) Maybe some css transitions are needed, or a different trigger for when to close the fill/bg layer.
And FWIW the popups I was talking about is for example when you click the "Change" btn
- KajMagnus @KajMagnus2019-04-30 13:54:46.733Z
Aha yes it does seem stuck for a little while, when closing the Change dialog. Thanks for explaining. There's a CSS animation that fades the backdrop in and out (if I remember correctly) — maybe I could adjust the timings of this animation so it happens faster. .... This also happens when I open and close the hamburger dropdown next to each post.
- Progresswith handling this problem
- KajMagnus @KajMagnus2019-04-30 13:57:17.291Z
I'm currently too short of time to consider UI things like this :- ) I have in mind to add a Postponed topic status, and postpone this topic until a later point in time.
(Hmm, this issue could be a good thing to fix, later when / if I find more full time people who want to help out with Talkyard — they can fix this issue and in the same time become familiar with the build system and code base etc.)
Postponed is a good idea!
I have 60+ bug reports I need to sort in our system haha, and right now I'm using pinning to prioritize. But postponed would definitely be nice. Especially if postponed meant they would come at the end of the category list. That way you'd have pinned, normal, postponed.
FWIW I also often like to open up say the 10 bug reports I need to work on (a way of keeping them in memory). But I very often hit the websocket connection limit. I know you intend to support this via PWA, just to let you know it still is quite limiting to my workflow. I would love it if there was a sort of fallback so this was possible (I don't need all the tabs to be polling data all the time, maybe only when they're active..) Or maybe some sort of static rendering of the first content so it was still possible just to "get the page" even if I had too many open connections for dynamic behavior. If that makes sense.
@chrscheuer FYI: Now I posted some thoughts about the Postponed thing I mentioned before. Actually, instead of Postponed, I'm now thinking about topic priorities, so Talkyard can also work like a light weight ticketing / issue-tracking system. Here: https://www.talkyard.io/-225/topic-priorities-a-pritority-tab-sort-by-priority