WICG/priority-hints
A browser API to enable developers signal the priorities of the resources they need to download.
BikeshedNOASSERTION
Issues
- 7
Ok to archive?
#77 opened by marcoscaceres - 2
Broken references in Priority Hints
#73 opened by dontcallmedom-bot - 5
Add a bit about the developer tools
#25 opened by domfarolino - 3
Address the scheduler use-case
#23 opened by yoavweiss - 9
`importance` is horribly long
#35 opened by mnot - 33
- 2
- 14
- 0
Abstract is horribly short
#65 opened by martinthomson - 4
Integer values for importance attribute
#44 opened by canadaduane - 3
Priority Hints API with AMP-HTML
#42 opened - 3
- 5
- 8
Questions following initial implementation
#10 opened by yoavweiss - 2
Link header support
#21 opened by addyosmani - 5
- 2
- 2
Processing model
#52 opened by martinthomson - 2
Priority is not magic
#55 opened by martinthomson - 1
Spec's source markup is broken
#57 opened by tabatkins - 5
Relative or absolute
#51 opened by martinthomson - 0
HTTP/2 and HTTP/3 priority spec
#50 opened by martinthomson - 11
- 2
Bring back examples into the explainer
#41 opened by yoavweiss - 3
- 1
Document "safety" of applying priority hints
#29 opened by addyosmani - 2
Responsive Image Support?
#46 opened by pmeenan - 5
Merge priority hints with lazy loading?
#47 opened by pmeenan - 3
Archive this?
#43 opened by marcoscaceres - 3
Mobile browser support
#45 opened by mziemer21 - 6
Coercive misuse by advertisers?
#34 opened by hadleybeeman - 1
- 3
- 2
Consider radio power state?
#30 opened by triblondon - 16
Group names bikeshed
#7 opened by yoavweiss - 6
importance vs priority
#27 opened by Malvoz - 7
Consider lowering the number of values
#17 opened by yoavweiss - 6
Converge to a single `group` attribute, with values indicating before and after
#6 opened by yoavweiss - 0
Start on ReSpec document
#18 opened by addyosmani - 1
- 2
- 0
Add a TL;DR to the explainer
#8 opened by yoavweiss