- From: Sanket Joshi via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 Feb 2021 20:20:03 +0000
- To: public-css-archive@w3.org
There are certainly benefits to the highlight API using live ranges internally: - The `Highlight` constructor can be modified to only accept `StaticRange`. The way I see it is that highlights would create and maintain their own "highlight ranges" internally, which are live, and the static ranges passed into the constructor are just inputs for creating these internal ranges. - We wouldn't need to define any invalidation behavior for the highlight API, and #4598 wouldn't be an issue anymore. However, I don't think we have answers yet regarding the performance tradeoff - live range maintenance cost vs. static range and highlight validation cost. It would be great to know if Safari ran any numbers on this (since they have an experimental implementation already) and what their findings were. cc: @hober, @megangardner Regardless of which option is ultimately chosen, we will need to document this in the spec, as there are painting behavior differences depending on which way we go. -- GitHub Notification of comment by sanketj Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4597#issuecomment-779431037 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 15 February 2021 20:20:04 UTC