<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Handle meta viewport in HTMLPreloadScanner"
href="https://bugs.webkit.org/show_bug.cgi?id=144640#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Handle meta viewport in HTMLPreloadScanner"
href="https://bugs.webkit.org/show_bug.cgi?id=144640">bug 144640</a>
from <span class="vcard"><a class="email" href="mailto:yoav@yoav.ws" title="Yoav Weiss <yoav@yoav.ws>"> <span class="fn">Yoav Weiss</span></a>
</span></b>
<pre>When asking around in the WebKit contributor meeting, it was suggested that unit testing is possible to do in such a way. Now that I'm aware of /Tools/TestWebKitAPI/Tests/WebCore it does seems significantly better. I'll move the unit test there.
I tried to write tests that do show the end-user effect using LayoutTests, but couldn't find a way to turn on <meta name=viewport> awareness in tests, since it is a no-op on desktop.
If there's a way to that in layout tests, I'll be happy to add them as well.
And finally, the patch's goal is to avoid the preloader loading the wrong resource when the HTML is of the form:
```
<html><head>
<script src="something.js">// This is a blocking script, so the preloader kicks in</script>
<meta name=viewport content="SOME VIEWPORT CHANGING VALUE">
<body>
<img srcset="400px.jpg 400w, 800px.jpg 800w">
```</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>