- From: Kunihiko Sakamoto <notifications@github.com>
- Date: Wed, 28 Nov 2018 17:55:10 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/329@github.com>
こんにちはTAG! I'm requesting a TAG review of: - Name: imagesrcset and imagesizes attributes on link rel=preload - Specification URL: https://github.com/whatwg/html/pull/4048 and https://github.com/w3c/preload/pull/134 - Explainer, Requirements Doc, or Example code: [Explainer](https://docs.google.com/document/d/1wob4u9AER1kmUodqIEp78BuziSJChBl54A5ZRXPRCUI/edit?usp=sharing) - Tests: https://github.com/web-platform-tests/wpt/pull/9595, https://github.com/web-platform-tests/wpt/pull/14231 - Primary contacts: @irori, @domfarolino, @kinu Further details (optional): - Relevant time constraints or deadlines: we plan to ship this in Chrome 73, which branches in late-Jan 2019 and ships in March. - [x] I have read and filled out the [Self-Review Questionnare on Security and Privacy](https://www.w3.org/TR/security-privacy-questionnaire/). The assessment is no difference from existing link rel=preload. - [x] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/) You should also know that... Two issues have been raised in the past discussions: - `<picture>` use-case: It's not always easy or possible to create a set of `<link rel=preload>`s whose selection logic is equivalent to a `<picture>` element. This was discussed at TPAC 2018, and a summary is [here](https://github.com/w3c/preload/issues/131#issuecomment-433314755). - Preloads that depend on viewport dimensions would need to be delayed until the end of the `<head>` tag, where the viewport is locked. (This is not an issue specific to imagesrcset/imagesizes, since preload can have `media` attribute.) That means most `imagesrcset`s cannot be preloaded just by preprocessing HTTP headers. We plan to discuss the viewport issue separately from this one. We'd prefer the TAG provide feedback as (please select one): - [ ] open issues in our Github repo for each point of feedback - [ ] open a single issue in our Github repo for the entire review - [x] leave review feedback as a comment in this issue cc: @yoavweiss -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/329
Received on Thursday, 29 November 2018 01:55:32 UTC