Summary: | Assertion failure seen running some mixed-content tests | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | mitz | ||||
Component: | WebKit2 | Assignee: | mitz | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | ||||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
mitz
2013-12-17 11:33:58 PST
Created attachment 219434 [details]
Remove a bogus assertion
Comment on attachment 219434 [details] Remove a bogus assertion View in context: https://bugs.webkit.org/attachment.cgi?id=219434&action=review > Source/WebKit2/UIProcess/PageLoadState.cpp:-275 > - ASSERT(m_uncommittedState.url.startsWith("https:", false)); This is a new assertion that seem OK to remove for now, but the code looks very surprising and inconsistent. canRunInsecureContent is invoked with m_document, and canDisplayInsecureContent is invoked with topFrame->document() Fixed in <http://trac.webkit.org/r160718>. |