Summary: | Node::InDetachFlag could be removed. | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Hajime Morrita <morrita> | ||||||||
Component: | DOM | Assignee: | Hajime Morrita <morrita> | ||||||||
Status: | RESOLVED FIXED | ||||||||||
Severity: | Normal | CC: | darin, webkit.review.bot | ||||||||
Priority: | P2 | ||||||||||
Version: | 528+ (Nightly build) | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Bug Depends on: | |||||||||||
Bug Blocks: | 77860 | ||||||||||
Attachments: |
|
Description
Hajime Morrita
2012-05-09 01:26:19 PDT
Created attachment 140888 [details]
Patch
Comment on attachment 140888 [details]
Patch
Looks like we could easily remove isDetach() as it has just one client that probably never gets hit.
Created attachment 140891 [details]
Patch
Comment on attachment 140891 [details]
Patch
r=me
Created attachment 141147 [details]
Patch for landing
Comment on attachment 141147 [details] Patch for landing Clearing flags on attachment: 141147 Committed r116644: <http://trac.webkit.org/changeset/116644> All reviewed patches have been landed. Closing bug. What proves inDetach can never be true? Can’t some of that code in detach result in calls out to arbitrary JavaScript? I am not sure this is correct. Hi Darin, thanks for the feedback! (In reply to comment #8) > What proves inDetach can never be true? Can’t some of that code in detach result in calls out to arbitrary JavaScript? I am not sure this is correct. The point is that this is not arbitrary detach() but Node::detach(). I checked the code and there is no such code path. But I agree that I might be too optimistic. I'll post a follow up at Bug 86157. |