4 ms·
On one hand, this is something easily done with a parent div, some positioning, and overflow hidden. Probably not worth adding to the spec for such a specific u
by jjcm 4y ago
On one hand, this is something easily done with a parent div, some positioning, and overflow hidden. Probably not worth adding to the spec for such a specific use case.
On the other hand, I do like that this unifies the functionality of svgs and other html elements more. We’ve been seeing svg-like additions to css for a while now, and they’ve been welcome.
Overall I suppose I’m happy for more consistency even if I won’t be using this except in niche cases.
- dgb23 4y agoWhat you’re describing is one of the possible workarounds, yes. Veterans have become accustomed to doing these things over the years. But generally speaking I think that this kind of feature is very useful. It conveys intent, so browsers can optimise things if they choose, and developers get to have cleaner code for free. Secondly there’s plenty of devs and future devs out there who appreciate that there’s a clear way to do this. Workarounds always have caveats and don’t necessarily play nicely with other features.