Re: [blink-dev] Intent to Ship: Element Reflection

Very exciting to see this! On Thu, Feb 1, 2024 at 12:10 AM alice wrote: > Contact emails > al...@igalia.com, meredi...@chromium.org > > Explainer > > https://github.com/WICG/aom/blob/gh-pages/aria-reflection-explainer.md#reflecting-element-references > > Specification > >

[blink-dev] 2 days until Chromium’s migration to the new issue tracker begins (Feb 2)

Hi all, As we shared yesterday, Chromium is moving to a different issue tracker to provide a well-supported user experience for the long-term. Migration is on track to begin February 2, 2024 at 5pm PST, and we expect migration will be completed by the end of day February 4, 2024 PST. There will

Re: [blink-dev] Re: Chromium’s migration to the new issue tracker begins Feb 2

It's issue-tracker-support at chromium.org On Wed, Jan 31, 2024, 8:31 PM David Dabbs wrote: > Thank you for the reminder Joe. > My digest message does not include a full e-mail address: > >You can reach out at any time to issue-trac...@chromium.org > with

[blink-dev] Request for Deprecation Trial: Deprecate Mutation Events

Contact emailsmas...@chromium.org ExplainerNone Specificationhttps://w3c.github.io/uievents/#legacy-event-types Summary Mutation Events, including `DOMSubtreeModified`, `DOMNodeInserted`, `DOMNodeRemoved`, `DOMNodeRemovedFromDocument`, `DOMNodeInsertedIntoDocument`, and

[blink-dev] Re: Chromium’s migration to the new issue tracker begins Feb 2

Thank you for the reminder Joe. My digest message does not include a full e-mail address: You can reach out at any time to issue-trac...@chromium.org with questions or concerns. Can you kindly please supply this so I can post a question? Thanks, dd On

Re: [blink-dev] Intent to Ship: Element Reflection

Look I don’t know what you guys are talking about. This is gonna be the last time I’m asking you give me a call right now or I am delivering this to the police department. I’m not playing around anymore I do not know who you people are. I don’t know if you guys are tracking something selling

Re: [blink-dev] Intent to Ship: Element Reflection

On Wed, Jan 31, 2024 at 6:14 PM Alice Boxhall wrote: > > > On Thursday, February 1, 2024 at 6:52:13 AM UTC+11 vmp...@google.com > wrote: > > On Wed, Jan 31, 2024 at 10:10 AM alice wrote: > > Contact emails > al...@igalia.com, mere...@chromium.org > > Explainer > >

Re: [blink-dev] Intent to Ship: Element Reflection

Hello Alice, I have no clue what you are talking about. This is all technology and I have no clue of what it is, ma’am, so if you can explain this in plain English, I would appreciate it. Just for your information someone is emailing all of you and it is not me. Our you a Technology company are

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

Thanks for marking it for review! I submitted a request to review this change to the chromium enterprise mailing list. Thanks, Thomas On Wed, Jan 31, 2024 at 1:08 PM Mike Taylor wrote: > Yep - seems that's the cause of confusion. In your first email, >

Re: [blink-dev] Intent to Ship: Element Reflection

On Thursday, February 1, 2024 at 6:52:13 AM UTC+11 vmp...@google.com wrote: On Wed, Jan 31, 2024 at 10:10 AM alice wrote: Contact emails al...@igalia.com, mere...@chromium.org Explainer https://github.com/WICG/aom/blob/gh-pages/aria-reflection-explainer.md#reflecting-element-references

Re: [blink-dev] Intent to Ship: Element Reflection

On Thursday, February 1, 2024 at 4:01:32 AM UTC+11 Philip Jägenstedt wrote: Hi Alice, For testing of these in WPT, do you have some details on what's missing? It's already possible to get the accessible name and role for an element:

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

Yep - seems that's the cause of confusion. In your first email, https://chromestatus.com/feature/5259513871466496 is linked from the bottom, so our review tooling is presenting that to us. But I've just flagged the new one so it will show up as well. thanks! On 1/31/24 2:41 PM, Thomas

Re: [blink-dev] Intent to Ship: Element Reflection

On Wed, Jan 31, 2024 at 10:10 AM alice wrote: > Contact emails > al...@igalia.com, meredi...@chromium.org > > Explainer > > https://github.com/WICG/aom/blob/gh-pages/aria-reflection-explainer.md#reflecting-element-references > > Specification > >

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

I requested privacy/security/debuggability on the video element fullscreen API deprecation feature last week. Privacy and debuggability are approved, just waiting on security. Mike, are you talking about requesting those

