[Webkit-unassigned] [Bug 48201] New: REGRESSION Zimbra email compose is broken with the HTML5 parser

[bugzilla-daemon at webkit.org]

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

           Summary: REGRESSION Zimbra email compose is broken with the
                    HTML5 parser
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Keywords: Regression
          Severity: Normal
          Priority: P2
         Component: HTML DOM
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: mihaip at chromium.org
                CC: eric at webkit.org, abarth at webkit.org


To reproduce:

1. Go to http://testzimbra.com/
2. Log in with username "zm1023yyxhm" and password "hvtpki"
3. Wait for all the UI to load
4. Click on the "New" button under the "Mail" tab to bring up a compose window

Expected result:
1. Compose window that you can type in

Actual result:
1. No editable area for the body of the email

This appears to be intermittent, so you may need to try it a few times to trigger it. Having an empty cache seems to make it more likely to happen. Using nightly builds I narrowed it down to the range r64727 to r64636. http://trac.webkit.org/changeset/64712, which enabled the HTML5 tree builder, was in that range. I verified that that particular change was responsible.

This is a beast of an app to reduce, but as far as I can tell, there's some sort of race condition with the body compose iframe. It has a src of http://demo2.zimbra.com/zimbra/public/blank.html. With the HTML5 parser change, I often see the compose area flash before it's replaced by the empty blank.html frame. Without the HTML5 change, "Failed to load resource: cancelled" message in the console about the blank.html frame. I'm guessing the app is registering an onload handler and enabling designMode on the frame and filling it with the new email template, and implicitly disabling the load of the blank.html source. That last part is no longer happening with the HTML5 parser, which is why blank.html is clobbering the compose area.

With things like bug 43423 I see that the HTML5 parser is affecting how events are fired for frames, but I don't know much else about this.

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