Bug 87372 - A DOMCharacterDataModified event is dispatched in loading HTML.
Summary: A DOMCharacterDataModified event is dispatched in loading HTML.
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: EasyFix
Depends on:
Blocks:
 
Reported: 2012-05-24 04:46 PDT by Hayato Ito
Modified: 2019-02-06 09:18 PST (History)
7 users (show)

See Also:

Attachments
DOMCharacterDataModified event is wrongly dispatched. (131 bytes, text/html)
2012-05-24 04:47 PDT, Hayato Ito 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hayato Ito 2012-05-24 04:46:37 PDT 
The attached html file fires a DOMCharacterDataModified event. That should not be dispatched since we just load the HTML file.
Note that the HTML does not contain new-line at the end of file. If we add a new-line at the end of file, event won't be dispatched.
Comment 1 Hayato Ito 2012-05-24 04:47:27 PDT 
Created attachment 143787 [details]
DOMCharacterDataModified event is wrongly dispatched.
Comment 2 Hayato Ito 2012-05-24 06:10:21 PDT 
The related bug is here:
https://bugs.webkit.org/show_bug.cgi?id=86953 (This might not be viewable due to the security-restriction).
Comment 3 Adam Barth 2012-05-24 13:33:27 PDT 
We probably just need to change the parser to use an API that doesn't trigger this mutation event, like we do with parserAddChild.
Comment 4 Jae Hyun Park 2012-08-12 23:56:32 PDT 
This bug has been fixed in r125162.
Comment 5 Adam Barth 2012-08-13 10:25:08 PDT 
Marking as fixed per Comment #4.
Comment 6 Lucas Forschler 2019-02-06 09:18:33 PST 
Mass move bugs into the DOM component.