Skip to content
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

Allow CSS counter integer to be in data- attribute #271

Closed
dragontheory opened this issue Feb 6, 2023 · 2 comments
Closed

Allow CSS counter integer to be in data- attribute #271

dragontheory opened this issue Feb 6, 2023 · 2 comments

Comments

@dragontheory
Copy link

dragontheory commented Feb 6, 2023

Auto pagination and so many other features could be done in pure CSS if unique IDs could be generated on the fly. One easy way to do that and keep everything in order would be to allow a data- attribute access to the CSS counter or ordered list :marker integer.

In combination with :has(), "self aware" GUIs, watching for the presence of data changes (on the fly validation) and or easily counting number of children, siblings, and or parents, would become a welcome reality.

Preset repetitive GUI logic (open/close, hide/show DOM elements, etc.) governed by application business logic and suddenly it's running on its own.

No more obfuscated workarounds. Straight forward logic. Less developer cognitive load.

Let the CSS renaissance begin!

Thank you for your time and consideration.

@dragontheory dragontheory changed the title Allow CSS counter to be in data- attribute Allow CSS counter integer to be in data- attribute Feb 6, 2023
@nt1m
Copy link
Member

nt1m commented Feb 7, 2023

That sounds like #86

@foolip
Copy link
Member

foolip commented Feb 7, 2023

Hi @dragontheory, thanks for suggesting this! However, we've just launched Interop 2023 and have not yet begun the process for next year. As @nt1m says this sounds similar to #86. When the proposal period starts for next year, this would be a welcome proposal.

I'll go ahead and close this, but don't take that as a rejection of the idea, we're just not ready yet!

@foolip foolip closed this as completed Feb 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants