- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Feb 2021 17:11:58 +0000
- To: public-css-archive@w3.org
> There is still one thing which I don't like, and that is the "if you fail to unhide once, you never get the event anymore" because I don't see why it's useful to punish the page in this way. If calling `onbeforematch` didn't reveal the content, you move to the next match and call it a day, I don't see why we want a persistant flag hidden to the page that disables the feature, that sounds like a footgun. The reason is to prevent the page from violating privacy by trying to read what you are typing into the search. However, it could be that this particular privacy mitigation doesn't end up being the best idea. How about we have spec text such as "the User Agent *may* skip calling page-defined event handlers if doing so is likely to lead to a privacy risk for the user." ? -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5595#issuecomment-777650204 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 February 2021 17:12:00 UTC