1581238 - webauthn / navigator.credentials.create throws DOMError when inspector/debugger is open

Status: RESOLVED WORKSFORME

(DevTools :: Debugger, defect)

Description

[Mollet]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

Called navigator.credentials.create with the inspector open to the debug tab and some breakpoints set.

Note that this works correctly with the inspector closed.

This can be easily duplicated by going to https://u2f.bin.coffee/ and opening the inspector and then clicking U2F register. The window will turn red and indicate an error. If the inspector is closed and the page reloaded, it works correctly.

Firefox 69.0, MacosX 10.14.6, yubikey 4

Actual results:

navigator.credentials.create threw an error:

NotAllowedError: The request is not allowed by the user agent or the platform in the current context, possibly because the user denied permission.

Expected results:

Firefox prompts for a user interaction with the physical key.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 2

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Attachment: image.png

@Mollet, I can see red window even without the DevTools toolbox being open

I just clicked the U2F Register button twice

Can you see that too?

Honza

Comment 3

[Mollet]

If you don't have a U2F key or don't use a U2F emulator, then it will show red and an error, that's an expected behavior. The bug is that even with a key, if the debugger is open, it fails.

Here's an emulator that you can use on Linux:

https://github.com/danstiner/rust-u2f

Testing this on another computer with 69.0.1, it appears to have been fixed. I updated the laptop where I originally found and reported this buy to 69.0.1 and it's fixed there as well.

Comment 4

[Jan Honza Odvarko [:Honza] (always need-info? me)]

(In reply to Mollet from comment #3)

Testing this on another computer with 69.0.1, it appears to have been fixed. I updated the laptop where I originally found and reported this buy to 69.0.1 and it's fixed there as well.

Thanks for the update!

I am closing the report for now, but feel free to reopen if you see the problem again.

Honza