<story><title>Populating the page: how browsers work (2020)</title><url>https://developer.mozilla.org/en-US/docs/Web/Performance/How_browsers_work</url></story><parent_chain></parent_chain><comment><author>bloopernova</author><text>That was really informative, but it raised a question for me:&lt;p&gt;It described the browser as single threaded, but then talked about multiple concurrent tasks. Aren&amp;#x27;t those threads?&lt;p&gt;One more question: are there any browsers that use multiple threads to lay out the various object models and render the page? If it&amp;#x27;s been found to be too difficult, what were the issues?</text></comment>
<story><title>Populating the page: how browsers work (2020)</title><url>https://developer.mozilla.org/en-US/docs/Web/Performance/How_browsers_work</url></story><parent_chain></parent_chain><comment><author>hkt</author><text>Neat. I&amp;#x27;m trying to write a browser, of a kind, which is focused on only presenting content, navigation, and an index of content where appropriate. I&amp;#x27;ll try to incorporate things like this into my thinking.&lt;p&gt;(Browser is here, very early stages, not appropriate for any kind of use really while I move to fltk: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;jmthackett&amp;#x2F;freeflow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;jmthackett&amp;#x2F;freeflow&lt;/a&gt; )</text></comment>