-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @clelland.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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" ...> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is really cool!
Co-authored-by: Philip Walton <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the feedback, @philipwalton.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.