- From: Yehonatan Daniv via GitHub <noreply@w3.org>
- Date: Sat, 28 Mar 2026 08:45:56 +0000
- To: public-css-archive@w3.org
> On the other hand, the specific comment I heard when discussing this with an internal partner was that it was unfortunate they had to split content up and stitch it back together after the animation effect concludes - this is one of the reasons I'm hoping we can offer a way to achieve these effects declaratively. Of course, currently text animations are very unfriendly towards SEO and A11Y. Another option I know of is to keep the original text visually hidden, and make a copy of the text for the effect and wrap it with an element with an `aria-hidden="true"`. But it's bad anyway. > Re: break inline text boxes into separate boxes and blockify them - can you expand on this? I'd be a little concerned about the performance implications if, for example, we were to make chunks of text addressable by selectors as if they were elements. If you want to animate the `transform` property, you have to not only wrap parts with `<span>`s, but also set `display: inline-block` on each one of them, since `transform` does not work on inline boxes. I agree with your concerns about performance and allow arbitrary text parts selection. That is indeed one of the main obstacles we need to pass. I suppose we'd need some opt-in mechanism to allow part selection and bockifying. This could perhaps behave similar to `will-change`? Like `will-change: text-effect`? > Declarative syntaxes for group effects and staggering timings definitely sound like pieces we would want. Starting with those makes a lot of sense to me - that would give us declarative pieces we could apply to the existing approach of breaking text units into individual elements, and maybe in parallel we can iterate more on how to do the text segmentation. wOOt! -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13689#issuecomment-4147638376 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 28 March 2026 08:45:57 UTC