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
HTML Standard
Firefox3.5+Safari4+Chrome4+Opera10.5+Edge79+Edge (Legacy)12+Internet Explorer8+Firefox Android6+Safari iOS?Chrome Android?WebView Android37+Samsung Internet?Opera Android11+ 12.1 Introduction This section is non-normative. This specification introduces two related mechanisms, similar to HTTP session cookies, for storing name-value pairs on the client side. [COOKIES] The first is designed for scena
Expose `history.index` in addition to `history.length` · Issue #2710 · whatwg/html
An integer history.index < history.length would be a big simplification for many history-based routers. Currently, many of these push/replace a "fake" first state when the app starts up only to record such an index. There might be some privacy/security concerns, but I can't think of any negatives that are not already possible with history.length, history.back(), etc. History state is used often fo
Estimating Available Storage Space | Blog | Chrome for Developers
tl;dr Chrome 61, with more browsers to follow, now exposes an estimate of how much storage a web app is using and how much is available via: if ('storage' in navigator && 'estimate' in navigator.storage) { navigator.storage.estimate().then(({usage, quota}) => { console.log(`Using ${usage} out of ${quota} bytes.`); }); } Modern web apps and data storage When you think about the storage needs of a m
Intersection Observer comes to Firefox – Mozilla Hacks - the Web developer blog
What do infinite scrolling, lazy loading, and online advertisements all have in common? They need to know about—and react to—the visibility of elements on a page! Unfortunately, knowing whether or not an element is visible has traditionally been difficult on the Web. Most solutions listen for scroll and resize events, then use DOM APIs like getBoundingClientRect() to manually calculate where eleme
The WHATWG Blog — Progressing Streams
Please leave your sense of logic at the door, thanks! Progressing Streams July 5th, 2017 by Adam Rice in What's Next Back in 2014 we announced the Streams Standard. It's about time for an update on where we are and what's coming up. Streaming the response to fetch() via the response.body attribute was standardized last year and is now implemented in several major browsers. Recently streaming uploa
An inside look at Quantum DOM Scheduling – Mozilla Hacks - the Web developer blog
Use of multi-tab browsing is becoming heavier than ever as people spend more time on services like Facebook, Twitter, YouTube, Netflix, and Google Docs, making them a part of their daily life and work on the Internet. Quantum DOM: Scheduling is a significant piece of Project Quantum, which focuses on making Firefox more responsive, especially when lots of tabs are open. In this article, we’ll desc
Cooperative Scheduling of Background Tasks (W3C Candidate Recommendation 31 January 2017)
requestIdleCallback() Cooperative Scheduling of Background Tasks W3C Working Draft 28 June 2022 More details about this document This version: https://www.w3.org/TR/2022/WD-requestidlecallback-20220628/ Latest published version: https://www.w3.org/TR/requestidlecallback/ Latest editor's draft:https://w3c.github.io/requestidlecallback/ History: https://www.w3.org/standards/history/requestidlecallba
Glimmer
Fast and light-weight UI components for the web Available for use within Ember.js and standalone apps. Use in Ember.js: Install Glimmer packages in your Ember app: npm install --dev @glimmer/component @glimmer/tracking Generate a Glimmer Component ember generate my-component -gc See the Ember Octane Guides to learn more! Standalone Glimmer App: Please note this is experimental Install the Ember bu
Understanding the Critical Rendering Path | bitsofcode
When a browser receives the HTML response for a page from the server, there are a lot of steps to be taken before pixels are drawn on the screen. This sequence the browsers needs to run through for the initial paint of the page is called the "Critical Rendering Path". Knowledge of the CRP is incredibly useful for understanding how a site's performance can be improved. There are 6 stages to the CRP
History API - Scroll restoration | Blog | Chrome for Developers
Using the History API to manage your URLs is awesome and, as it happens, a crucial feature of good web apps. One of its downsides, however, is that scroll positions are stored and then, more importantly, restored whenever you traverse the history. This often means unsightly jumps as the scroll position changes automatically, and especially so if your app does transitions, or changes the contents o
Cooperative Scheduling with requestIdleCallback – Mozilla Hacks - the Web developer blog
TL;DR: requestIdleCallback support has landed in Firefox Nightly, with plans to ship in Firefox 52. The messiest aspect of building interactive websites boils down to this: the main thread is the same as the UI thread. Rendering the page and responding to user actions happens in contention with computation, network activity, and manipulation of the DOM. Some of these things can be moved to another
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Add scrollOptions for Element.focus() by jihyerish · Pull Request #2787 · whatwg/html
Simple EventListenerOptions feature detection · Issue #491 · whatwg/dom
Abort controller by jakearchibald · Pull Request #437 · whatwg/dom
GitHub - airbnb/browser-shims: Browser and JS shims used by Airbnb.
Removing event listeners through an identifier · Issue #208 · whatwg/dom
http://www.jomendez.com/2017/01/25/copy-clipboard-using-javascript/
Adds requestIdleCallback to vdom/component by paullewis · Pull Request #409 · preactjs/preact
hidden - HTML: HyperText Markup Language | MDN