Closed
Bug 618008
Opened 14 years ago
Closed 14 years ago
Separator spree in the Web Developer menu
Categories
(Firefox :: Menus, defect)
Tracking
()
RESOLVED
FIXED
Firefox 4.0b8
People
(Reporter: dao, Assigned: dao)
References
()
Details
(Whiteboard: [target-betaN])
Attachments
(2 files)
31.10 KB,
image/png
|
faaborg
:
ui-review+
|
Details |
1.29 KB,
patch
|
Gavin
:
review+
Gavin
:
approval2.0+
|
Details | Diff | Splinter Review |
There are three separators for four items, which seems pointless. When every item has its own group, you might as well put them all in one. I suggest we either do that or try to really group them in a useful way, e.g. Web Console + View Page Source (strict developer tools) and Character Encoding + Work Offline (other random stuff which developers or non-developers may or may not use).
Assignee | ||
Updated•14 years ago
|
Summary: Separator spree in the Developer menu → Separator spree in the Web Developer menu
Comment 1•14 years ago
|
||
wow, I'm not sure how I missed this, thanks for filing. I don't really see any really obvious way to group these, so perhaps just go with all one group?
Updated•14 years ago
|
Assignee | ||
Comment 2•14 years ago
|
||
note that I enabled the inspector here, it's currently disabled by default
Attachment #496777 -
Flags: ui-review?(faaborg)
Comment 3•14 years ago
|
||
Comment on attachment 496777 [details]
keeping one separator
sure, to me it kind of feels like things versus other things, but nonetheless this will help people build up some spatial memory
Attachment #496777 -
Flags: ui-review?(faaborg) → ui-review+
Assignee | ||
Comment 4•14 years ago
|
||
Updated•14 years ago
|
Attachment #497259 -
Flags: review?(gavin.sharp)
Attachment #497259 -
Flags: review+
Attachment #497259 -
Flags: approval2.0+
Updated•14 years ago
|
Whiteboard: [target-betaN]
Assignee | ||
Comment 5•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/c141a4b27049
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 4.0b8
You need to log in
before you can comment on or make changes to this bug.
Description
•