[blink-dev] Intent to Ship: aria-brailleroledescription and aria-braillelabel

*Contact emails* alevent...@chromium.org, spectran...@igalia.com *Explainer* https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-brailleroledescription https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-braillelabel *Specification* https:/

Re: [blink-dev] Intent to Experiment: Declarative Beacon API

On Wed, Aug 31, 2022 at 3:04 AM Ming-Ying Chung wrote: > Hi all, > > Reviving this thread as we plan to conduct an Origin Trial for this > feature in M106, with the following updates. Please take a look. > Is it possible to extend this trial for a few releases? Most trials run for ~3 releases in

Re: [blink-dev] ChromeStatus -- Direct Sockets

+ericwillig...@chromium.org , can you transfer ownership of this feature to Andrew? Reilly Grant | Software Engineer | reil...@chromium.org | Google Chrome On Fri, Sep 2, 2022 at 10:57 AM 'Panos Astithas' via blink-dev < blink-dev@chromium.org> wrote: > Hi Andrew,

Re: [blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.surfaceSwitching

This is shipping in m107. (Thank you François Beaufort for implementing!) On Wednesday, June 22, 2022 at 7:20:56 PM UTC+2 Elad Alon wrote: > When I have an exact date, I will update ChromeStatus and ping this thread > with the target. Currently, I only know that it will be before EoY, but no >

Re: [blink-dev] Re: Intent to Ship: DisplayMediaStreamConstraints.systemAudio

This is shipping in m105. On Thursday, June 23, 2022 at 10:28:26 AM UTC+2 Elad Alon wrote: > Thanks you all! > > On Tuesday, June 21, 2022 at 6:45:57 PM UTC+2 Chris Harrelson wrote: > >> LGTM3 >> >> On Thu, Jun 16, 2022 at 5:12 AM Mike Taylor wrote: >> >>> LGTM2 >>> >>> On 6/16/22 9:42 AM, Yoav

Re: [blink-dev] Re: Intent to Ship: tech() function support in @font-face src: descriptor

LGTM3 On Fri, Sep 2, 2022 at 7:48 PM Chris Harrelson wrote: > LGTM2 > > On Fri, Sep 2, 2022 at 10:20 AM Alex Russell > wrote: > >> Hey Dominik, >> >> Thanks for getting back to me, the detail on the syntax, and for the link >> to the explainer. Thanks also for correcting me regarding the TAG re

Re: [blink-dev] Side Nav - Sub menu not Working after update chrome 105

Hi, Sorry to hear there was a problem. Could you file a bug at https://crbug.com/new and indicate steps to reproduce it, such as website url? On Fri, Sep 2, 2022 at 10:57 AM Lau RdyS wrote: > Please help, after I updated chrome to version 105 from version 104, the > sub menu from the side menu

[blink-dev] Side Nav - Sub menu not Working after update chrome 105

Please help, after I updated chrome to version 105 from version 104, the sub menu from the side menu doesn't work but in Mozilla browser it can [image: BUG_CHROME.jpg] -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this grou

Re: [blink-dev] ChromeStatus -- Direct Sockets

Hi Andrew, The feature owner listed in the Chromestatus page is the best PoC for updating the page. If you plan to make frequent updates they can add you as an editor per our recent announcement . Thanks, Panos O

Re: [blink-dev] Re: Intent to Ship: tech() function support in @font-face src: descriptor

LGTM2 On Fri, Sep 2, 2022 at 10:20 AM Alex Russell wrote: > Hey Dominik, > > Thanks for getting back to me, the detail on the syntax, and for the link > to the explainer. Thanks also for correcting me regarding the TAG review. I > feel much better about the proposal as a result of all of this de

Re: [blink-dev] Re: Intent to Ship: tech() function support in @font-face src: descriptor

Hey Dominik, Thanks for getting back to me, the detail on the syntax, and for the link to the explainer. Thanks also for correcting me regarding the TAG review. I feel much better about the proposal as a result of all of this detail. On the CSS WG aspects, if features are developed w/ epxlainer

Re: [blink-dev] Re: Intent to Ship: tech() function support in @font-face src: descriptor

On Wed, Aug 31, 2022 at 6:02 PM Alex Russell wrote: > We discussed this at today's API OWNERs meeting and, while I realise I > should perhaps be directing most of these comments at the CSS WG more > broadly, I'm concerned that the bundle of features that this function is > designed to support are

Re: [blink-dev] Intent to Ship : :has() pseudo class

Thank you for checking the issue and sorry for not being able to prevent it in advance. I missed the risk of conflicting with JQuery's :has() implementation. I apologize for not checking enough. I made a CL to avoid current JQuery conflict by following the WebKit behavior: - https://chromium-

Re: [blink-dev] Re: Intent to Ship: tech() function support in @font-face src: descriptor

Hi Theo, On Friday, September 2, 2022 at 3:07:04 PM UTC+2 Theodore Olsauskas-Warren wrote: > (Chrome OWP Privacy reviewer drive-by) > > I'm trying to understand whether the various tech() capabilities are > directly derivable from already exposed information, and this is just a > convenience,

Re: [blink-dev] Re: Intent to Ship: tech() function support in @font-face src: descriptor

(Chrome OWP Privacy reviewer drive-by) I'm trying to understand whether the various tech() capabilities are directly derivable from already exposed information, and this is just a convenience, or whether otherwise identical UAs might give out different values based on the platform or user confi

Re: [blink-dev] Intent to Ship : :has() pseudo class

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 >>> have been using (as a polyfill, but still) for

Re: [blink-dev] Intent to Ship : :has() pseudo class

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 >> have been using (as a polyfill, but still) for a lng while, I'm >> somewhat skeptical that we can get away

Re: [blink-dev] Intent to Ship : :has() pseudo class

On Fri, Sep 2, 2022 at 1:37 PM Yoav Weiss wrote: > Thanks for the update! Given that this is something that web developers > have been using (as a polyfill, but still) for a lng while, I'm > somewhat skeptical that we can get away with the spec as currently written. > As we can't have use-cou

Re: [blink-dev] Intent to Ship : :has() pseudo class

Thanks for the update! Given that this is something that web developers have been using (as a polyfill, but still) for a lng while, I'm somewhat skeptical that we can get away with the spec as currently written. As we can't have use-counters for things passed as jquery selectors, I wonder if an

Re: [blink-dev] Intent to Ship : :has() pseudo class

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: > > https://github.com/jquery/jquery/issues/5098

Re: [blink-dev] Intent to Ship : :has() pseudo class

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 > > The problem is

Re: [blink-dev] Intent to Ship : :has() pseudo class

Hi all, We have an incoming issue for jQuery that seems pretty serious for them: https://crbug.com/1358953 The problem is that jQuery uses the native implementation of :has() when present, but the feature detection detects support for other custom jQuery selectors inside :has() because of :has()