-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
set data-fragment-index on elements #241
Comments
Interesting idea! I anticipate it would be straight forward to implement too. We need to release 2.0 first so I'll tag it for 2.1. If someone PRs this before we release we will review and accept. Contributions welcome! |
FYI, solving asciidoctor/asciidoctor#1305 wouldn't solve the problem for this converter since the implementation is specific to the converter. In other words, the reveal converter can implement passthrough support for data- attributes today without waiting for core. It's a converter concern. All user-defined attributes are available via the API. |
This feature would indeed be great! :) |
It would be great to have possibility to set data-fragment-index on an element. This could allow to make simultaneous appearence or disappearence or whatever else of several elements.
This issue asciidoctor/asciidoctor#1305 would solve the problem, but it is not implemented yet.
General solution could look like:
[.fragment.highlight-red, data-fragment-index=1]#text1#
[.fragment.highlight-red, data-fragment-index=0]#text2#
[.fragment.highlight-red, data-fragment-index=1]#text3#
On the 1st step we get text2 turning red, on the second -- text1 and text3 turning red.
The text was updated successfully, but these errors were encountered: