[Webkit-unassigned] [Bug 44381] New: ASSERTION FAILED: m_type == Uninitialized || m_type == Character

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=44381

           Summary: ASSERTION FAILED: m_type == Uninitialized || m_type ==
                    Character
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: tonyg at chromium.org
                CC: eric at webkit.org, abarth at webkit.org


Created an attachment (id=65027)
 --> (https://bugs.webkit.org/attachment.cgi?id=65027)
Testcase

This DOM triggers an ASSERT:

FAIL<iframe onload="document.write('PASS')">

ASSERTION FAILED: m_type == Uninitialized || m_type == Character
(/work/WebKit/WebCore/html/HTMLToken.h:117 void WebCore::HTMLToken::ensureIsCharacterToken())

I suspect this is closely related to the fix from bug 43055. Adding a document.open() before the document.write() avoids the ASSERT. I haven't debugged, but it looks like Document::open() bails out if parser->isExecutingScript().

I'll be on vacation next week, so I probably won't be able to get to this in a timely manner.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.