WebUI issue with firefox 48 and Electrolysis

[chelmzy]

Still having the issue on 4.3. Has anyone upgraded to 4.4 and tried FF?

 

[Ashley]

Still having the issue on 4.3. Has anyone upgraded to 4.4 and tried FF?

Use 4.4.5 with FF 50.1.0 on Windows 10 without an issue.

 

[Jackson]

I'm using 4.4-5 and still having this issue with Firefox, for what it's worth.

 

[encript]

I am still having this issue as well. My workaround was to use Chromium. But I really like Firefox, but have no choice at the moment.

 

[dcsapak]

as i described here: https://bugzilla.proxmox.com/show_bug.cgi?id=1223
this is bad combination of firefox/multiprocess/extjs

as long as either

sencha releases an extjs version with a fix
or
mozilla decides to change the touch events in firefox on multiprocessing

you will have to use another browser or the workaround described in the bugreport

 

[torontob]

This is crazy because no browser works now. Chrome has an issue with resizing and see graphs as the page refreshes too often and is not stable. Firefox you can't click. I have the same problem with Proxmox 4.2.2 and latest Firefox and latest Chrome (jumping graphs in summary page).

Use IE? WTH

 

[dcsapak]

Chrome has an issue with resizing and see graphs as the page refreshes too often and is not stable.

can you post a screenshot/video of this? i cannot really imagine what you mean.

Firefox you can't click. I

did you try the workaround posted in the bugreport ?

 

[tijn]

Had the same issue, fixed it as follows:

1. go to: about:config
2. search for: browser.tabs.remote.autostart
3. set value(s) to: false

 

[mvrhov]

https://www.sencha.com/forum/showth...-touchscreen&p=1174857&viewfull=1#post1174857

So proxmox can fix this on their side.

 

[X3n0]

Hi
Have same problem on proxmox ve 5.1-43.
FF58 on windows 10

click mouse right ok
click mouse left only select but impossible to validate

Had the same issue, fixed it as follows:

1. go to: about:config
2. search for: browser.tabs.remote.autostart
3. set value(s) to: false

Work for me, thx

But is not solution final, only proxmox have this problem