67
I have made the first actual change in my lightly fork, what do you guys think? (lemmy.kde.social)
submitted 2 years ago by to c/kde@lemmy.kde.social
33 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 34 points 2 years ago (5 children)

I think this is a big accessibility issue. Please let tabs be tabs. This design seems too similar to Firefox's new design where it's hard to tell which tab is active (specially if you have only two open). I feel like tabs should be attached to the viewport/content otherwise they look like buttons where my intuition is to click on an active to tab to activate it

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 3 points 2 years ago (3 children)

    in what way is this an accessability issue, it just seems to be a minor visual stylization change?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 2 years ago* (2 children)

    Consider having just two of them. The one which is active actually seems like a button that demands attention. It's basic design stuff. Tabs denote choices between active viewports, it should be unambiguous always which one is active. These hovering tabs are more like buttons which intuitively ask to be clicked

    https://github.com/black7375/Firefox-UI-Fix

    Try looking at the comparison screenshots in this repo. Or look up some images of firefox australis. You'll see how tabs are actually behaving like tabs and are denoting clearly which one is active by linking itself naturally to the viewport

    Edit: https://github.com/Glitchcode2447/Firefox-Australis-Theme

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •