It's come up several times now and there have been ideas that I think are worth tackling. I managed to have a good discussion with @scottaohara today and I think we decided the following made sense...
We should respect a css custom property in our custom element that will stand in for a future OS/browser setting exposed as env/const that allows negotiation. Effectively, the idea is that the author is beginning with 'good content' and laying out what they believe is most useful/pleasant/efficient as a way to consume content at different media or sizes - but authors might disagree with that in a few ways and allowing them to have control over this somehow seems ideal. So I proposed is a css custom property which will be read off root before any affordance change happens - let's hyptothetically call is prefers-sectioning-affordance and it would have values - I would propose the initial set would be:
auto (default) - just do what the MQ says when it says
none - please leave it as plain, non-interactive HTML
once go ahead and set the affordance style once, but then leave it. This can be useful for people who use certain tools which might cause rapid or unnecessary changes - they don't particularly care which affordance, but once it is set, don't change it.
- IE, just always show them as 'collapse' or 'tabs' or whatever is easier for me to use.
This would allow someone to set a user stylesheet, or extensions which provide it, or sites to fairly easily provide interfaces to make it possible to let users be in control. Given some research here then, we can craft an actual proposal.
It's come up several times now and there have been ideas that I think are worth tackling. I managed to have a good discussion with @scottaohara today and I think we decided the following made sense...
We should respect a css custom property in our custom element that will stand in for a future OS/browser setting exposed as env/const that allows negotiation. Effectively, the idea is that the author is beginning with 'good content' and laying out what they believe is most useful/pleasant/efficient as a way to consume content at different media or sizes - but authors might disagree with that in a few ways and allowing them to have control over this somehow seems ideal. So I proposed is a css custom property which will be read off root before any affordance change happens - let's hyptothetically call is
prefers-sectioning-affordanceand it would have values - I would propose the initial set would be:auto(default) - just do what the MQ says when it saysnone- please leave it as plain, non-interactive HTMLoncego ahead and set the affordance style once, but then leave it. This can be useful for people who use certain tools which might cause rapid or unnecessary changes - they don't particularly care which affordance, but once it is set, don't change it.This would allow someone to set a user stylesheet, or extensions which provide it, or sites to fairly easily provide interfaces to make it possible to let users be in control. Given some research here then, we can craft an actual proposal.