Contact emails
gabrielbr...@microsoft.com
Explainer
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/GamepadHapticsActuatorTriggerRumble/explainer.md
Specification
https://w3c.github.io/gamepad/#dom-gamepadhapticeffecttype-trigger-rumble
Design docs
None
Summary
Extend the
Thank you all!
Mason
On Wed, Apr 10, 2024 at 11:27 AM Mike Taylor wrote:
> LGTM3
> On 4/10/24 12:55 PM, Daniel Bratell wrote:
>
> LGTM2
>
> /Daniel
> On 2024-04-10 18:43, Alex Russell wrote:
>
> Ok, so Chris reminded me that we'd already shipped a setter via
> `setHTMLUnsafe()` and that
LGTM3
On 4/10/24 12:55 PM, Daniel Bratell wrote:
LGTM2
/Daniel
On 2024-04-10 18:43, Alex Russell wrote:
Ok, so Chris reminded me that we'd already shipped a setter via
`setHTMLUnsafe()` and that Mozilla has an intent out for this new
version of the getter, which suggests to me that we
I should add that we’re open to the idea of auto, and definitely see the use.
We’d like to iterate on the feature, assessing the impact & complexity at each
step to ensure we don’t end up quagmired.
On Wed, 10 Apr 2024, at 6:39 PM, Keith Cirkel wrote:
> Initially, no. I think there’s scope to
Initially, no. I think there’s scope to introduce auto later, if I’m not
mistaken.
On Wed, 10 Apr 2024, at 6:38 PM, Brian Kardell wrote:
> But not experimenting at all with some kind of auto?
>
> On Wednesday, April 10, 2024 at 1:31:39 PM UTC-4 Keith Cirkel wrote:
>> __
>> We’re looking at
But not experimenting at all with some kind of auto?
On Wednesday, April 10, 2024 at 1:31:39 PM UTC-4 Keith Cirkel wrote:
> We’re looking at prototyping the additive model in your latest comments
> Tab. We’ll also be implementing the similar model across GitHub.com (for
> internal validation
We’re looking at prototyping the additive model in your latest comments Tab.
We’ll also be implementing the similar model across GitHub.com (for internal
validation only, for now) to see how well it aligns to our desired model. Hope
this helps.
On Wed, 10 Apr 2024, at 6:15 PM, Tab Atkins Jr.
There's been significant discussion in that thread over what the precise
behavior should be, particularly when elements using the attribute are
nested. Can you elaborate on which behavior you're intending to prototype?
On Wednesday, April 10, 2024 at 9:15:47 AM UTC-7 Keith Cirkel wrote:
>
LGTM2
/Daniel
On 2024-04-10 18:43, Alex Russell wrote:
Ok, so Chris reminded me that we'd already shipped a setter via
`setHTMLUnsafe()` and that Mozilla has an intent out for this new
version of the getter, which suggests to me that we should, indeed,
handle the streams thing separately.
LGTM3
/Daniel
On 2024-04-08 17:37, Mike Taylor wrote:
LGTM2
On 4/8/24 10:41 AM, Yoav Weiss (@Shopify) wrote:
Can you please flip on the "debuggability" review bit in
chromestatus? (feel free to mark it as "N/A" if you think that's the
case)
On Mon, Apr 8, 2024 at 4:40 PM Yoav Weiss
Now that this has approval, it would be good to understand when the V2
changes to move to POST are anticipated to go out and the deprecation
timline for this version.
Best,
Alex
On Wednesday, April 10, 2024 at 8:43:17 AM UTC-7 Daniel Bratell wrote:
> LGTM3
>
> /Daniel
> On 2024-04-08 17:37,
Ok, so Chris reminded me that we'd already shipped a setter via
`setHTMLUnsafe()` and that Mozilla has an intent out for this new version
of the getter, which suggests to me that we should, indeed, handle the
streams thing separately.
LGTM1.
On Friday, April 5, 2024 at 3:31:10 PM UTC-7 Mason
Thanks all! This is shipping in Chrome 125.
On Wednesday, March 20, 2024 at 11:09:47 AM UTC-4 Daniel Bratell wrote:
> LGTM3
>
> I'm also a bit concerned with the risk, but it sounds like you have it
> under control and will be able to handle the rollout appropriately.
>
> /Daniel
> On
Contact emailsmc...@chromium.org
Explainer
https://github.com/explainers-by-googlers/future-browsing-context-group-dependency-hint
SpecificationNone yet. The spec changes will be a set of patches to the
HTML spec. See the "Specification changes" section of the explainer for
details.
Summary
Contact emails
chrom...@keithcirkel.co.uk, c...@smockle.com
Explainer
https://github.com/whatwg/html/issues/5033
Specification
(Not yet available)
Summary
Adding a `headingstart=` attribute to Element nodes, that influences the child
`h1`-`h6` elements' heading levels.
Blink component
LGTM3
On Wednesday, April 10, 2024 at 8:51:54 AM UTC-7 Daniel Bratell wrote:
> LGTM2
>
> /Daniel
> On 2024-04-08 17:35, Mike Taylor wrote:
>
> LGTM1
> On 4/4/24 2:29 PM, 'Thomas Guilbert' via blink-dev wrote:
>
> The last launch gate approval came in today.
>
> Thanks!
>
> On Wed, Apr 3, 2024
LGTM2
/Daniel
On 2024-04-08 17:35, Mike Taylor wrote:
LGTM1
On 4/4/24 2:29 PM, 'Thomas Guilbert' via blink-dev wrote:
The last launch gate approval came in today.
Thanks!
On Wed, Apr 3, 2024 at 11:49 AM Thomas Guilbert
wrote:
I agree that this would have been a viable solution,
LGTM3
/Daniel
On 2024-04-08 17:37, Yoav Weiss (@Shopify) wrote:
LGTM2
On Mon, Apr 8, 2024 at 5:36 PM Mike Taylor wrote:
LGTM1
On 4/3/24 11:05 AM, Daniel Bratell wrote:
Thanks, that clarifies a bit and calms my worries considerably.
/Daniel
On 2024-03-29 14:27, Paul
Great to hear there's support for the feature.
118-126 w/o breaking changes is pushing things. Is it practical to ship
inside the 123-126 window? How close are we?
Best,
Alex
On Tuesday, April 9, 2024 at 9:07:37 AM UTC-7 Stefan Peter wrote:
> Hi, I think it would help to extend the Open
19 matches
Mail list logo
