Summary: | Web Inspector: an error is encountered when trying to delete nodes that have children | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | BJ Burg <bburg> | ||||||
Component: | Web Inspector | Assignee: | BJ Burg <bburg> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | bburg, commit-queue, graouts, joepeck, mattbaker, nvasilyev, timothy, webkit-bug-importer | ||||||
Priority: | P2 | Keywords: | InRadar | ||||||
Version: | WebKit Nightly Build | ||||||||
Hardware: | All | ||||||||
OS: | All | ||||||||
Attachments: |
|
Created attachment 280839 [details]
Proposed Fix
Comment on attachment 280839 [details] Proposed Fix Clearing flags on attachment: 280839 Committed r201843: <http://trac.webkit.org/changeset/201843> All reviewed patches have been landed. Closing bug. |
Created attachment 280836 [details] The bad code probably responsible It looks like we mistakenly try to index into a number, as in the screenshot, and we end up trying to create a DOMTreeElement with a null DOMNode. This eventually throws an exception which is dropped on the floor by DOMTreeManager._wrapClientCallback.