Re: [blink-dev] Intent to Ship: Element Reflection

Hi Alice, For testing of these in WPT, do you have some details on what's missing? It's already possible to get the accessible name and role for an element: https://web-platform-tests.org/writing-tests/testdriver.html#accessibility I suspect that won't help, but there's an experimental/tentative

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

Apologies in advance for excessive paperwork, but can you also put https://chromestatus.com/feature/5111638103687168 through the process, requesting enterprise signoff in particular? Enterprise folks could depend on this and might need to take some extra action, and a "Feature deprecation" entry

Re: [blink-dev] Re: Intent to Ship: NavigationActivation

LGTM3 /Daniel On 2024-01-31 17:53, Chris Harrelson wrote: LGTM2 On Wed, Jan 31, 2024 at 8:00 AM Yoav Weiss (@Shopify) wrote: LGTM1 On Friday, January 26, 2024 at 10:27:50 AM UTC+1 Noam Rosenthal wrote: Contact emailsjap...@chromium.org, nrosent...@chromium.org

Re: [blink-dev] Re: Intent to Ship: NavigationActivation

LGTM2 On Wed, Jan 31, 2024 at 8:00 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM1 > > On Friday, January 26, 2024 at 10:27:50 AM UTC+1 Noam Rosenthal wrote: > > Contact emailsjap...@chromium.org, nrosent...@chromium.org > >

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

Gentle reminder to follow up on requesting privacy/security/debuggability approvals in chromestatus (which is currently blocking LGTMs). On Wednesday, January 24, 2024 at 7:23:28 AM UTC-5 Mike Taylor wrote: > Would you mind requesting reviews for the various gates (privacy, > security,

Re: [blink-dev] Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking

Thanks for chiming in, Robert! Sahir - can you let us know once the PEWG has discussed this and you feel this is good to go? On Tuesday, January 23, 2024 at 8:26:32 PM UTC+1 sahir@microsoft.com wrote: > Thanks Rick and Robert! > > Rick, I agree that it would be relatively easy to

[blink-dev] Re: Intent to Ship: NavigationActivation

LGTM1 On Friday, January 26, 2024 at 10:27:50 AM UTC+1 Noam Rosenthal wrote: Contact emailsjap...@chromium.org, nrosent...@chromium.org Explainerhttps://github.com/WICG/view-transitions/blob/main/ navigation-activation-explainer.md

[blink-dev] Re: Intent to Ship: CJK punctuation kerning: the CSS `text-spacing-trim` property

Oops, the approved emails are now coming. Sorry for the spam, and thank you for fixing it  On Wednesday, January 31, 2024 at 4:10:02 PM UTC+1 Kagami Rosylight wrote: > Hello, Koji Ishii; > > I think this post has a mistake about Mozilla's standards position. >

[blink-dev] Intent to Ship: Element Reflection

Contact emails al...@igalia.com, meredi...@chromium.org Explainer https://github.com/WICG/aom/blob/gh-pages/aria-reflection-explainer.md#reflecting-element-references Specification

[blink-dev] Re: Intent to Ship: CJK punctuation kerning: the CSS `text-spacing-trim` property

Hi Blink people, I think there was a misunderstanding while reading Mozilla's standards position issue; the issue currently has no response from Mozilla employee and thus should be understood as No Signal rather than Positive. I hope this makes sense. On Wednesday, January 31, 2024 at 6:38:19 

[blink-dev] Re: Intent to Ship: CJK punctuation kerning: the CSS `text-spacing-trim` property

Hello, Koji Ishii; I think this post includes a mistake about Mozilla's standards position. https://github.com/mozilla/standards-positions/issues/903 does not have any comment from Mozilla employee so far, so I think it should be No Signal instead. On Wednesday, January 31, 2024 at 6:38:19 AM

[blink-dev] Re: Intent to Ship: CJK punctuation kerning: the CSS `text-spacing-trim` property

Hello, Koji Ishii; I think this post has a mistake about Mozilla's standards position. https://github.com/mozilla/standards-positions/issues/903 is empty without Mozilla employee's comment, so I think it should be treated as No Signal here. Thanks! On Wednesday, January 31, 2024 at 6:38:19 AM

[blink-dev] Re: Intent to Ship: CJK punctuation kerning: the CSS `text-spacing-trim` property

Hi Kagami, Thank you for the information and sorry about the misunderstanding. Fixed the chromestatus entry . On Wed, Jan 31, 2024 at 8:30 PM Kagami Rosylight wrote: > > Hi Blink people, > > I think there was a misunderstanding while reading