1558804 - Find what's preventing user to get CodeMirror JsTerm

Status: RESOLVED WONTFIX

(DevTools :: Console, defect, P3)

Description

[Nicolas Chevobbe [:nchevobbe]]

In Bug 1557324, there are 2 reports of people getting the old jsterm, while the codeMirror pref is on and they don't use assistive technologies.
We should check what's causing this.

Comment 1

[Nicolas Chevobbe [:nchevobbe]]

Peter, Cristian, I'm pinging you here since you both experienced a console input without syntax highlighting.
Do you have Windows high contrast mode enabled?

Comment 2

[petersonazv]

(In reply to Nicolas Chevobbe [:nchevobbe] from comment #1)

Peter, Cristian, I'm pinging you here since you both experienced a console input without syntax highlighting.
Do you have Windows high contrast mode enabled?

Nicolas, thanks for the attention, I don't have the Windows High Contrast mode enabled.

Comment 3

[Cristian Craciun]

No, I don't have the Windows High Contrast mode enabled either.

Comment 4

[James Teh [:Jamie]]

Windows HCM shouldn't cause this. My guess is that there is an application on the users' systems which uses accessibility for some reason, even though it isn't an assistive technology.

Peter, Cristian, when this happens, can you please go to about:support using the address bar, look under the Accessibility section and reply with the information provided for "Accessibility Instantiator"? Thanks.

Nicolas, a while ago, you asked whether we could switch to CodeMirror for the console. I tested a build and provided feedback suggesting it should be okay. (There's the regression of braille users only being able to read a single line at a time - bug 1558405 - but that's what we also experience for Edit as HTML.) What's the status on that from your perspective? (Internal Slack thread)

Comment 5

[Nicolas Chevobbe [:nchevobbe]]

Hello Jamie, thanks for your help on this!

We're currently going through some refactoring for Fission, and I just finished a big patch for the JsTerm. Once that lands, I'll remove the old console input (In Bug 1465149). Thanks for following up on that:)

Comment 6

[petersonazv]

(In reply to James Teh [:Jamie] from comment #4)

Peter, Cristian, when this happens, can you please go to about:support using the address bar, look under the Accessibility section and reply with the information provided for "Accessibility Instantiator"? Thanks.

Hello Jamie,

Since the last update the problem seens to be solved. (I've been trying to replicate for a while)

That said, my "Accessibility Instantiator" value is blank.

Thanks for the attention

Comment 7

[Cristian Craciun]

Build ID 20190723155748
User Agent Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0

I can confirm that the issue is fixed now. Also the "Accessibility Instantiator" value is blank on my side.

Comment 8

[Nicolas Chevobbe [:nchevobbe]]

old jsterm is now removed, so let's close this