Thread:Talk:Athena/Some intuitive likes and dislikes/reply (4)

''With the "context" navigation at the bottom and the "edit" action at the top, and some other actions again at the bottom, we may be negatively impacting navigation efficiency. In Vector, it's fairly easy to switch modes, take page-level actions, etc. with relatively high navigational efficiency.''


 * Regarding Vector's tabs (and Monobook's, actually, before it): I actually find the opposite to be true with regards to new users trying to understand what is going on.
 * I've heard varying comments from users (many of whom say that they can't even find the edit button). They see links that may or may not be tabs (since the UI isn't very clear on that fact).  This is further compounded by the fact that it appears that there are two tabs active at the same time (because the "sub-tab" metaphor isn't well-described).
 * I think that the strengths of "in-line sub-tabs" will become clearer in a functional prototype.

''The fixed floating/disappearing nature of the different elements doesn't yet intuitively "click" for me, and I've seen floating elements get in the way quite a bit. Obviously I'd love to try this in an interactive prototype, though.''
 * I've seen similar things work well on several sites but not as "heavy weight" as this is. Obviously, it's a known, workable pattern in mobile devices.  Facebook uses floating elements rather well.  Again, this is a prototype-noticable thing.