Bug 1720902 Comment 13 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Thanks. Are some of your monitors High-DPI (also called "retina" display or pixel-scaling) and others not, out of curiosity?

Specifically: if you open the Web Console (Ctrl Shift K) and type in...
```
window.devicePixelRatio
```
...what does it tell you?  (Probably `1` or `2`)

Importantly, **does the answer change** if you drag your window from one monitor to another and query the value again? (just hit "up" and then "enter" to repeat the query)

If so, I could imagine that difference causing some confusion for YouTube's code, if they have some logic that links the video quality to your pixel-density.  This would explain the connection to having multiple monitors which is otherwise a bit mysterious.

(If this is indeed the issue, then it theoretically should affect Chrome in just the same way that it affects Firefox, except that YouTube probably a different codepath for Firefox vs. for Chrome, and maybe this is a wrinkle that they haven't worked out in their Firefox codepath...)
Thanks. Are some of your monitors High-DPI (also called "retina" display or pixel-scaling) and others not, out of curiosity?

Specifically: if you open the Web Console (Ctrl Shift K) and type in...
```
window.devicePixelRatio
```
...what does it tell you?  (Probably `1` or `2`)

Importantly, **does the answer change** if you drag your window from one monitor to another and query the value again? (With the web console still open, just hit "up" and then "enter" to repeat the query.)

If so, I could imagine that difference causing some confusion for YouTube's code, if they have some logic that links the video quality to your pixel-density.  This would explain the connection to having multiple monitors which is otherwise a bit mysterious.

(If this is indeed the issue, then it theoretically should affect Chrome in just the same way that it affects Firefox, except that YouTube probably a different codepath for Firefox vs. for Chrome, and maybe this is a wrinkle that they haven't worked out in their Firefox codepath...)
Thanks. Are some of your monitors High-DPI (also called "retina" display or pixel-scaling) and others not, out of curiosity?

Specifically: if you open the Web Console (Ctrl Shift K) and type in...
```
window.devicePixelRatio
```
...what does it tell you?  (Probably `1` or `2`)

Importantly, **does the answer change** if you drag your window from one monitor to another and query the value again? (With the web console still open, just hit "up" and then "enter" to repeat the query.)

If the value does change, I could imagine that difference causing some confusion for YouTube's code, if they have some logic that links the video quality to your pixel-density.  This would explain the connection to having multiple monitors which is otherwise a bit mysterious.

(If this is indeed the issue, then it theoretically should affect Chrome in just the same way that it affects Firefox, except that YouTube probably a different codepath for Firefox vs. for Chrome, and maybe this is a wrinkle that they haven't worked out in their Firefox codepath...)

Back to Bug 1720902 Comment 13