Assigned
Status Update
No update yet.
Comments
bl...@google.com
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for component 522910.
sh...@adobe.com
sh...@adobe.com
Just want to add that this is needed for the Bard to Express workflow which is critical for both Adobe and Google. Google One Tap widget needs to positioned front and center when a user click on a CTA in Bard to edit a generated image in Adobe Express. Kindly prioritize this accordingly.
jp...@google.com
It seems that this can be worked around by passing the ID to a slot? HTMLElement instead of the prompt_parent_id.
sh...@adobe.com
Thanks.
sh...@adobe.com
The workaround mentioned above doesn't really work since there is a lot of nesting of the shadowRoots and the events like node removal still remain unrecognized. Just passing the parent element would work as suggested in the issue above since the widget would have direct access to the parent and the positioning the element relative to the parent would also be easy.
sh...@adobe.com
Any ETA on when this will arrive?
Description
I was guided to create this ticket from another issue -
We at Adobe are currently working at integrating Google One Tap into one of our workflows of Adobe Express Beta.
An issue we're facing with Google One Tap is that right now it takes prompt_parent_id if we want to place it anywhere else in the HTML DOM.
See -
This is a problem for us since our web application uses shadow DOM and just passing the id wouldn't help.
We tried to attach it programmatically by moving the HTML element for the One Tap Widget one it is available, inside of an element in the ShadowDOM however we stopped receiving notifications from the widget and were unable to properly dismiss it.
Our suggestion: It would be better if we could pass the parent element itself instead of the parent id, this way, One Tap widget can use that parent element to remove the widget properly, instead of having to find it by id in the Light DOM, which will not work in our case due to the sandboxing provided by Shadow DOM
This is not a security issue but it's is critical for Adobe as feature request.
Thanks,