Closed Bug 135210 Opened 23 years ago Closed 22 years ago

This Frame flyout context menu: duplicate "w" and "f" accesskeys

Categories

(SeaMonkey :: UI Design, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.4beta

People

(Reporter: bugzilla, Assigned: shliang)

References

()

Details

(Keywords: access, Whiteboard: [adt3])

Attachments

(1 file, 2 obsolete files)

(deleted), patch
jag+mozilla
: review+
sspitzer
: superreview+
sspitzer
: approval1.4+
Details | Diff | Splinter Review
found using 2002.04.03.09-static mozilla build on linux rh7.2. 1. go to a web page with frames, eg, http://wired.com/ 2. bring up the context menu (either for the page content, selection or a link). 3. observe the following duplicate menu accesskeys: a. for "w": Sho_w Only This Frame Open Frame in New _Window b. for "f": Bookmark This _Frame Save _Frame As... expected: a. per the spec at http://mozilla.org/projects/ui/communicator/framework/contextmenus/cmrev2-3.html#Anchor-45980, shouldn't the "Show Only This Frame" item be removed? if yes, then that'll remove the duplicate "w"... b. per the spec, the menu accesskey for "Bookmark This Frame" should be the "m", as in "Book_mark This Frame". correcting this would take care of the duplication of "f".
kw-o-rama...
Keywords: access, adt1.0.0, nsbeta1
QA Contact: paw → sairuh
[show only this frame] was left out of the spec because it was too similar to [open frame in new window] and [open frame in new tab]. the differences between these two operations were so little, that we had to decide on one or the other in order to keep menus short.
Removing adt1.0.0. When there is a patch, r= and sr= add the keywork for approval.
Keywords: adt1.0.0
Nav triage team: nsbeta1+/adt2
Keywords: nsbeta1nsbeta1+
Whiteboard: [adt2]
Blocks: 135841
I strongly disagree that Show Only This Frame should be left out. Why would Open Frame in New Window be used more?
renominating for reconsideration, this isn't critical accessibility work. Users who must use the keyboard can still hit Open Frame in New Window by hitting the down arrow twice, which isn't much harder than hitting w once, and this isn't even a frequently used menuitem.
Keywords: nsbeta1+nsbeta1
nsbeta1- per Nav triage team.
Keywords: nsbeta1nsbeta1-
Target Milestone: --- → mozilla1.1alpha
the presence of both methods opens a depth vs. breadth debate. i attempted to broadly cover real in-use scenarios, rather than offer deeper control of only a few. this is of course applied generally, but it is how we manage to keep menus short. the frame situation is unique addition of the submenu so if this item indeed has some sort of hidden advantage that was overlooked, it wouldn't be too painful to squeeze it in. Just give me more than the obvious, "i use it all the time and i simply love it"
Keywords: nsbeta1-nsbeta1
Target Milestone: mozilla1.1alpha → ---
"Open Frame in New Window" is mainly there for the purpose of breaking out of frames, isn't it? I contend that the common usage pattern for this would be to open frame in new window and then close the original window. With Show Only This Frame, we attempted to bypass this extra step by opening the frame in the same window. The item serves the common purpose of helping to break out of a frameset, which currently is an option the website offers (if it offers). I can't see of any reason why you'd break a frame out into a new window but still want the original frameset open. (I still don't see why this is critical for machv/beta1).
It isn't; this is way down the list of things we need to worry about. Marlon, the triage team acknowledges that this deviation from the spec is a defect, but it doesn't come close to being required for MachV. nsbeta1-/1.1.
Keywords: nsbeta1nsbeta1-
Whiteboard: [adt2]
Target Milestone: --- → mozilla1.1alpha
Attached patch fix (obsolete) (deleted) — Splinter Review
Comment on attachment 88760 [details] [diff] [review] fix r=db48x
Attachment #88760 - Flags: review+
nominating --has patch, to boot. :)
Keywords: nsbeta1-nsbeta1, patch, review
Nav triage team: nsbeta1+/adt3
Keywords: nsbeta1nsbeta1+
Whiteboard: [adt3]
Nav triage team: nsbeta1-
Keywords: nsbeta1+nsbeta1-
why was this minused? there's a patch here --unless it's obsolete. over shuehan, but reassign as needed.
Assignee: blaker → shliang
Keywords: nsbeta1-nsbeta1
Nav triage team: nsbeta1+/adt3
Keywords: nsbeta1nsbeta1+
Flags: blocking1.3?
Target Milestone: mozilla1.1alpha → mozilla1.4beta
Flags: blocking1.3? → blocking1.3-
*** Bug 194901 has been marked as a duplicate of this bug. ***
Flags: blocking1.4b?
Attachment #88760 - Flags: superreview?(alecf)
Comment on attachment 88760 [details] [diff] [review] fix sr=alecf
Attachment #88760 - Flags: superreview?(alecf) → superreview+
I ask that you back this out now. This discussion was not over, yet a patch was made and checked in. This is not acceptable behavior. Where is the MOA?
Comment on attachment 88760 [details] [diff] [review] fix This patch is incomplete. The entity can't be removed without removing the XUL using it.
Attachment #88760 - Flags: superreview+ → superreview-
Flags: blocking1.4b?
Flags: blocking1.4b-
Flags: blocking1.4?
we'd consider a fix but not blocking on this
Flags: blocking1.4? → blocking1.4-
Attached patch patch (obsolete) (deleted) — Splinter Review
Attachment #88760 - Attachment is obsolete: true
Attachment #123025 - Flags: review?(jaggernaut)
Comment on attachment 123025 [details] [diff] [review] patch I think blake makes a strong enough case to keep "Show Only This Frame" for now.
Attachment #123025 - Flags: review-
Attached patch patch (deleted) — Splinter Review
ok then, keep menuitem and just change accesskeys
Attachment #123025 - Attachment is obsolete: true
Attachment #123041 - Flags: review?(jaggernaut)
Comment on attachment 123041 [details] [diff] [review] patch r=jag No need for the change in nsContextMenu.js though.
Attachment #123041 - Flags: review?(jaggernaut) → review+
Attachment #123025 - Flags: review?(jaggernaut)
r=varga
Comment on attachment 123041 [details] [diff] [review] patch sr/a=sspitzer
Attachment #123041 - Flags: superreview+
Attachment #123041 - Flags: approval1.4+
checked in
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
vrfy'd fixed with 2003.05.19.08. thanks, shuehan!
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: