I am currently moving the feature through chrome's experimentation channels. I will update the tracking bug when it is enabled by default: https://bugs.chromium.org/p/chromium/issues/detail?id=649162
On Tue, Mar 8, 2022 at 4:27 AM prerana wankhade <preranawankha...@gmail.com> wrote: > Hello Team, > > Do we have any update on the ongoing "Autofill in ShadowDOM" issue, is > there a solution in place, if not then when can we expect the release/live? > > Thanks in Advance, > Prerana > > On Tuesday, February 22, 2022 at 10:42:28 PM UTC+5:30 Joey Arhar wrote: > >> > Does this works in other browsers? Have we reported bugs if it doesn't? >> >> I just found this WebKit bug someone else reported: >> https://bugs.webkit.org/show_bug.cgi?id=172567 >> I'm guessing this means it doesn't work in WebKit, at least. >> >> On Thu, Feb 17, 2022 at 12:21 PM Joey Arhar <jar...@chromium.org> wrote: >> >>> > The required “Debuggability” section was left empty. Per the guide at >>> https://goo.gle/devtools-checklist, we need to ensure that DevTools >>> supports basic display and editing of new HTML features — which would >>> likely work out-of-the-box anyhow. Please follow this guide and elaborate >>> on how developers would inspect & debug this new feature please. Thanks! >>> >>> Apologies for leaving this empty. As far as I know, there is >>> unfortunately no existing debuggability of autofill in DevTools in general. >>> I'm not sure what autofill debugging would look like, but if that ever >>> happens, I'd be happy to add in any logic for this feature if needed. >>> >>> On Thu, Feb 17, 2022 at 3:20 AM Changhao Han <chang...@google.com> >>> wrote: >>> >>>> The required “Debuggability” section was left empty. Per the guide at >>>> https://goo.gle/devtools-checklist, we need to ensure that DevTools >>>> supports basic display and editing of new HTML features — which would >>>> likely work out-of-the-box anyhow. Please follow this guide and elaborate >>>> on how developers would inspect & debug this new feature please. Thanks! >>>> >>>> On Wednesday, February 16, 2022 at 7:30:31 PM UTC+1 Joey Arhar wrote: >>>> >>>>> > Yeah, and there's already an issue about that: >>>>> > https://github.com/web-platform-tests/wpt/issues/27118 >>>>> >>>>> Thanks! I'll watch this in case I can ever add WPTs for this. >>>>> >>>>> > Does this works in other browsers? Have we reported bugs if it >>>>> doesn't? >>>>> >>>>> I don't think other browsers do this, but I couldn't get autofill to >>>>> even fill the non-ShadowDOM input on my test page on firefox or safari... >>>>> >>>>> On Wed, Feb 16, 2022 at 1:39 AM Manuel Rego Casasnovas < >>>>> re...@igalia.com> wrote: >>>>> >>>>>> LGTM3. >>>>>> >>>>>> Some comments inline. >>>>>> >>>>>> On 16/02/2022 00:39, Mike Taylor wrote: >>>>>> >> Interoperability and Compatibility >>>>>> >> >>>>>> >> I believe there is low compat risk. As far as I know, much >>>>>> >> autofill behavior already diverges between browsers. >>>>>> >> >>>>>> >> Gecko: No signal >>>>>> >> >>>>>> >> WebKit: No signal >>>>>> >>>>>> Does this works in other browsers? Have we reported bugs if it >>>>>> doesn't? >>>>>> >>>>>> >> Is this feature fully tested by web-platform-tests >>>>>> >> < >>>>>> https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md >>>>>> >? >>>>>> >> >>>>>> >> No. Autofill is not testable in WPT, as far as I know. In >>>>>> >> order to test this feature, I had to make C++ browser >>>>>> tests. >>>>>> >>>>>> Yeah, and there's already an issue about that: >>>>>> https://github.com/web-platform-tests/wpt/issues/27118 >>>>>> >>>>>> Cheers, >>>>>> Rego >>>>>> >>>>> -- 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 view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK6btw%2ByjxDFHRLWaCz3JMJPc-JoDgfzbEiOLPvcpnQf27fVtg%40mail.gmail.com.
