You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not necessarily a bug, I do not understand the problem space well enough!
Running console.log(screen.colorDepth) while using a standard monitor with 32-Bit color would usually be expected to print 24 (the bits used for the alpha channel aren't counted).
However, in Firefox Dynasty, the above code prints 30 on both my Desktop (connected to what is, as far as I know, a completely boring 32-Bit monitor) and my Macbook Air (using the internal LCD screen).
Is this expected behavior? I can't tell, it seems odd.
P.S. I am in fact quite interested in whether Mavericks could drive an HDR display, the HDR wouldn't work but I think the added color depth might? Something to try some day...
The text was updated successfully, but these errors were encountered:
On Sunday January 26 2025 18:49:21 Jonathan wrote:
P.S. I am in fact quite interested in whether Mavericks could drive an HDR display, the HDR wouldn't work but I think 10 bit color might? Something to try some day...
Since you hijack your own thread: I'm dubious that you'd notice a lot of difference in every day life. IIUC a 10-bit depth will give you 1024 levels of pure gray instead of just 256, but you need content that will actually make use of those extra levels. I wouldn't be surprised if most code and codecs assume that a pixel has 3 8-bit colour components plus an optional 8-bit transparency component.
This is not necessarily a bug, I do not understand the problem space well enough!
Running
console.log(screen.colorDepth)
while using a standard monitor with 32-Bit color would usually be expected to print24
(the bits used for the alpha channel aren't counted).However, in Firefox Dynasty, the above code prints
30
on both my Desktop (connected to what is, as far as I know, a completely boring 32-Bit monitor) and my Macbook Air (using the internal LCD screen).Is this expected behavior? I can't tell, it seems odd.
P.S. I am in fact quite interested in whether Mavericks could drive an HDR display, the HDR wouldn't work but I think the added color depth might? Something to try some day...
The text was updated successfully, but these errors were encountered: