W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2020

Re: [csswg-drafts] [css-highlight-api][css-contain] static ranges and css-contain (#4598)

From: Dan Clark via GitHub <sysbot+gh@w3.org>
Date: Fri, 18 Dec 2020 19:34:19 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-748281485-1608320058-sysbot+gh@w3.org>
Discussed this with some other Edge folks.

It seems like the most straightforward thing is to not paint a range that crosses the boundary of a contained element, basically treating it as invalid.  This could just be included as part of the invalidation in [Range Updating and Invalidation](https://drafts.csswg.org/css-highlight-api-1/#range-invalidation) where it would be another condition for which "the User Agent must ignore that range".

I expect that authors will generally not have a need to create a highlight that crosses a CSS contain boundary, but an author that does need to do this could use a `Range` instead of a `StaticRange`.

GitHub Notification of comment by dandclark
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4598#issuecomment-748281485 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 December 2020 19:34:20 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:24 UTC