Confirmed users
95
edits
(updated fennec bugzilla links, added another fennec issue) |
(Two monitors configurations (between browsers) - added data) |
||
Line 22: | Line 22: | ||
===== Two monitors configurations (between browsers) ===== | ===== Two monitors configurations (between browsers) ===== | ||
* performed by: avih | * performed by: avih | ||
* Test how well browsers use the correct refresh rate in a two monitors configuration. | |||
* tested using: http://www.vsynctester.com/index.html | |||
* Procedure - with a single browser window, check all combinations of the following variables: | |||
** Browser: Firefox release / nightly / Chrome / IE / Edge (win10 only) | |||
** OS: Windows 8.1 / Windows 10 | |||
** Windows "main" display: laptop's built-in / external monitor | |||
** The browser window is at: laptop's built-in / external monitor | |||
** Laptop's built in display refresh rate: lower/identical/higher than that of the external monitor | |||
* Observations: | |||
** When both monitors have the same rate - all browsers behave optimally. | |||
** Firefox is the best, with only a single suboptimal case (and not worse than other browsers in this case): | |||
*** When the Windows "main" display has lower rate than the extended-to display (regardless if the main is the built-in/external, or windows 8.1/10), then the animation rate on the extended-to display is the refresh rate of the "main" display (therefore lower than it should be). | |||
** Chrome comes second: | |||
*** Same issue as Firefox, plus few other cases where it incorrectly uses the rate of the "other" monitor. | |||
** IE/Edge are last: | |||
*** Same issues as Firefox and Chrome, plus when the main display is the laptop, and it has a lower rate than the external display, on both win8/10 -> it uses weird rAF rate (67hz, 64hz) which doesn’t match any monitor. | |||
===== Memory usage of e10s, non e10s (Firefox and others) ===== | ===== Memory usage of e10s, non e10s (Firefox and others) ===== |