1419376 - VMware Horizon Web Client does double-typing

Status: RESOLVED DUPLICATE of bug 1504692

(Core :: DOM: UI Events & Focus Handling, defect, P1)

Description

[cmitasch]

Attachment: out-2.ogv

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce:

Since the upgrade to Firefox 57.0, using VMwar Horzion Web Client is nearly unusable since characters are typed multiple times if typing in normal speed.


Actual results:

See the video attached


Expected results:

don't do double types

Comment 1

[cmitasch]

the problem also exists when running Firefox in Windows 10.
It's definitely related with the new version 57.0.

Comment 2

[cmitasch]

If you don't have a VMware View Horizon Web Client available, you could test it here:
https://portal.vmtestdrive.com/

Just register, then login and select "LAUNCH Services", "​Horizon HTML Access​", "Europe".
Then I logged in on "VMWDEMO" with the registered username.
Finally I selected "EMEA WIN10", opened Notepad and I experienced the same double-typing issue as on our environment.

Christoph

Comment 3

[Cosmin Muntean [:cmuntean], Ecosystem QA - PTO until 18 Sept - ping mcoman for any question]

I haven't managed to create an account, I get a " We're sorry, but the email domain you have submitted is not currently allowed to register on the VMware TestDrive system." error. I have tried with multiple email accounts but it did not work with any.

Given the fact that I can't test this issue and the problem appeared after updating to Firefox 57, could you please try to find a regression range using Mozregression tool?
Information on the tool is available at http://mozilla.github.io/mozregression/. Please don't hesitate to contact us if you encounter any problems.

Comment 4

[Andrew Overholt [:overholt]]

A regression window is still crucial here but Stone can take it from there once we've got a window.

Comment 5

[Ming-Chou Shih [:stone]]

Hi Christoph,
I can't get an account for testing either. Could you please try to disable the preference 'input_event_queue.supported' and test if this is still reproducible? Thanks.
steps:
1. enter about:config in url bar
2. search 'input_event_queue.supported' and change it to false
3. restart browser

Comment 6

[cmitasch]

Hi,

disabling input_event_queue.supported did not help.

I will give mozregression a try and will get back with the results to you.

Christoph

Comment 7

[cmitasch]

2017-12-05T13:27:34: INFO : Narrowed inbound regression window from [8b1881ea, 665ea291] (3 builds) to [d6e1c5f5, 665ea291] (2 builds) (~1 steps left)
2017-12-05T13:27:34: DEBUG : Starting merge handling...
2017-12-05T13:27:34: DEBUG : Using url: https://hg.mozilla.org/integration/mozilla-inbound/json-pushes?changeset=665ea291fce432c014fa48dedc94f204f3dd1fb4&full=1
2017-12-05T13:27:35: DEBUG : Found commit message:
Bug 1390044 - Enable the input event queue on nightly. r=smaug

MozReview-Commit-ID: 9lK19VNDCGr

2017-12-05T13:27:35: INFO : The bisection is done.
2017-12-05T13:27:35: INFO : Stopped
--------------------
I disabled the event queue in about:config again, but it did not help.

Comment 8

[cmitasch]

I seems that restarting the browser with disabled event queue helps.

Comment 9

[Ming-Chou Shih [:stone]]

Not sure but I guess this is the same as bug 1421805

Comment 10

[Julien Cristau [:jcristau]]

We have a regression range in comment 7.

Does this need a new assignee?

Comment 11

[Andrew Overholt [:overholt]]

(In reply to Julien Cristau [:jcristau] from comment #10)
> We have a regression range in comment 7.
> 
> Does this need a new assignee?

Yes. Maybe Olli since he reviewed some of the input event queue work Stone did?

Comment 12

[Olli Pettay [:smaug][[e-mail]]]

I don't expect to get to this any time soon.

Comment 13

[Mike Kaply [:mkaply]]

This is going to be a pretty major problem when the Firefox 60 ESR releases.

We are effectively breaking enterprise applications.

Do we have any idea why enabling the event queue broke this? 

See also bug 1421805

Comment 14

[Mike Kaply [:mkaply]]

From VMWare:

vCenter 6.7 U1 fixes this and it hit GA today. The release notes and KB articles should be updated soon to reflect this.

Please let me know if you get a chance to test.