<?xml version="1.0"?>
<rss version="2.0" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:neowin="https://www.neowin.net/">
	<channel>
		<title>Neowin News Feed for: Whatwg</title>
		<link>https://www.neowin.net/news/tag/whatwg/</link>
        <atom:link href="https://www.neowin.net/news/rss/whatwg/" rel="self" type="application/rss+xml" />
		<description>Neowin News Feed for: Whatwg</description>
		<language>en-us</language>
		<generator>Neowin Ignition News</generator>
		<managingEditor>editor@neowin.net (Managing Editor)</managingEditor>
		<webMaster>developers@neowin.net (Neowin Developers)</webMaster>
		<ttl>5</ttl>
		<image>
			<title>Neowin.net</title>
			<url>https://www.neowin.net/images/pegasus/icon.png</url>
			<link>https://www.neowin.net</link>
		</image>
		        <item>
            <title>Firefox 75 Nightly comes with lazy loading flag for images and iframes</title>
            <link>https://www.neowin.net/news/firefox-75-nightly-comes-with-lazy-loading-flag-for-images-and-iframes/</link>
            <description>&lt;div style="float:left;margin-right:10px;"&gt;&lt;img src="https://cdn.neowin.com/news/images/uploaded/2019/09/1568742281_firefoxnew4_medium.jpg" alt="" /&gt;&lt;/div&gt;Mozilla has added support for lazy loading of images and iframes in the latest Nightly build of Firefox. It&amp;#039;s disabled by default but enabling it to try out is simple enough, here&amp;#039;s how to do it. &lt;a href="https://www.neowin.net/news/firefox-75-nightly-comes-with-lazy-loading-flag-for-images-and-iframes/"&gt;Read more...&lt;/a&gt;</description>
            <author>Paul Hill</author>
            <pubDate>Sat, 15 Feb 2020 10:32:01 +0000</pubDate>
            <guid>https://www.neowin.net/news/firefox-75-nightly-comes-with-lazy-loading-flag-for-images-and-iframes/</guid>
            <media:thumbnail url="https://cdn.neowin.com/news/images/uploaded/2019/09/1568742281_firefoxnew4_story.jpg" width="760" height="428" />
            <neowin:tags>#Firefox #LazyLoading</neowin:tags>            <neowin:twitter>@ziks_99</neowin:twitter>        </item>
                <item>
            <title>W3C and WHATWG agree on single HTML and DOM specs</title>
            <link>https://www.neowin.net/news/w3c-and-whatwg-agree-on-single-html-and-dom-specs/</link>
            <description>&lt;div style="float:left;margin-right:10px;"&gt;&lt;img src="https://cdn.neowin.com/news/images/uploaded/2018/03/1521458709_html5_logo_medium.jpg" alt="" /&gt;&lt;/div&gt;The W3C and WHATWG organisations have agreed to start working towards a common HTML and DOM specification. The W3C described there being two standards as harmful to the wider community. &lt;a href="https://www.neowin.net/news/w3c-and-whatwg-agree-on-single-html-and-dom-specs/"&gt;Read more...&lt;/a&gt;</description>
            <author>Paul Hill</author>
            <pubDate>Tue, 28 May 2019 14:52:01 +0000</pubDate>
            <guid>https://www.neowin.net/news/w3c-and-whatwg-agree-on-single-html-and-dom-specs/</guid>
            <media:thumbnail url="https://cdn.neowin.com/news/images/uploaded/2018/03/1521458709_html5_logo_story.jpg" width="760" height="428" />
            <neowin:tags>#W3C #WHATWG</neowin:tags>            <neowin:twitter>@ziks_99</neowin:twitter>        </item>
        	</channel>
</rss>
