16551 2007-12-21 00:17:57 -0800 Disable (temporarily remove) DOM nodes 2014-12-14 20:46:40 -0800 1 1 1 Unclassified WebKit Web Inspector (Deprecated) 528+ (Nightly build) All All RESOLVED WONTFIX InRadar P2 Enhancement --- 1 danny.bloemendaal webkit-unassigned burg bweinstein phazei oldest_to_newest 64925 0 danny.bloemendaal 2007-12-21 00:17:57 -0800 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. 65342 1 timothy 2007-12-26 23:54:24 -0800 Bug 14377 covers disabling CSS properties. We will use this bug to track disabling DOM nodes, a neat idea! 68659 2 aroben 2008-01-29 11:10:55 -0800 <rdar://problem/5712900> 165516 3 bweinstein 2009-11-20 17:01:06 -0800 They can be deleted currently, but not disabled. I don't see an option to disable but not delete DOM nodes in Firebug. 165527 4 timothy 2009-11-20 17:14:21 -0800 Disabling nodes would be unique to Web Inspector. 267009 5 phazei 2010-08-19 15:48:26 -0700 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.