Sorry I was mainly bikeshedding/still asking a question. I’ll prefix with in future :D.
I don’t have any immediate need for light level really and certainly I can’t imagine many use cases for very granular lumen levels besides perhaps an always on photo frame that was web driven (Something like: https://www.electricobjects.com/) even then I wouldn’t need anything lumen specific just perhaps a little more granular. I’m sure there will be web enabled projectors one day too.
The reason I was mostly asking is that it seems like letting browsers implement their own interpretation of the light levels will never get consistency, could the spec perhaps specify roughly what the lumens each washed, normal and dim relate to?
Also it does feel a little like the fight with view ports having poor sensors is obviously a problem, if the browser made it clear that sensors were unreliable devices would be forced to fix perhaps?
The more I think about it “passive interaction mode” makes sense more as a mode where the device could enable always or other devices could choose to be in passive when the users eye isn’t looking at it. I’m thinking of my watch and it’s certainly more than a boolean state:
- Not looking at it
- In my peripheral vision
- Useful for heads up notifications
- Directly looking at it
I’m not sure if distance doesn’t apply to fixed screens either, for example my sat nav screen is a similar size to a normal phone but the viewing distance means that I am likely going to be upset with phone sized text. My girlfriend might get in the car and then expect the text to be a touch smaller because she is closer to the steering wheel. (It’s a bit of a contrived example as it’s the first I could think of but assume I’m 14ft and she is 4ft and it might be less extreme ). In this example would you expect media queries to be used to modify the viewport size?