Please rename the subject when you're going to discuss the work on a new feature.
We made a lot of progress regarding CSS containment [1].
Rob and I have finished the layout containment and size containment [2].\o/
And the patches of paint containment and style containment are ready for review now [3].
So we think now it's time to move on to content-visibility:
(https://www.w3.org/TR/css-contain-2/#content-visibility)
That seems premature. Have we implemented all the perf optimizations for layout, size, & paint containment? I'd rather not start piling on more features before we get to a point where we're happy with the performance of these features.
Since content-visibility depends on paint and style containment, we will do some specification research first, then prototype it based on Rob's patches.
Does the research part also include making a judgement call as to whether it's a good idea at all? It's wholly unclear to me that content-visibility is a feature we'd like to implement in WebKit given its implications to the accessibility and other browser features.
- R. Niwa