[web] - Move text editing nodes outside of shadowDOM, reland

[htoor3]

Password input autofill + suggest password functionality is broken for password inputs inside of a shadowDOM on chrome. This experiment is testing to see if we can lift text editing nodes outside of the shadowDOM while maintaining functionality.

1. Create a new host node outside of the shadowDOM for text-editing + accessibility
2. Attach all text editing nodes, accessibility placeholders, and semantics tree into that node
3. Ensure text editing + accessibility global styles are applied to new host node

Tree goes from:

                flt-glass-pane
                      |
                 #shadow-root
                      |
                 text nodes

to:

                            flutter-view
           -----------------------------------------------
           /                        |                  \
  flt-glass-pane             text-editing-host   semantics-host
          /  \                      |                  |
#shadow-root platform views     text nodes       semantics nodes

Will need to reland this after flutter/flutter#124299 merges.

[htoor3]

flutter/flutter#124299 is merged to fix the previously blocking framework test. This should be good to merge now, but will monitor in case of any issues.

[philyang07]

Hey, I was just wondering when this change will be accessible from stable?

[htoor3]

Hey @philyang07, the next stable release is tentatively scheduled for August. You have a couple of options if you need it sooner (and can't use master):

1. You can try to use beta, which is branched off of master and is relatively more stable (only high priority cherrypicks are accepted). Release schedule says a new beta gets cut on the first Wednesday of the month, so you can see if the changes land tomorrow 5/3.
2. You can cherrypick these changes and build your own version of engine until stable is released.

I'd recommend option 1 as there's less setup needed on your end. Hope this helps!

[rmahmadkhan]

hi @htoor3, is there any other workaround for using autofill password on web if we don't want to go with these options?