No internet connection
  1. Home
  2. Support

Popups flicker

By Christian Scheuer @chrscheuer2019-04-25 08:01:14.030Z

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.

  • 11 replies
  1. C
    Christian 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.

    1. CChristian Scheuer @chrscheuer2019-04-25 08:38:55.697Z

      And FWIW the popups I was talking about is for example when you click the "Change" btn

      1. 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.

    2. Progress
      with handling this problem
    3. 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.)

      1. C
        Christian Scheuer @chrscheuer2019-04-30 14:06:34.232Zreplies toKajMagnus:

        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.

        1. KajMagnus @KajMagnus2019-04-30 14:11:17.797Zreplies tochrscheuer:

          Interesting. A bit later, I can create a separate topic about Postponed and describe a bit more what i have in mind, in case you have more feedback & thoughts about how you want it to work.

          1. C
            Christian Scheuer @chrscheuer2019-04-30 14:15:10.071Zreplies toKajMagnus:

            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.

            1. KajMagnus @KajMagnus2019-05-02 08:35:44.564Zreplies tochrscheuer:

              Ok, I've resumed working with this, i.e. the [too many tabs —> too many connections] probem. I reopened the original topic: https://www.talkyard.io/-138#post-19

              1. KajMagnus @KajMagnus2019-05-15 13:08:34.466Zreplies tochrscheuer:

                @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

                1. KajMagnus @KajMagnus2019-05-26 11:08:02.523Z

                  Closing this for now (so it'll disappear from the things-to-do list, for now). I'll try to remember to reopen, if I implement topic priorities, or postponing-of-topics.

                  1. @KajMagnus closed this topic 2019-05-26 11:08:07.234Z.