over to joe and timeless, the owner and qa for DOM inspector.
Assignee: ben → hewitt
QA Contact: sairuh → timeless
1. techpubs doesn't document inspector so they don't care about this bug. 2. how would someone install the inspector sidebar (today) without this pref panel? 3. why do you care? if you just don't want to see the panel then you should be able to use userChrome.css to hide it. if you don't want the bloat then you don't have to install inspector or you can build your own version without the panel.
No longer blocks: 121324
Component: Preferences → DOM Inspector
> 3. why do you care? i don't care. but i've read so many times about how is bloated the Preferences window, and i think that we can resign to *six* prefs about how to blink a selected element in a document; Sure, if mozteam remove this panel, another way to install the sidebar tab is needed, but i think there are at least two (very) easy ways to do that; 1. like any other tab; 2. from the inspector itself (menu item) > if you don't want the bloat then you don't have to install inspector i love the DOM Inspector.
Assignee: hewitt → caillon
I don't think the prefs panel is useless. DOMI is well within its rights to have a prefs panel because it has prefs. There are other hidden prefs that we can expose in the prefs UI which we don't currently. Rather than remove the prefs panel, I'd much rather add the other prefs and make the panel more useful. On a separate note, DOM Inspector has nothing to do with the bloat of preferences. If there is pref bloat, complain to others.
The prefs panel will need to be redesigned for use with Firebird. There will be no need to remove the settings.
To be fair, the prefs _are_ useless. There are two at the moment: The length of time an element should blink (!), and the ability to install the sidebar. The first can go altogether (I mean, come on), the second should just be a menu item in the DOM inspector or some such.
Severity: normal → enhancement
Mass re-assigning bugs to email@example.com
Assignee: caillon → dom.inspector
Is this even valid anymore?
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → INVALID
What's invalid here? Inspector still ships its useless pref dialog. You can reach it even in Firefox by pasting this url into the location bar: chrome://inspector/content/prefs/pref-inspector.xul It doesn't work properly though... I don't think anybody would disable blink selected element. And why should border color/width and blink duration/speed need UI?
Status: RESOLVED → REOPENED
OS: Windows 2000 → All
Hardware: PC → All
Resolution: INVALID → ---
(In reply to comment #11) > What's invalid here? Inspector still ships its useless pref dialog. You can > reach it even in Firefox by pasting this url into the location bar: > chrome://inspector/content/prefs/pref-inspector.xul > It doesn't work properly though... > > I don't think anybody would disable blink selected element. And why should > border color/width and blink duration/speed need UI? That's what I was wondering. So, ideally the preferences should be toggled by their menu entries under view then?
The View menu offers to switch "Blink Selected Element" on/off. That's already more than enough. Nobody needs UI in a dialog or in the View menu for the other blinking prefs, see comment 7. And instead of the button to install the sidebar, it could hook up the sidebar in Firefox's View->Sidebar menu.
(In reply to comment #13) > The View menu offers to switch "Blink Selected Element" on/off. That's already > more than enough. Nobody needs UI in a dialog or in the View menu for the other > blinking prefs, see comment 7. > And instead of the button to install the sidebar, it could hook up the sidebar > in Firefox's View->Sidebar menu. The install button doesn't even work. I'm wondering if we should remove that code as well. Adding Alex to CC since he should know more about this.
Assignee: dom-inspector → nobody
Status: REOPENED → NEW
QA Contact: timeless → dom-inspector
(In reply to comment #14) > The install button doesn't even work. It works for SeaMonkey. I don't think it was ever intended to work for Firefox, although maybe some would find it useful?
You need to log in before you can comment on or make changes to this bug.