ure/5177580990496768?gate=5074696605007872
This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.
--
Rune Lillesveen
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group a
On Tue, May 20, 2025 at 1:38 PM Yoav Weiss (@Shopify) <
yoavwe...@chromium.org> wrote:
>
>
> On Tue, May 20, 2025 at 1:32 PM Rune Lillesveen
> wrote:
>
>> On Tue, May 20, 2025 at 10:47 AM Yoav Weiss (@Shopify) <
>> yoavwe...@chromium.org> wrote:
>>
On Tue, May 20, 2025 at 10:47 AM Yoav Weiss (@Shopify) <
yoavwe...@chromium.org> wrote:
>
>
> On Wed, May 14, 2025 at 6:10 PM Philip Jägenstedt
> wrote:
>
>> On Wed, May 14, 2025 at 5:21 PM Rune Lillesveen
>> wrote:
>>
>>> On Tue, May 13, 2025 at
On Tue, May 13, 2025 at 9:20 AM Rune Lillesveen
wrote:
> On Tue, May 13, 2025 at 8:34 AM Rune Lillesveen
> wrote:
>
>> On Tue, May 13, 2025 at 7:43 AM Domenic Denicola
>> wrote:
>>
>>> I'm very slightly worried about the cases which we seem to accep
On Tue, May 13, 2025 at 8:34 AM Rune Lillesveen
wrote:
> On Tue, May 13, 2025 at 7:43 AM Domenic Denicola
> wrote:
>
>> I'm very slightly worried about the cases which we seem to accept, but
>> the latest on the CSSWG thread suggests we should disallow. Namely,
>>
safer to be conservative and wait for the
resolution, since for @container there are clear use cases and and a more
or less obvious behavior in that context.
On Tuesday, May 13, 2025 at 6:37:14 AM UTC+9 Mike Taylor wrote:
>
>> LGTM1
>> On 5/9/25 9:47 AM, Rune Lillesveen
rototype:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67c70d35.2b0a0220.36af1.0007.GAE%40google.com
This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.
--
Rune Lillesveen
--
You received this message because you are subscribed to the Google Groups
On Sat, Feb 8, 2025 at 7:26 PM Mike Taylor wrote:
> On 2/7/25 8:19 AM, Rune Lillesveen wrote:
> 2 years ago Apple indicated that they would prefer official position
> requests for anything related to Interop (see
> https://groups.google.com/a/chromium.org/g/blink-dev/c/HxqAcgnTs8o/m/
k (e.g., changing to naming or structure of
the API in a non-backward-compatible way).
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/4728308937523200?gate=5083464346632192
This intent message was generated by Chrome Platform Status
<https://chromestatus.com/
ences if they match the spec.
>
> Thanks for mentioning this, I've got a PR for this:
> https://github.com/web-platform-tests/wpt/pull/50056
>
Remember to also update the rel=help links to actual spec references.
--
Rune Lillesveen
--
You received this message because you are subscr
nce, IIUC,
https://wpt.live/css/css-scoping/has-slotted-flattened-001.tentative.html
should match the selector because a slot is assigned to another slot, not
because nodes are flattened through.
>
> Estimated milestones
> Shipping on desktop 133
> Shipping on Android 133
> Shipping on
at 7:22 AM Mike Taylor
>> wrote:
>>
>>> LGTM1
>>> On 11/21/24 4:12 AM, Rune Lillesveen wrote:
>>>
>>> On Wed, Nov 13, 2024 at 10:38 AM Rune Lillesveen
>>> wrote:
>>>
>>>> Four issues are opened against the spec:
>>
apshot
Otherwise there is no particular interaction between scroll-state() queries
and scroll-timelines different from other CSS features.
On Wednesday, November 13, 2024 at 1:38:36 AM UTC-8 Rune Lillesveen wrote:
>
>> Four issues are opened against the spec:
>>
>> https://github.
On Wed, Nov 13, 2024 at 10:38 AM Rune Lillesveen
wrote:
> Four issues are opened against the spec:
>
> https://github.com/w3c/csswg-drafts/issues/11181
> https://github.com/w3c/csswg-drafts/issues/11182
> https://github.com/w3c/csswg-drafts/issues/11183
> https://github.co
aming from
'overflowing' to 'scrollable':
https://github.com/w3c/csswg-drafts/issues/11182
Two of the others are convenience keyword additions, and the last one is a
non-behavioral editorial change to the spec.
On Tue, Nov 12, 2024 at 2:12 PM Rune Lillesveen
wrote:
> Contac
ium.org/d/msgid/blink-dev/CACuPfeQyse1btL_jhkEQJT9WCsR2sndRo8i%3DyHmzgPu6sDpDOw%40mail.gmail.com
This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.
--
Rune Lillesveen
--
You received this message because you are subscribed to the Google Groups
&q
uld I copy the signals and TAG review entries from
https://chromestatus.com/feature/5124922471874560 ?
This is a minor change to allow anchor-size() in margins and insets based
on a CSSWG resolution after the realization that it was fine to allow the
function in those properties too.
Best,
>
> Alex
>
&g
as generated by Chrome Platform Status
<https://chromestatus.com/>.
--
Rune Lillesveen
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubsc
quot; syntax component name in @property.
>
This is also the case for registerProperty(), right?
--
Rune Lillesveen
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
On Fri, Aug 23, 2024 at 7:09 AM Domenic Denicola
wrote:
> LGTM1, with nit about Chrome Platform Status info accuracy below.
>
> On Fri, Aug 16, 2024 at 10:31 PM Rune Lillesveen
> wrote:
>
>>
>> Flag name on chrome://flagsCSSFlatTreeContainer
>>
>
> I navi
Contact emailsfuth...@chromium.org
ExplainerNone
Specificationhttps://drafts.csswg.org/css-conditional-5/#container-queries
Landed PR: https://github.com/w3c/csswg-drafts/pull/10701
Summary
Look up query containers in the flat tree ancestor order instead of
shadow-including order. The specifica
e web compat/interop risk (e.g., changing to naming or structure of
the API in a non-backward-compatible way).
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/4909742688567296
This intent message was generated by Chrome Platform Status
<https://chromestatus
ay).
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5105423604776960
This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.
--
Rune Lillesveen
--
You received this message because you are subscribed to the Google Group
iche this is and that WebKit and Gecko have
> >> both shipped this without any apparent compat fallout, I agree the
> >> compat risk is very low. I'm ok treating it as a bugfix, but please
> >> circle back here (and consider using your killswitch) if you hear of
> >
duce web compat/interop risk (e.g., changing to naming or structure of
the API in a non-backward-compatible way).
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/4875749691752448
This intent message was generated by Chrome Platform Status
<https://chromestatu
rrors
>
Please remove base_feature: "None" from runtime_enabled_features.json5
--
Rune Lillesveen
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
On Tue, Oct 24, 2023 at 1:58 AM Mike Taylor wrote:
> Hey Rune,
> On 10/20/23 9:30 AM, Rune Lillesveen wrote:
>
> Contact emails futh...@chromium.org, andr...@chromium.org
>
> Explainer None
>
> Specification
> https://drafts.css-houdini.org/css-properties-values-api-1/
ucture of
the API in a non-backward-compatible way).
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5184552188510208
This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.
--
Rune Lillesveen
--
You received this
s
entry accordingly.
>
> (Not that I object to this change tho)
>
> -- Emilio
>
> On 10/4/23 11:08, Rune Lillesveen wrote:
> >
> > Contact emails
> >
> > futh...@chromium.org <mailto:futh...@chromium.org>, andr...@chromium.org
> >
On Wed, Oct 4, 2023 at 11:08 AM Rune Lillesveen
wrote:
> Contact emailsfuth...@chromium.org, andr...@chromium.org
>
> ExplainerNone
>
> Specification
> https://drafts.css-houdini.org/css-properties-values-api-1/#syntax-strings
>
> Summary
>
> Supports using the
he API in a non-backward-compatible way).
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5142205606133760
This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.
--
Rune Lillesveen
--
You received this message because you
ium.org/g/blink-dev/c/jiuxWVJEmqs/m/u0dMUmA4AwAJ
x: https://groups.google.com/a/chromium.org/g/blink-dev/c/FsD97U77tss
--
Rune Lillesveen
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receivin
08
This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.
--
Rune Lillesveen
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send
d here:
https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/layout/custom_scrollbar.cc;l=134-162;drc=d708cc843536cc344f0f7679a978634cc14d6153;bpv=1;bpt=1?q=CustomScrollbar::&ss=chromium%2Fchromium%2Fsrc
Hope that helps.
--
Rune Lillesveen
--
You received this m
ium.org/d/msgid/blink-dev/CACuPfeS2468yfK2EzrnmiKrnyScCYfbiSF7C6aC3pix7G_XOkQ%40mail.gmail.com
This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.
--
Rune Lillesveen
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group
com/w3c/csswg-drafts/pull/8729
[3] https://github.com/w3c/csswg-drafts/pull/8756
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/6332337266098176
Links to previous Intent discussions
This intent message was generated by Chrome Platform Status
<https://chromestatus
mium.org/d/msgid/blink-dev/4b30219f-bda6-4be9-953d-c5abe0bd8874n%40chromium.org
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4b30219f-bda6-4be9-953d-c5abe0bd8874n%40chromium.org?utm_medium=email&utm_source=footer>
> .
>
--
Rune Lillesveen
--
You received this message
Contact emailsfuth...@chromium.org
Explainer
https://github.com/chrishtr/rendering/blob/master/entry-exit-animations.md
Specification
Summary
Allow authors to start CSS transitions on first style update CSS
transitions do not trigger transitions from initial styles on the first
style update for
generated by Chrome Platform Status
<https://chromestatus.com/>.
--
Rune Lillesveen
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsub
lementation of
> > Option 3?
>
> As far as I know, WebKit is indeed working an implementation of Option 3.
>
Enabled feature for preview (TP?) here:
https://github.com/WebKit/WebKit/commit/ceafa556d06a475ae4b9362abeb64a42128ce9ee
--
Rune Lillesveen
--
You received this message
seems similar.
>>> I made a CL that adds 'CSSPseudoHasNonForgivingParsing' feature (
>>> https://chromestatus.com/feature/6177049203441664) for the change:
>>> - https://chromium-review.googlesource.com/c/chromium/src/+/4151453
>>>
>>> The CL also ad
On Fri, Dec 16, 2022 at 11:13 AM Rune Lillesveen
wrote:
>
> Debuggability
>
> DevTools may need to show style containers like it is done with size
> container queries today. However, all elements are style containers by
> default, so probably not the same type of UI. There is
on:", but the
generated e-mail does not include that field. I've reported
https://github.com/GoogleChrome/chromium-dashboard/issues/2591
> On Fri, Dec 16, 2022 at 5:13 AM Rune Lillesveen
> wrote:
>
>> Contact emailsfuth...@chromium.org
>>
>> Expla
Platform Status
<https://chromestatus.com/>.
--
Rune Lillesveen
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubscr...@chromium.org.
To
On Mon, Oct 17, 2022 at 3:19 PM Yoav Weiss wrote:
>
>
> On Thu, Oct 13, 2022 at 4:11 PM Rune Lillesveen
> wrote:
>
>> Contact emailsfuth...@chromium.org
>>
>> ExplainerNone
>>
>> Specificationhttps://www.w3.org/TR/css-values-4/#lh
>>
>>
On Fri, Oct 14, 2022 at 9:32 AM Manuel Rego Casasnovas
wrote:
>
>
> On 13/10/2022 16:10, Rune Lillesveen wrote:
> > Summary
> >
> > Support for expressing CSS lengths relative to the line-height
>
> Is this only about "lh"? What about "rl
msgid/blink-dev/CACuPfeSsKWD6%3DEvmbzVe7f1o4cniTDcRzXEqWnvHLAbCRxnfgQ%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACuPfeSsKWD6=evmbzve7f1o4cnitdcrzxeqwnvhlabcrxn...@mail.gmail.com>
This intent message was generated by Chrome Platform Status
<https://chrom
se you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+unsubscr...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgi
On Fri, Sep 2, 2022 at 2:39 PM Yoav Weiss wrote:
>>
>>>
>>>
>>> On Fri, Sep 2, 2022 at 2:19 PM Rune Lillesveen
>>> wrote:
>>>
>>>> On Fri, Sep 2, 2022 at 1:37 PM Yoav Weiss wrote:
>>>>
>>>>> Thanks for the up
es specified
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/4998371945742336
This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.
--
Rune Lillesveen
--
You received this message because you are subscribed to the Google
On Fri, Sep 2, 2022 at 2:39 PM Yoav Weiss wrote:
>
>
> On Fri, Sep 2, 2022 at 2:19 PM Rune Lillesveen
> wrote:
>
>> On Fri, Sep 2, 2022 at 1:37 PM Yoav Weiss wrote:
>>
>>> Thanks for the update! Given that this is something that web developers
>>> h
implementation to
not allow forgiving selectors lists. Authors should be able to get the same
forgiving effect for :has() sprinkling :is() at appropriate places.
Slightly longer term, the spec issue for possibly changing it is here:
https://github.com/w3c/csswg-drafts/issues/7676
On Fri, Sep 2,
On Fri, Sep 2, 2022 at 1:09 PM Rune Lillesveen wrote:
> On Fri, Sep 2, 2022 at 11:40 AM Rune Lillesveen
> wrote:
>
>> Hi all,
>>
>> We have an incoming issue for jQuery that seems pretty serious for them:
>>
>
> An update on the impact for jQuery:
>
On Fri, Sep 2, 2022 at 11:40 AM Rune Lillesveen
wrote:
> Hi all,
>
> We have an incoming issue for jQuery that seems pretty serious for them:
>
An update on the impact for jQuery:
https://github.com/jquery/jquery/issues/5098#issuecomment-1235351545
https://crbug.com/1358953
>
&
ointed at above will *not* be fixed before shipping.
>>>>>
>>>>> Since it is positive to disallow explicit ':scope' inside ':has()', I
>>>>> think disallowing ':host()' inside ':has()' is still reasonable.
>>
rallel with the spec
consideration.
On Tue, Aug 9, 2022 at 6:14 PM Rune Lillesveen wrote:
> Given this was rejected last time it was discussed in the csswg, it
> doesn't seem likely it will change this time?
>
> On Sat, Aug 6, 2022 at 5:54 PM 紫云飞 wrote:
>
>> Please hold shipping
54d-1ac4-b567043ecdb7%40gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, sen
duce web compat/interop risk (e.g., changing to naming or structure of
the API in a non-backward-compatible way).
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5193188445257728
This intent message was generated by Chrome Platform Status
<https://chromestatu
is has been discussed with a couple of API owners and considered to be an
acceptable bug for the first release.
We have added a console warning
<https://chromium-review.googlesource.com/c/chromium/src/+/3706582> to
notify authors about this (including the printing case)
--
Rune Lillesveen
--
You r
On Wed, Nov 10, 2021 at 2:54 PM Rune Lillesveen
wrote:
> On Fri, Oct 29, 2021 at 9:09 PM Emilio Cobos Álvarez
> wrote:
>
>>
>>
>> On 10/28/21 13:14, Rune Lillesveen wrote:
>> > On Thu, Oct 28, 2021 at 12:11 PM Manuel Rego Casasnovas <
>> r...@ig
On Fri, Oct 29, 2021 at 9:09 PM Emilio Cobos Álvarez
wrote:
>
>
> On 10/28/21 13:14, Rune Lillesveen wrote:
> > On Thu, Oct 28, 2021 at 12:11 PM Manuel Rego Casasnovas > <mailto:r...@igalia.com>> wrote:
> >
> > Hi,
> >
> > Some com
On Thu, Oct 28, 2021 at 12:11 PM Manuel Rego Casasnovas
wrote:
> Hi,
>
> Some comments inline.
>
> On 27/10/2021 16:09, Rune Lillesveen wrote:
> > Summary
> >
> > The 'only' keyword has been re-added to the specification for
> > colo
On Wed, Oct 27, 2021 at 4:09 PM Rune Lillesveen
wrote:
>
> Debuggability
>
> The existing property and the new keyword should automatically be
> supported in devtools. There is possibly a need for force dark /
> color-scheme override debugging support in devtools, but that is
me?False
Tracking bughttps://crbug.com/1224806
Estimated milestones
DevTrial on desktop 96
DevTrial on android 96
DevTrial on Webview 96
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5157621012103168
This intent message was generated by Chrome Platform Status
<
! Positive response from dholbert.
On 9/14/21 6:12 PM, Rune Lillesveen wrote:
>
> Contact emails futh...@chromium.org
>
> Specification http://drafts.csswg.org/css-contain-1/#c3
>
> Summary
>
> Used values for contain different from none on the root or body elements
> will
.html
<https://wpt.fyi/results/css/css-contain/contain-html-w-m-004.html>
Flag nameCSSContainedBodyPropagation
Requires code in //chrome?False
Tracking bughttps://crbug.com/1215265
Estimated milestones
M96
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5663
66 matches
Mail list logo
