• 56!@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    If they did the exact opposite of this, I think it would look ok. If I was trying to fix this, I would probably just swap the styles of the selected and deselected states. Maybe it’s a miscommunication between designers and implementers, causing the meanings to be swapped?

    • kevincox@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      I don’t think it is that simple. I think that outline is about the “focus”. So if I press enter it will activate that tab, if I press tab it will move the focus to the “Entire Screen” tab.

      The UX issue is that there are two concepts of focus in this UI. There is “which tab is active” and “what UI element will pressing enter activate”. These two are not sufficiently differentiated which leads to a confusing experience.

      Or maybe there can just be no keyboard focus indicator by default, but that may be annoying for keyboard power users. But this is generally how it works on the web, you have to press tab once to move keyboard focus to the first interactive element.

      • 56!@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        Right, that makes sense as well. What I was thinking is that the use of the accent colour shows which one is active, though it would probably be less confusing if this wasn’t done with an outline. See the KDE version for example:

        Screenshot of the KDE screen sharing portal, showing "Screens" and "Windows" tabs, where the selected tab has a horizontal accent colour line above it.

        Regarding keyboard navigation, I could see this working similarly to radio buttons, where the tab key selects the entire tab group, and tabs need to be navigated using the arrow keys. In this case I think it makes sense to put the focus border around only the selected option, and having the focus border follow the selected option when arrow keys are used. If this is the case, I think swapping the current version does make sense.

        • kevincox@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          edit-2
          3 months ago

          Yeah. I like old school tabs that were clearly attached to the thing that they switched. I definitely prefer the KDE UX here.

          • 56!@lemmy.ml
            link
            fedilink
            arrow-up
            0
            ·
            3 months ago

            Sadly KDE is also trying out the “modern” style tabs in some places too:

            Screenshot of the top of the KDE keyboard system settings page, showing 3 large buttons which act as tabs