You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of how this started came from other systems. Where I used <section> to put things in a container and either build templates consistently for static site, or pull in dynamic content in what is now called JAM stack...
Looks like I should have just made <div> soup. This is not an issue I've been aware of until now. This mistake only affects heading ordering for a minority of browsers, but it's still not ideal.
The text was updated successfully, but these errors were encountered:
A lot of how this started came from other systems. Where I used
<section>to put things in a container and either build templates consistently for static site, or pull in dynamic content in what is now called JAM stack...An article by Bruce Lawson suggests that this can impact heading ordering for some older browsers.
https://www.smashingmagazine.com/2020/01/html5-article-section/
Looks like I should have just made
<div>soup. This is not an issue I've been aware of until now. This mistake only affects heading ordering for a minority of browsers, but it's still not ideal.The text was updated successfully, but these errors were encountered: