1609530 - Focused input in devtools add-on panel is unable to type "'" or "/"

Status: UNCONFIRMED

(Firefox :: Extension Compatibility, defect)

Description

[jason]

Attachment: example extension to reproduce issue

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36

Steps to reproduce:

1. Create a devtools add-on panel with an input field
2. Attempt to type ' or / into the field

My guess is this is related to the Accessibility.typeahead feature because when this feature is disabled, I am able to successfully type those values into an input inside of a devtools add-on panel. Attached is an example extension to reproduce the issue.

Actual results:

Unable to type ' or / into focused input field

Expected results:

Able to type ' or / into focused input field

Comment 1

[Daniel Bodea [:danibodea]]

I would like to confirm your issue, but I do not seem to be able to reproduce it. The add-on you attached to this bug cannot be installed because it appears to be corrupt. If loaded as a temporary extension, the add-on panel cannot be opened. How exactly fo you install your test add-on in order to get the add-on's panel displayed and the issue reproduced?

Comment 2

[jason]

I used npx web-ext run in the unpackaged extension directory to load it into Firefox.

Comment 3

[Daniel Bodea [:danibodea]]

I have used the method explained here (https://extensionworkshop.com/documentation/develop/getting-started-with-web-ext), I succeeded in loading the extension into Firefox Nightly v74.a1 from 2020-01-29 on MacOS 10.15.1, but an icon would not be displayed in the top-right area of the browser, no panel could be opened to attempt issue reproduction.

Please give provide us with the exact steps to reproduce. Thank you!

Comment 4

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

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit auto_nag documentation.