It drives me bonkers! The browser already has a way to display loading and it’s even respectful of back buttons.
I get that in a select few cases, for real time content, it makes sense to handle the loading inside the page. But if all you’re doing is displaying an article, I don’t need you to load a framework page that the loads the article.
They mean the browsers page loading status. They’re saying if your content is static, it should be static or loaded in the page document through a CMS, not through an asynchronous call to an api after the page and js framework and load.
It drives me bonkers! The browser already has a way to display loading and it’s even respectful of back buttons.
I get that in a select few cases, for real time content, it makes sense to handle the loading inside the page. But if all you’re doing is displaying an article, I don’t need you to load a framework page that the loads the article.
You mean like when an HTP request is not completely fulfilled? Is there an API for this “native” loading display of the browser?
You can tell by the shooting stars behind the big “N”.
They mean the browsers page loading status. They’re saying if your content is static, it should be static or loaded in the page document through a CMS, not through an asynchronous call to an api after the page and js framework and load.