- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Feb 2021 23:18:12 +0000
- To: public-css-archive@w3.org
One additional point I'd like to make (@astearns suggested I talk it through) is regarding potential risk to the platform if we get this wrong. There was quite a bit of discussion today about how this feature touches some things that are very important parts of the web platform - in particular, progressive enhancement, how to express meaning in HTML elements, and how it relates to CSS. I agree that all of these things are very important, and I think it's more than fair to say all of us in this group also think so. So what if this feature ships and we end up deciding it was not the right thing, and need to back it out or replace it with a better solution? What would break / how hard would it be to do this? **I think it would be quite easy**: we'd just stop firing `beforematch`, and treat `content-visibility: hidden-matchable` as an alias of `content-visibility: hidden`. Sites could not possibly break due to this, in the sense of a broken display or javascript errors. Likewise it should also still be possible for users to find all the content they want, because sites can't rely on find-in-page or search engines to drive users to the content they want - the sites also have UX affordances such as buttons, scrolling widgets, or accordion icons that have click event listeners to show the hidden content. The main problem for sites would be if they come to depend (in the sense of expecting it to work as part of their UX plan for users) more deeply on `beforematch` and would be unhappy to lose the feature. If the feature needs to get backed out or replaced, and this sites-want-it problem is deemed important enough, then we'd need to have a replacement feature, fulfilling the same use cases, already implemented before the old one is removed, and give sites some time to migrate. -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5595#issuecomment-776309984 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 February 2021 23:18:14 UTC