Add a meta explainer #82
Conversation
|
@mmocny @clelland would you mind taking a pass? @anniesullie too if you're interested. |
|
FYI @philipwalton as well - feedback appreciated! |
|
@brendankenny can you take a look as well? |
| internal [browser task | ||
| queues](https://source.chromium.org/chromium/chromium/src/+/261ad5cb51f1dbf3385af53218512796602100ed:content/browser/scheduler/browser_task_queues.h). | ||
|
|
||
| 1. **user-blocking**: tasks that block a user from interacting with and using the app. This could be |
There was a problem hiding this comment.
FWIW, it's never been totally clear to me what is meant by "block a user from interacting with and using the app". I've interpreted this to mean "tasks that will run before the next frame is presented", but I'm not 100% sure that's accurate since that's precisely what sync code does.
So I guess my suggestion here is to more clearly define what "blocking" means.
There was a problem hiding this comment.
Naming is hard. I tried rephrasing this as "essential to user experience" and added a bit more details (including synchronous vs. user-blocking). LMK if this helps or if I should try to expand more.
| **Example: The `taskpriority` `<script>` attribute.** | ||
| ```html | ||
| <!-- Ensure the script execution doesn't get in the way of other pending work. --> | ||
| <script async taskpriority="background" ...> |
Co-authored-by: Philip Walton <philipwalton@users.noreply.github.com>
| internal [browser task | ||
| queues](https://source.chromium.org/chromium/chromium/src/+/261ad5cb51f1dbf3385af53218512796602100ed:content/browser/scheduler/browser_task_queues.h). | ||
|
|
||
| 1. **user-blocking**: tasks that block a user from interacting with and using the app. This could be |
There was a problem hiding this comment.
Naming is hard. I tried rephrasing this as "essential to user experience" and added a bit more details (including synchronous vs. user-blocking). LMK if this helps or if I should try to expand more.
Add an explainer tying together the various Scheduling API proposals, which TAG mentioned requested, and which I agree would be helpful.