July 2021 - webkit-dev - lists.webkit.org

Re: [webkit-dev] Request for position: CSS @font-face descriptor advance-override
by Dominik Röttsches 09 Aug '21

09 Aug '21

As an update to our intent here. as posted by Xiaocheng earlier, we're planning to ship the size-adjust descriptor <https://drafts.csswg.org/css-fonts-5/#size-adjust-desc>. On Mon Feb 22 16:50:28 PST 2021 Xiaocheng Hu xiaochengh(a)chromium.org wrote: Hi webkit-dev, > This is a request for WebKit's position on a new descriptor > 'advance-override' of the CSS @font-face rule. > This is a new feature that the CSSWG just added into CSS Fonts Level 5 for > reducing layout shifting caused by web fonts. Chrome has already > implemented it in M90 behind a flag. > > Explainer: > https://gist.github.com/xiaochengh/3aae8a97d1b0388c8e701819b63e2c49 > Spec: https://drafts.csswg.org/css-fonts-5/#font-metrics-override-desc > May I assume https://github.com/w3c/csswg-drafts/pull/5991, authored by > Myles, as a positive signal? > Thank you!

2 1

Commit Queue down for maintainence
by Aakash Jain 28 Jul '21

28 Jul '21

Hi Everyone, We just took commit-queue bots offline for some maintenance. I will send another update when they are back online. Thanks Aakash

1 1

Fixed merged commits in GitHub Mirror
by Jonathan Bedard 28 Jul '21

28 Jul '21

Morning folks, Last Friday, git-svn failed us and merged two commits together (this was the cause of the incorrect commits.webkit.org <http://commits.webkit.org/> links folks saw over the last few days). I’ve fixed it, but that fix involves force-pushing, if you have a GitHub checkout, you might need to `git reset HEAD~125 —hard` and re-pull to fix the problem (be aware of local commits you may have, because `git reset —hard` will throw those out). Thank you for your patience, Jonathan

1 0

Request for Position: EyeDropper API
by Ionel Popescu 22 Jul '21

22 Jul '21

Hi webkit-dev, This is a request for Webkit's position on EyeDropper API. Explainer: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/EyeDropper/expl… TAG review: https://github.com/w3ctag/design-reviews/issues/587 Chrome Status entry: https://chromestatus.com/feature/6304275594477568 Please let us know if you have any feedback! Thanks, Ionel

1 0

Request for position: CSS tree-scoped at-rule names and refs (for @font-face etc.)
by Xiaocheng Hu 19 Jul '21

19 Jul '21

Hi webkit-dev, This is a request for WebKit's position on CSS tree-scoped names and references for @font-face, @keyframes, @counter-style and other name-defining at-rules. Spec: https://drafts.csswg.org/css-scoping/#shadow-names Explainer: https://drafts.csswg.org/css-scoping/#example-f1503361 https://drafts.csswg.org/css-scoping/#example-ee72cb37 Existing WebKit bug: I'm not aware of any WebKit bug for exactly the same issue. Please let me know if I missed any. There are some related bugs as listed below: https://bugs.webkit.org/show_bug.cgi?id=72461 https://bugs.webkit.org/show_bug.cgi?id=186837 Summary: It has been a long standing issue on how name-defining at-rules should be handled across shadow tree boundaries. The existing behaviors are non-interoperable between browsers, and even inconsistent in the same browser between different rules [1]. Following a recent CSSWG resolution [2], a new and reasonable behavior has been proposed. Chrome is planning to implement this new behavior, starting with the @counter-style rule [3]. [1] https://wiki.csswg.org/spec/css-scoping [2] https://github.com/w3c/csswg-drafts/issues/1995#issuecomment-848941922 [3] https://chromestatus.com/feature/5716198446596096

1 0

Request for position: Web App Note Taking - New Note URL
by Glen Robertson 19 Jul '21

19 Jul '21

Hi, I am requesting a standards position signal on Web App Note Taking - New Note URL This proposed spec allows web app authors to declare a `note_taking: { new_note_url: <URL> }` member in their web app manifest. User agents can use the member to enable OS integrations. Explainer: https://github.com/WICG/manifest-incubations/blob/gh-pages/note_taking-expl… Spec: https://wicg.github.io/manifest-incubations/index.html#note_taking-member Chromestatus: https://chromestatus.com/feature/5205972320518144 Let me know if you have any questions. Thanks -Glen Robertson (Chrome OS web apps platform team)

1 0

Ryan Haddad is now a WebKit Reviewer
by Aakash Jain 15 Jul '21

15 Jul '21

Hello All, I would like to announce that Ryan Haddad is now a WebKit Reviewer. His expertise is tools and infrastructure. Please join me in congratulation him. 🎉 Congratulations Ryan! 🎉 -Aakash

1 0

Request for position: CSS scrollbar-gutter
by Felipe Erias 15 Jul '21

15 Jul '21

Hi webkit-dev, This is a request for WebKit's position on the CSS "scrollbar-gutter" property. The spec status is Working Draft. This feature is already implemented in Chrome behind a flag. Spec: https://drafts.csswg.org/css-overflow-4/#scrollbar-gutter-property Explainer: https://github.com/felipeerias/scrollbar-gutter-explainer Existing WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=167335 Summary: The scrollbar-gutter property provides control over the presence of scrollbar gutters (the space which may be reserved to display a scrollbar). This gives Web authors more agency over how their layouts interact with the scrollbars provided by the browser, so they can e.g. prevent excessive layout changes as content expands while avoiding unwanted visuals when scrolling isn't needed. Thanks! Best. Felipe

3 7

Request for Position on supporting more flex-basis keywords
by David Grogan 14 Jul '21

14 Jul '21

Hi WebKit devs, I'm going to make the 'flex-basis' property (and its part of the 'flex' shorthand) in Blink honor the css-sizing-3 keywords 'min-content,' 'max-content', and 'fit-content', and the css-flexbox-1 keyword 'content'. Neither Blink nor WebKit currently support those keywords in flexbox. This is a request for Webkit's position on implementing those keywords in flexbox. Thanks, David

1 0

Request for position: EME MediaKeySession Closed Reason
by Xiaohan Wang (王消寒) 09 Jul '21

09 Jul '21

This is a request for WebKit's position on the "EME MediaKeySession Closed Reason" proposal: *Links* - W3C EME spec issue/explainer: https://github.com/w3c/encrypted-media/issues/473 - W3C EME spec Pull Request: https://github.com/w3c/encrypted-media/pull/487 - Previous Media Working Group meeting discussion on this topic (with Jer Noble): https://lists.w3.org/Archives/Public/public-media-wg/2020Sep/0004.html Summary A MediaKeySessionClosedReason is proposed to indicate the reason for EME MediaKeySession closure, and the `closed` attribute would return a `Promise<MediaKeySessionClosedReason>` instead of the current `Promise<void>`. Motivation The current EME spec says "the CDM may close a session at any point, such as when the session is no longer needed or when system resources are lost". However, there's no way to specify the exact reason for session closure. In some cases, this is part of normal user flow, e.g. user close laptop lid to put the device into sleep mode, where the player should resume playback. In some other cases, this is due to some unrecoverable fatal error. This proposal updates the `closed` attribute on MediaKeySession to provide a MediaKeySessionClosedReason so that the JavaScript player can handle session closure differently based on the reasons. *Contact email* xhwang at chromium.org Looking forward to your feedback! Best, Xiaohan

1 3