-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android: enable iframe support #536
Conversation
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
Signed-off-by: Emanuele Feliziani <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @GioSensation - I love how we're consolidating more and more APIs/functionality to match across platform.
Just a single question for you to have a look at 👍🏻
if (!(androidSpecificName in window)) { | ||
throw new MissingHandler(`Missing android handler: '${methodName}'`, methodName) | ||
} | ||
return window[androidSpecificName] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the story around these handlers, do we need to attempt to capture them? or is that out of scope for this work?
I know that previously the exec-time of Android's JS couldn't be guaranteed to be 'first' - can it now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about that, and even attempted a quick solution, but then I backtracked. It's not strictly in scope, and we should think this through a bit more, especially if we think of that as improving security, because it may not change anything. We would likely still do it for a variety of reasons, but we need a triage etc. I will scope a project to follow up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice - yeah with a follow-up project in place then we can approve this and move forward 💪🏻
Signed-off-by: Emanuele Feliziani <[email protected]>
… ema/android-iframe-support Signed-off-by: Emanuele Feliziani <[email protected]> # Conflicts: # dist/autofill-debug.js # dist/autofill.js # swift-package/Resources/assets/autofill-debug.js # swift-package/Resources/assets/autofill.js
Signed-off-by: Emanuele Feliziani <[email protected]>
This reverts commit 8b046b1, disabling Android iframe support due to a bug in the native WebView. See https://app.asana.com/0/1203822806345703/1207304124810216/f for details.
This reverts commit 8b046b1, disabling Android iframe support due to a bug in the native WebView. See https://app.asana.com/0/1203822806345703/1207304124810216/f for details.
This reverts commit 8b046b1, disabling Android iframe support due to a bug in the native WebView. See https://app.asana.com/0/1203822806345703/1207304124810216/f for details.
This was originally introduced as a commit squashed into 8b046b1 (Android: enable iframe support (#536), 2024-04-09), but was accidentally removed via 18dd599 (android: revert "Android: enable iframe support (#536)" (#582), 2024-06-20). Reintroduce that commit, to ensure the `password_generation` runtime config flag is again respected and prevent password prompts after a user clicks "Never save for site". (cherry picked from commit 4c16e52)
This was originally introduced as a commit squashed into 8b046b1 (Android: enable iframe support (#536), 2024-04-09), but was accidentally removed via 18dd599 (android: revert "Android: enable iframe support (#536)" (#582), 2024-06-20). Reintroduce that commit, to ensure the `password_generation` runtime config flag is again respected and prevent password prompts after a user clicks "Never save for site". (cherry picked from commit 4c16e52)
Reviewer: @shakyShane
Asana: https://app.asana.com/0/0/1206521793046282/f
Description
Enables iframe autofill on Android by migrating to the new webview API.
Steps to test
All integration tests updated to match the new messaging pattern. Plus tested extensively by Craig on Android and by me on other platforms.