Skip to content
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

Deleting annotations doesn't work on Chrome 91.0 #3254

Closed
esanzgar opened this issue Apr 6, 2021 · 4 comments
Closed

Deleting annotations doesn't work on Chrome 91.0 #3254

esanzgar opened this issue Apr 6, 2021 · 4 comments
Assignees

Comments

@esanzgar
Copy link
Contributor

esanzgar commented Apr 6, 2021

On Chrome version >= 91.0 the delete button on an annotation card doesn't work:

image

We believe this is related to a security feature that could prevent third party iframes to use window.confirm.

Steps to reproduce

  1. Click on the delete button

Expected behaviour

A pop-up dialog should appear to confirm the deletion.

Actual behaviour

The pop-up dialog doesn't appear.

Browser/system information

Chrome >= 91.0

Additional details

Latest versions of Safari and Firefox work correctly.

@lyzadanger
Copy link
Contributor

If this is indeed a window.confirm restriction, we'll also need to address the other usage, which is in the HypothesisApp component to warn of unsaved draft annotations.

@lyzadanger
Copy link
Contributor

More information on the "intent to remove": https://groups.google.com/a/chromium.org/g/blink-dev/c/hTOXiBj3D6A/m/YdExd4wgAgAJ?pli=1

@robertknight
Copy link
Member

It looks like this change is coming to Safari and Firefox in future as well. See whatwg/html#6297 that was linked from the above blink-dev mailing list thread.

@robertknight
Copy link
Member

The issue has been fixed for users of Chrome >= 91, and any other browsers where this issue occurs, in #3274. Users of other browsers will still see the native confirmation dialog while we polish the styling of the new one, then we'll flip the switch and use it everywhere.

I'm closing this issue since the main issue here has been resolved, although there is follow-up work ongoing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants