Permanence issues #30
The spec so far seems to derive appeal and simplicity from thinking of a
But it's not. In three respects:
How should browsers behave if the JS twiddles the bit live over time?
In the end, I realize this may be up to individual specs using
It's a runtime knob because it can change at runtime (for instance when a tab cast switches from casting a spreadsheet to casting an Youtube video).
The effect of changing it at runtime should be to make things better for the new value of the hint (typically munge codec sharpness vs smoothness parameters).
The hint was defined because automatic detection is sometimes wrong. If it hadn't been needed, the asker wouldn't have asked for it.