Summary: | dispatchDocumentElementAvailable is fired for fragment parsing on XML and XHTML documents | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Matt Perry <mpcomplete> | ||||
Component: | Layout and Rendering | Assignee: | Matt Perry <mpcomplete> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | commit-queue, eric, hyatt, pfeldman, timothy | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | OS X 10.5 | ||||||
Attachments: |
|
Description
Matt Perry
2010-01-20 14:54:33 PST
Created attachment 47378 [details]
small patch with tests
Comment on attachment 47378 [details]
small patch with tests
Why does the test case need to be in userscripts? Can't this be tested with a normal script-tests test?
(In reply to comment #2) > (From update of attachment 47378 [details]) > Why does the test case need to be in userscripts? Can't this be tested with a > normal script-tests test? It doesn't look like it. I think the only side effect of calling dispatchDocumentElementAvailable is that user scripts are injected. Comment on attachment 47378 [details]
small patch with tests
LGTM.
Comment on attachment 47378 [details] small patch with tests Clearing flags on attachment: 47378 Committed r53917: <http://trac.webkit.org/changeset/53917> All reviewed patches have been landed. Closing bug. |