Closed Bug 169837 Opened 23 years ago Closed 16 years ago

scroll bookmarks but not other menu items in bookmarks menu

Categories

(Firefox :: Bookmarks & History, defect, P4)

defect

Tracking

()

RESOLVED WONTFIX
Future

People

(Reporter: asa, Unassigned)

References

Details

Attachments

(1 file)

we should just scroll the bookmarks, leaving the Add bookmarks and Manage bookmarks menu items visible.
possibly related: bug 98119
*** Bug 213094 has been marked as a duplicate of this bug. ***
Target Milestone: --- → Firebird1.0
taking QA contact, sorry about the bugspam
QA Contact: asa → mconnor
Priority: -- → P3
Target Milestone: Firefox1.0 → After Firefox 1.0
Attached patch patchSplinter Review
Well, this seems to work for me.
nominating since we have a patch. blake or ben, can you look at this?
Flags: blocking-aviary1.0?
-> vlad, can you take a look at the patch?
Assignee: p_ch → vladimir
Flags: blocking-aviary1.0? → blocking-aviary1.0+
Priority: P3 → P4
p4 priority - not a blocker. if a fully reviewed patch materializes, please nominate for aviary approval.
Flags: blocking-aviary1.0+ → blocking-aviary1.0-
This patch works but it also causes: 1. It's not possible to jump to bookmarks anymore (example, press "M" to jump to a bookmark named "Mozilla.org" 2. The menu automatically scrolls to the top everytime you open the bookmarks menu no matter where you left it off the last time Intended? Or accidental? :-P
These are minor inconveniences compared to the initial problem. Better implement the patch immmediately and look for a better solution later, if at all.
(In reply to comment #10) > These are minor inconveniences compared to the initial problem. Better implement > the patch immmediately and look for a better solution later, if at all. No, #1 from comment 9 is not minor. It's an accessibility issue that should not be sacrificed for this functionality.
(In reply to comment #11) > (In reply to comment #10) > > These are minor inconveniences compared to the initial problem. Better implement > > the patch immmediately and look for a better solution later, if at all. > > No, #1 from comment 9 is not minor. It's an accessibility issue that should not > be sacrificed for this functionality. I have been using Firebird/Firefox for a year and a half now without knowing that you could access a boolmark this way, and was very happy without it. I think that 1.0 aims at a much larger population than current users of Firefox, and that population will not miss what it did not know existed. On the other hand, the disappearance of the two commands is not a good design and should be corrected. The Jump to Bookmark could be reinstated later along with other bugs & improvements sidelined for 1.0.
Attachment #154295 - Flags: review?(vladimir)
This patches also makes it not possible to navigate the menu with keyboard How to reproduce: 1. Download and ubpack my build: http://pryan.org/firefox/jayfromtaiwan/1.0RC1/JTw-Fx-1_0_RC1-advA(169837).exe , which contains the patch 2. Open firefox and try pressing ALT-F Actual Result: - The "File" menu is opened, but the first option "New Window" is not highlighted, and pressing directional keys doesn't have any effects Expected Result: - "New Window" is highlighted and it's possible to navigate the menu using the keyboard My guess is this is related to the "vbox" change ... i may be wrong tho
*** Bug 272132 has been marked as a duplicate of this bug. ***
Assignee: vladimir → vladimir+bm
(In reply to comment #9) > 1. It's not possible to jump to bookmarks anymore (example, press "M" to jump to > a bookmark named "Mozilla.org" The following may not be too helpful, but I experimented with a variation of the patch by creating a special xbl that extended from "xbl:popup" and moved the unscrolled elements inside there: <binding id="bookmarksmenu" extends="chrome://global/content/bindings/popup.xml#popup"> <content> <xul:menuitem key="addBookmarkAsKb" ../> <xul:menuitem key="manBookmarkKb" ../> <xul:menuseparator/> <xul:arrowscrollbox> <children/> </xul:arrowscrollbox> </content> </binding> But I received the opposite effect of what you guys experienced. I could jump to the bookmarks entries with a key, but I could not reach the "Add Bookmark" and "Manage Bookmark" menuitems with the keyboard. Pressing up/down traversed the bookmarks only and wrapped around. I could access the add/manage bookmark with the mouse only. The reason I tried this particular variation was because I wanted to write an extension and wanted to avoid using "xul:vbox" which would require fidgeting with CSS skins (since the xul:vbox broke the CSS hierarchy). Also, "Add Bookmark" doesn't have an id so I could not override it in an overlay. > 2. The menu automatically scrolls to the top everytime you open the bookmarks > menu no matter where you left it off the last time I think this behavior is related to bug 280399. I'm also experiencing it with my variation too. The reason I'm not releasing my extension is because the automatic scrolling is even worse with the changes than without.
Nominating for 1.1 final.
Flags: blocking-aviary1.1?
Flags: blocking-aviary1.1? → blocking-aviary1.1-
Hardware: PC → All
Assignee: vladimir+bm → nobody
had someone ask about this in irc today. Is this being left to Places or did it just fall off the radar?
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → bookmarks
I'm going to WONTFIX this bug. No system menus every scroll just some of their entries, so this would break a strong platform convention across the board.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
If this is technically impossible, then too bad. But platform convention by itself is not very convincing as a reason. After all, platforms change, and Firefox could show how to improve them. In fact, Word menus, while not providing this sort of behavior, are dynamic, which is not conforming to any platform convention, and vaguely approach the idea expressed in this "bug". With conventions alone, there would have been no Internet, nor many other things...
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Martin - please do not reopen bugs that have been WONTFIXed without specifying a reason. Platform convention is a reason we've WONTFIXed bugs in the past because we want to feel native to users.
Status: REOPENED → RESOLVED
Closed: 17 years ago17 years ago
Resolution: --- → WONTFIX
See https://developer.mozilla.org/en/What_to_do_and_what_not_to_do_in_Bugzilla#Resolving_bugs_as_WONTFIX Afaik, you're not a module owner or peer for this component. And fwiw, IE's bookmark menu does scroll part of their entries, so that defeats you argument that no system menu does this.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
(In reply to comment #21) > No system menus every scroll just some of their entries, so this would break a > strong platform convention across the board. "break strong platform convention" on its own isn't a strong enough argument to reject something outright, since in many cases we defy platform conventions to provide a better user experience. If your argument is actually that the platform awkwardness and/or implementation cost outweighs the functionality win, then that's a different argument entirely, and much more justifiable.
I'm pretty sure that it is better to scroll the entire menu, as opposed to just the bookmarks area. Introducing new behaviors that are not conventions of the platform is good when it makes something significantly easier to use, but in cases where something is mostly the same, or only slightly better, I think the change is a net loss because users have habituated to the platform behavior. Also, when the user is visually scanning for a particular bookmark, isn't it better to devote more visual area to the list of bookmarks, instead of keeping unrelated commands around in the unlikely event that they want to change their overall goal?
IE does this kind of thing, so this is in fact a platform convention on windows at least.
Yeah, you're right. And even if IE hadn't done this, I really am all for completely disregarding the HIG when we want to make a UI better, or specialized for a particular use case. So platform convention is often only a consideration when there isn't a good reason for something to be different. But taking the discussion to a higher level, if the user is scanning the menu aren't they looking for a particular bookmark, and if they are looking for a particular bookmark, why keep the other unrelated commands around?
If the menu starts remembering what bookmark you were scrolled to, then it starts making sense. I don't think this would be an illogical next step. If people save related things in folders, and are going back and forth working on that thing it'd suck to have to keep scrolling to the bottom of the menu. Otherwise I have to agree, there's currently no use case where someone would want the commands *and* their bookmarks at the same time. I was originally thinking this would be cool, but I totally agree that scrolling the whole menu makes more sense because it lets you see more bookmarks at once.
(In reply to comment #28) > But taking the discussion to a higher level, if the user is scanning the menu > aren't they looking for a particular bookmark, and if they are looking for a > particular bookmark, why keep the other unrelated commands around? Yes, you're right. There was a time where it seemed useful to me, but I can't think of a reason currently anymore. It seems as what Opera9.60 is doing is a smarter and more efficient way to browse through the bookmarks. They also have a "Bookmark Page" item in every folder, which is a handy way to bookmark a page in a particular folder.
(In reply to comment #30) > They also have a "Bookmark Page" item in every > folder, which is a handy way to bookmark a page in a particular folder. That is what Add Bookmarks Here 2 makes, and i'm totally available to integrate that behaviour by default if UX team thinks that's useful.
Whiteboard: wontfix?
WONTFIXING per the analysis in comment #28. (In reply to comment #29) > If the menu starts remembering what bookmark you were scrolled to, then it > starts making sense. I don't think this would be an illogical next step. If > people save related things in folders, and are going back and forth working on > that thing it'd suck to have to keep scrolling to the bottom of the menu. This sounds like how I leave my desk messy, but know where *some* things are because I remember the state of the mess. #doingitwrong I think a better way to resolve this use-case would be to provide a better browsing/managing tool than a menu.
Status: REOPENED → RESOLVED
Closed: 17 years ago16 years ago
Resolution: --- → WONTFIX
Fwiw, I don't agree with the resolution of this bug.
Whiteboard: wontfix?
(In reply to comment #30) > (In reply to comment #28) > > But taking the discussion to a higher level, if the user is scanning the menu > > aren't they looking for a particular bookmark, and if they are looking for a > > particular bookmark, why keep the other unrelated commands around? > > Yes, you're right. There was a time where it seemed useful to me, but I can't > think of a reason currently anymore. > It seems as what Opera9.60 is doing is a smarter and more efficient way to > browse through the bookmarks. They also have a "Bookmark Page" item in every > folder, which is a handy way to bookmark a page in a particular folder. From my perspective, the only reason we even need to have the stuff at the top of the menu more quickly accessible anymore is to allow quicker access to the Bookmarks Library link. All other menu items listed there have faster alternatives elsewhere in the UI -- the star and RSS icons in the address bar, and right clicking the tab bar to select the option to bookmark all tabs. If there was a button I could add to the navigation bar to open the Bookmarks Library, it would save me a click, and I would never have to enter the Bookmarks menu for anything other than bookmarks.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: