Hm, I'm against using up/down arrows. I find them very misleading in this case. We’re looking at a tree structure in the markup view that can be navigated in arbitrary order (e.g. with the element picker). Those arrows suggest to me that I would navigate it up and down, not backward and forward. Left/right on the other hand is a known backward/forward navigation pattern, learned for example on the general browser toolbar.
Bug 1537666 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hm, I'm against using up/down arrows. I find them very misleading in this case. We’re looking at a tree structure in the markup view that can be navigated in arbitrary order (e.g. with the element picker). Those arrows suggest to me that I would navigate it up and down, not backward and forward. And in reality, the previous selected element can be below the current one (=> pressing arrow up would navigate the view down). Left/right on the other hand is a known backward/forward navigation pattern, learned for example on the general browser toolbar.
Hm, I'm against using up/down arrows. I find them very misleading in this case. We’re looking at a tree structure in the markup view that can be navigated in arbitrary order (e.g. with the element picker). Those arrows suggest to me that I would navigate it up and down (previous/next), not backward and forward. And in reality, the previous selected element can be below the current one (=> pressing arrow up would navigate the view down). Left/right on the other hand is a known backward/forward navigation pattern, learned for example on the general browser toolbar.