<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Allow the page to render before <link> stylesheet tags in body"
href="https://bugs.webkit.org/show_bug.cgi?id=149157">149157</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Allow the page to render before <link> stylesheet tags in body
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>WebKit Nightly Build
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>OS</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>Layout and Rendering
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>jaffathecake@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>Test page: <a href="https://wiki-offline.jakearchibald.com/wiki/Hulk_Hogan?use-url-flags&prevent-sw=1&no-css-async-hack=1">https://wiki-offline.jakearchibald.com/wiki/Hulk_Hogan?use-url-flags&prevent-sw=1&no-css-async-hack=1</a>
Results:
Chrome <a href="http://www.webpagetest.org/video/compare.php?tests=150424_57_12PJ-r:1-c:0">http://www.webpagetest.org/video/compare.php?tests=150424_57_12PJ-r:1-c:0</a>
IE <a href="http://www.webpagetest.org/video/compare.php?tests=150424_NH_12XE-r:1-c:0">http://www.webpagetest.org/video/compare.php?tests=150424_NH_12XE-r:1-c:0</a>
In the test above, the page has inline CSS, 'defer'd javascript, then the HTML for the top toolbar. After the toolbar, there's a <link> for some CSS (load.php in the waterfall), followed by the article content.
In Chrome/Safari, the preparser discovers the CSS and blocks further rendering, including content before the <link>. IE will allow content before the <link> to render, and block afterwards. Firefox is similar to IE
The spec is unclear here, but developers seem to want this behaviour <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=27303#c37">https://www.w3.org/Bugs/Public/show_bug.cgi?id=27303#c37</a>, and there are hacks to work around the current block-everything behaviour <a href="https://github.com/filamentgroup/loadCSS">https://github.com/filamentgroup/loadCSS</a>
Chrome is looking to align with Firefox & IE on this <a href="https://code.google.com/p/chromium/issues/detail?id=481122#c17">https://code.google.com/p/chromium/issues/detail?id=481122#c17</a>
Further explanation of the problem & benefits of this solution <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=27303#c36">https://www.w3.org/Bugs/Public/show_bug.cgi?id=27303#c36</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>