Ensure that parser doesn't attach children that have been removed by JavaScript event handlers.
Created attachment 64048 [details] Patch
Comment on attachment 64048 [details] Patch Oh man... This patch looks correct, but it enscarifies me.
Looks good to me as well. Mitz, Hyatt - have any thoughts on this?
I land this yes? :)
I think so. :)
The change looks correct to me. Andy, if you have any test cases that you’ve developed while investigating bug 40742, other than the regression test, you can verify that this patch doesn’t regress them.
(In reply to comment #6) > The change looks correct to me. Andy, if you have any test cases that you’ve developed while investigating bug 40742, other than the regression test, you can verify that this patch doesn’t regress them. Looks good to me. I checked in several additional tests covering this behavior in http://trac.webkit.org/changeset/61744, and it looks like those tests are passing. Dimitri, for my own edification, I'm curious how the lazy-attach optimization affects <link> elements. I had convinced myself it wasn't when writing this patch, but I might have missed something.
I think we'd like to lazy attach everything. Once you have one element that doesn't support lazy attach, you have to break out of your lazy slumber for all it's ancestors.
Comment on attachment 64048 [details] Patch Clearing flags on attachment: 64048 Committed r65281: <http://trac.webkit.org/changeset/65281>
All reviewed patches have been landed. Closing bug.