On 25/04/2019 15:58, Yoav Weiss wrote:
>
>
> On Thu, Apr 25, 2019 at 3:51 PM Manuel Rego Casasnovas <
re...@igalia.com
> <mailto:
re...@igalia.com>> wrote:
>
>
> On 25/04/2019 14:44, Yoav Weiss wrote:
> > Developers that would still want to force that behavior (in Chromium)
> > would be able to use the "style" keyword.
> > It would be good to introduce counters for "style" containment. If
> usage
> > is high after this removal, that could be evidence that developers
> > actually find it useful. If it isn't, it could be evidence to the
> > contrary. (although weaker one, as single-vendor support may hold
> usage
> > back)
>
> BTW, note that "contain: style" implementation has been pretty broken
> (see
crbug.com/855798 <
http://crbug.com/855798>,
crbug.com/869296
> <
http://crbug.com/869296>,
crbug.com/882383 <
http://crbug.com/882383>,
>
crbug.com/882385 <
http://crbug.com/882385>). So I'm not sure how
> many usage it actually has, or if
> it's actually doing anything in some of the cases where it's used.
>
>
> Thanks for the input! I'd take this to mean that if it is used, it's
> really strong evidence of its necessity, but if it isn't we can't know
> for sure why.
Or maybe when the bugs are fixed and it starts to do more things, people
need to remove style containment in some places they're using it now.
So I guess we cannot know a lot about the usage yet, until the feature
is fixed. Maybe we can add some very specific use counters for the
things that are actually working on style containment and make a
difference when you don't use it.
Bye,
Rego