Closed Bug 160857 Opened 23 years ago Closed 15 years ago

move DOM Inspector & JS Debugger to Window menu

Categories

(SeaMonkey :: UI Design, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: bugs4hj, Assigned: samir_bugzilla)

Details

The 'DOM Inspector' and 'JavaScript Debugger' menu items should be moved from 'Tools/Web Development' to the Window menu (or move composer to the tool menu). off record: I wonder why nobody came up with 'Managers' for the 'manager' menu items in the Tools menu and moved the Manage Bookmarks to that same menu ;)
Summary: [RFE] mode DOM Inspector & JS Debugger to Window menu → [RFE] move DOM Inspector & JS Debugger to Window menu
why should we move it ? Only developers need the dom Inspector and that why it's in Tools/web Development. many normal (not developer) people use the composer to create simple html documents but they never use Dom Inspector or JS debugger. -> User Interface Design (mpt should decide)
Assignee: Matti → mpt
Component: Browser-General → User Interface Design
QA Contact: asa → zach
Severity: normal → enhancement
But following that logic, only developers need Composer, yet that is in the Windows menu.... That said, I think it makes more sense where it is, we don't need more clutter in the (poorly named, IMO) Windows menu. ->XPApps, since user interface design is deprecated and this is more of an apps problem anyway.
Assignee: mpt → sgehani
Component: User Interface Design → XP Apps
OS: Windows NT → All
QA Contact: zach → paw
Hardware: PC → All
Summary: [RFE] move DOM Inspector & JS Debugger to Window menu → move DOM Inspector & JS Debugger to Window menu
Product: Core → Mozilla Application Suite
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.