deliveryType (Resource Timing) · Issue #858 · w3ctag/design-reviews
こんにちは TAG-さん! I'm requesting a TAG review of deliveryType (part of Resource Timing). Resources on the web are usually fetched via HTTP (from the origin server), but in some cases they are known to be delivered from a cache or other buffer, in a way that affects loading performance. Insight into this is useful for authors understanding when these caches accelerate resource loading. The deliveryType
GitHub - WICG/view-transitions
When a user navigates on the web from Page-A to Page-B, the content that they are looking at changes suddenly and unexpectedly as the first page disappears and the new page jumps into view. This sequenced, disconnected user experience is disorienting and results in a higher-cognitive load as the user is forced to piece together how they got to where they came from. Additionally, this jarring exper
GitHub - WICG/navigation-api: The new navigation API provides a new interface for navigations and session history, with a focus on single-page application navigations.
Formerly known as the app history API The web's existing history API is problematic for a number of reasons, which makes it hard to use for web applications. This proposal introduces a new API encompassing navigation and history traversal, which is more directly usable by web application developers. Its scope is: initiating navigations, intercepting navigations, and history introspection and mutat
handwriting-recognition/explainer.md at main · WICG/handwriting-recognition
Handwriting is a widely used input method, one key usage is to recognize the texts when users are drawing. This feature already exists on many operating systems (e.g. handwriting input methods). However, the web platform as of today doesn't have this capability, the developers need to integrate with third-party libraries (or cloud services), or to develop native apps. We want to add handwriting re
webappsec-permissions-policy/document-policy-explainer.md at master · w3c/webappsec-permissions-policy · GitHub
Document Policy This is a proposal for a mechanism, similar to Feature Policy, to cover those kinds of features which don't involve delegation of permission to trusted origins; features which are more about configuring a document, or removing features (sandboxing) from a document or a frame. Start with Examples! Performance best practices The simplest example is a site which wants to enforce some
Webbundle によるサブリソース取得の最適化 | blog.jxck.io
Intro WebBundle を用いてサブリソースのみを Bundle する、Subresource Bundle の策定と実装が進んでいる。 これを用いると、複数サブリソースの取得を一回の fetch で行うことができ、RTT を減らしつつも個別に取得したかのようにキャッシュを制御できる。 現時点での仕様と実装を解説する。 Intent to Prototype: Subresource loading with Web Bundles Subresource Bundling WebBundle の初期の仕様は、HTML を頂点としたページ全体をまとめる方向で始まった。 WebBundle によるコンテンツの結合と WebPackaging | blog.jxck.io これをサブリソース(JS, CSS, Img etc)に対して利用できるようにする仕様だ。 HTML 自体は普通に
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Specification Review: FetchLater API · Issue #887 · w3ctag/design-reviews
GitHub - ben-allen/locale-extensions
docs/beacon_api.md at main · darrenw/docs
fenced-frame/explainer at master · WICG/fenced-frame
editing/docs/EditContext/explainer.md at gh-pages · alexkeng/editing
GitHub - WICG/shared-storage: Explainer for proposed web platform Shared Storage API
scheduling-apis/explainers/prioritized-post-task.md at main · WICG/scheduling-apis
Intent to Prototype: App history API
GitHub - privacycg/storage-partitioning: Client-Side Storage Partitioning
Support `AbortSignal`s in `addEventListener`s options to unsubscribe from events? · Issue #911 · whatwg/dom
GitHub - slightlyoff/history_api: Some ideas for to improve history state on the web
GitHub - privacycg/is-logged-in: The IsLoggedIn API
Detect inactive users with the Idle Detection API | Capabilities | Chrome for Developers
request-post-animation-frame/explainer.md at main · WICG/request-post-animation-frame