https://github.com/w3ctag/design-reviews/issues/881 I've filed a tag review
(hopefully filled it all out correctly)
On Wednesday, 2 August 2023 at 00:03:46 UTC+1 Chris Harrelson wrote:
> Hi Luke, could you file for a TAG review for this feature?
>
> On Tue, Aug 1, 2023 at 7:56 AM 'David Bolter'
Contact emailsdizha...@chromium.org
ExplainerNone
Specificationhttps://drafts.csswg.org/css-writing-modes-4/#block-flow
Summary
CSS property writing-mode should be enabled for form controls elements as
it will allow lines of text to be laid out horizontally or vertically. With
this feature, we
Hi Luke, could you file for a TAG review for this feature?
On Tue, Aug 1, 2023 at 7:56 AM 'David Bolter' via blink-dev <
blink-dev@chromium.org> wrote:
> I agree with Mike that the incremental entropy available is probably
> acceptable. I don't have any data/awareness of demand for this setting b
On Tue, 1 Aug 2023 at 23:44, Mike Taylor wrote:
> On 8/1/23 7:54 AM, 'Mingyu Lei' via blink-dev wrote:
>
> Contact emails le...@chromium.org, fer...@chromium.org
>
> Explainer None
>
> Specification None
>
> Given that WebKit is shipping this and we would like to, any reason to not
> document thi
I need to add some context to this I2S. This has already shipped.
I just noticed a couple of days ago that this was not behind a flag and had
already shipped. The work was done in prep for CCNS/BFCache, so in my head
it was all coming together under one I2S. Apologies for that,
F
On Tue, 1 Aug
Hello API Owners,
Please let us know if there are any questions we can answer. This feature
is planned to ship in M117 (branching Aug 8). Requesting approval to ship.
Thanks in advance.
-Ajay
On Tuesday, August 1, 2023 at 9:40:59 AM UTC-7 rei...@chromium.org wrote:
> On Tue, Aug 1, 2023, 06
LGTM1
On Tuesday, August 1, 2023 at 1:27:31 PM UTC-7 Philip Rogers wrote:
> Contact emails...@chromium.org
>
> ExplainerNone
>
> Specificationhttps://drafts.fxtf.org/css-masking/#the-clip-path
>
> Summary
>
> Clip-path supports values to control the clip's reference
> box, making clip-path easi
Contact emails...@chromium.org
ExplainerNone
Specificationhttps://drafts.fxtf.org/css-masking/#the-clip-path
Summary
Clip-path supports values to control the clip's reference
box, making clip-path easier to use. These box values can be used alongside
basic shapes (for example, clip-path: circl
Yep, sounds good. Thanks for the heads up!
On 8/1/23 1:24 PM, Christian Biesinger wrote:
FYI, we are extending this origin trial to Android (excluding webview)
in Chrome 117. I understand we do not need a new LGTM for that.
Christian
On Fri, Jun 9, 2023 at 10:00 AM Mike Taylor
wrote:
FYI, we are extending this origin trial to Android (excluding webview) in
Chrome 117. I understand we do not need a new LGTM for that.
Christian
On Fri, Jun 9, 2023 at 10:00 AM Mike Taylor wrote:
> LGTM to experiment from M116 to M119 inclusive.
> On 6/8/23 5:38 PM, Christian Biesinger wrote:
>
On Tue, Aug 1, 2023, 06:01 Balazs Engedy wrote:
> For clarity, are the per-device permissions persisted across visits? If
> so, what device attribute(s) do we use to form a device identifier to key
> that permission on?
>
Yes, the Bluetooth device MAC address.
On Thursday, July 27, 2023 at 7:06
Contact emails
aric...@chromium.org, miketa...@chromium.org, bing...@chromium.org
Specification
https://httpwg.org/http-extensions/draft-ietf-httpbis-rfc6265bis.html#name-the-expires-attribute
Summary
Since M104 cookies newly created or updated with an expiration date would
have that date capp
I agree with Mike that the incremental entropy available is probably
acceptable. I don't have any data/awareness of demand for this setting but
it is at least some signal that it is available on Windows, Mac, iOS
(thanks Luke). I'll ping some folks and come back (or they will) if there
is info
On 8/1/23 7:54 AM, 'Mingyu Lei' via blink-dev wrote:
Contact emails
le...@chromium.org, fer...@chromium.org
Explainer
None
Specification
None
Given that WebKit is shipping this and we would like to, any reason to
not document this behavior to the Clear-Site-Data
For clarity, are the per-device permissions persisted across visits? If so,
what device attribute(s) do we use to form a device identifier to key that
permission on?
On Thursday, July 27, 2023 at 7:06:37 PM UTC+2 Reilly Grant wrote:
> That behavior is to be expected. The "2" and ":59:NN PM" are
LGTM2
/Daniel
On 2023-07-24 11:48, Ari Chivukula wrote:
Wanted to bump review for this, thanks!
~ Ari Chivukula (Their/There/They're)
On Tue, Jul 18, 2023 at 2:00 PM Rick Byers wrote:
Seems like a pretty minor and straightforward addition to an
already shipped feature to me. LGTM1
Contact emailsle...@chromium.org, fer...@chromium.org
ExplainerNone
SpecificationNone
Summary
When performing browsing data removal (e.g. via
chrome://settings/clearBrowserData, hard reload, or the `Clear-Site-Data `
header), the disk and in-memory cache for the HTTP response will be
cleared. I
Opened https://github.com/GoogleChrome/developer.chrome.com/pull/6965 to
also reflect this change in the developer-facing docs.
On Tue, Aug 1, 2023 at 9:59 AM Adam Rice wrote:
> WebSocketStream is not a shipped API so normally we wouldn't announce
> changes, but I know some people are trying it
WebSocketStream is not a shipped API so normally we wouldn't announce
changes, but I know some people are trying it out using the experimental
flag, so I am sending this PSA.
>From Chromium version 117.0.5914.0 onwards, the "connection" attribute has
been renamed to "opened".
Where previously you
19 matches
Mail list logo
