Bug 16551 - Disable (temporarily remove) DOM nodes
Summary: Disable (temporarily remove) DOM nodes
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Enhancement
Assignee: Nobody
Keywords: InRadar
Depends on:
Reported: 2007-12-21 00:17 PST by Danny Bloemendaal
Modified: 2014-12-14 20:46 PST (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Danny Bloemendaal 2007-12-21 00:17:57 PST
Again I name Firebug as an example. There you can disable css properties by clicking directly to the left of the property. It will show a little blocked icon and grays out the property. This is such a convenient way to see what that property does with your page. But it doesn't remove it. You can easily turn it on again.

In addition I'd like to propose the same for dom nodes. Sometimes you want to turn off a node temporarily in a similar fashion as described above with properties. Very handy.

Oh, and.. as I reported earlier as a feature request (http://bugs.webkit.org/show_bug.cgi?id=16528), that summary of course must show that you disabled these properties/nodes.
Comment 1 Timothy Hatcher 2007-12-26 23:54:24 PST
Bug 14377 covers disabling CSS properties. We will use this bug to track disabling DOM nodes, a neat idea!
Comment 2 Adam Roben (:aroben) 2008-01-29 11:10:55 PST
Comment 3 Brian Weinstein 2009-11-20 17:01:06 PST
They can be deleted currently, but not disabled. I don't see an option to disable but not delete DOM nodes in Firebug.
Comment 4 Timothy Hatcher 2009-11-20 17:14:21 PST
Disabling nodes would be unique to Web Inspector.
Comment 5 Adam 2010-08-19 15:48:26 PDT
This idea seems to be close enough on topic.

If you delete them, being able to undo (ctrl-z) the delete.

Being disabled would be a better option though and would probably remove the need to delete any.