sebmarkbage
commented
1 year ago That's correct. An example:
<div>
<h1>Hello</h1>
<div class="loading" aria-busy="true">
Loading...
</div>
</div>
<script>
navigation.stopIndicator();
</script>
<script>
moar stuff...
</script>The main use case is that you have lots of more content that will stream in at the bottom of the HTML document but you've effectively already finished loading or are showing a custom loading state to the user already. This can be because the bottom include data or meta data that isn't visible to the user anyway (e.g. "hydration data") or it can be HTML that gets injected into the page later in slots that already have inline loading states and don't need a global one.
Although even better would be to have it work without JavaScript. E.g. some placeholder in the HTML would be enough.
E.g. <? done ?> in this example.
<div>
<h1>Hello</h1>
<div class="loading" aria-busy="true">
Loading...
</div>
</div>
<? done ?>
<script>
moar stuff...
</script>It could potentially also be an attribute annotation to indicate that when an element "ends" the essence of the document is already done.
domenic
@sebmarkbage was mentioning that in some of their server streaming HTML cases, the user agent loading spinner continues long after the important parts of the page have loaded.
If developers had some way of early terminating the loading spinner with JavaScript, that could provide a better user experience. This would not involve modifying actual loading behavior, merely the loading spinner indicator.
Correct me if I misunderstood the request Seb.