Manual priority control of resource fetching
I think there would be value in exposing a way to manually specify the priority of resource requests. Both via HTML (perhaps using a priority attribute) and via JS (fetch() prioritization). The attribute based approach could be helpful for when you need to load resources with a particular priority before any JS is run at all. Today, we have <link rel=preload>, however as is often not powerful enou
Adding a [disabled] attribute to <a>s
A partial archive of discourse.wicg.io as of Saturday February 24, 2024. TL;DR: I propose to add a disabled attribute to the <a> element, which would work the same as it already does for the <button> element. See also http://w3bug.com/28673 Background: Interchangeability Lemma 1: <button> and <a> are largely interchangeable. Visually, <a>s can be styled into buttons and <button>s can be styled to
Proposal: Sandbox Policy
A partial archive of discourse.wicg.io as of Saturday February 24, 2024. TL;DR: The existing HTML spec provides sandboxing capability that restricts abilities of iframed content. We would like to propose extending this: Allow the policy to be applied to the top-level document with granular opt-in Allow the top-level policy set in (1) to propagate to subframes Allow the policy to run in report-only
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Location.canonical proposal - APIs - WICG
