Conversation
| new Browser("jp.co.fenrir.android.sleipnir_black", "url_text"), | ||
| new Browser("jp.co.fenrir.android.sleipnir_test", "url_text"), | ||
| new Browser("com.vivaldi.browser", "url_bar"), | ||
| new Browser("com.vivaldi.browser.snapshot", "url_bar"), |
There was a problem hiding this comment.
Do we also need to add this to Autofill Helpers CompatBrowsers?
There was a problem hiding this comment.
It doesn't appear to make a difference (neither vivaldi seems to work with autofill, at least for me). I can add it anyway if you'd like.
|
Hello, @mportune-bw Is there a specific reason for not adding com.vivaldi.browser.snapshot to autofillservice.xml too? As was the case with com.vivaldi.browser when it was added? @kspearrin More generally, is autofillservice.xml still used? If yes, why so many "package names" missing when compared to AutofillHelpers.cs? Namely: Thanks. |
|
@mportune-bw Can you evaluate if we still need to be using autofillservice.xml definitions? |
|
Looks like yes, if my understanding of the autofill service compatibility mode is correct. #834 brings it all back together. (Thanks for the pointer @contribucious ) |
|
@mportune-bw No problem and thank you! 👍 |
|
@kspearrin / @mportune-bw ⬇️
To maintain a list of browsers in compatibility mode, considering that Android requires the use of this dedicated XML file anyway, why not rather reason in the opposite direction therefore, @kspearrin? PRESS ME TO READ MORE ABOUT THIS IDEA ... 👈💡 Knowing that ...
... and that you want to manage this data set from CompatBrowsers in your code, why not just populate it from this XML file, therefore? Below ... code for you on this subject! Feel free to do whatever you want with it, then!
|
Add autofill (accessibility) support for Vivaldi snapshot browser
┆Issue is synchronized with this Asana task by Unito