In #2 we discussed a bit the idea of browser's having a setting to let users override the value, and this is what chromium has implemented:
@tunetheweb and I were discussing this a bit in the TAG issue. Let's use this issue for aligning on the question of what the spec should say about this and/or guidance for site developers on ensuring users have control over their experience.
Maybe the spec should focus on the developer guidance of letting users customize behavior, but also mention that user agents may want to consider providing an override as well? Personally I'd hope (and actually expect) that the browser-level override is entirely unnecessary and unused, hopefully that's something we can test with the Chrome implementation.
In #2 we discussed a bit the idea of browser's having a setting to let users override the value, and this is what chromium has implemented:
@tunetheweb and I were discussing this a bit in the TAG issue. Let's use this issue for aligning on the question of what the spec should say about this and/or guidance for site developers on ensuring users have control over their experience.
Maybe the spec should focus on the developer guidance of letting users customize behavior, but also mention that user agents may want to consider providing an override as well? Personally I'd hope (and actually expect) that the browser-level override is entirely unnecessary and unused, hopefully that's something we can test with the Chrome implementation.