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.

Sign up for GitHub

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

Jump to bottom

webkit-prefixed animation/transition event handler content attributes #5204

Open
annevk opened this issue Jan 10, 2020 · 5 comments · May be fixed by #5205
Open

webkit-prefixed animation/transition event handler content attributes #5204

annevk opened this issue Jan 10, 2020 · 5 comments · May be fixed by #5205

Comments

@annevk
Copy link
Member

annevk commented Jan 10, 2020

As @mtrootyy points out in 0b8e268#commitcomment-36731422 we don't mention them as allowed content attributes and we also don't say they are obsolete.

We should probably say one or the other, right?

cc @domenic @stephenmcgruer
annevk referenced this issue Jan 10, 2020
@stephenmcgruer @domenic
Spec the prefixed CSS Animation/Transition event handlers
0b8e268 
Closes whatwg/compat#118.
stephenmcgruer added a commit to stephenmcgruer/html that referenced this issue Jan 10, 2020
@stephenmcgruer
Add event handler content attributes for prefixed animation/transitio…
4a00c89 
…n events

Fixes whatwg#5204
@stephenmcgruer stephenmcgruer linked a pull request Jan 10, 2020 that will close this issue
Open
@stephenmcgruer
Copy link
Contributor

I believe you're correct. I don't think these are obsolete content attributes, given all browsers do or will soon support them afaik?

@annevk
Copy link
Member Author

annevk commented Jan 10, 2020

Unfortunately HTML uses "obsolete" to mean "obsolete for developers", not "obsolete for implementers".

@stephenmcgruer
Copy link
Contributor

Ohhh, I see. In which case... yes, obsolete. Any preferences on how they might be marked this way? I could just do

onwebkitanimationend (obsolete) in the 'The following event handler content attributes may be specified on any HTML element:' section

?

@annevk
Copy link
Member Author

annevk commented Jan 10, 2020 •
edited
Loading

We should enumerate them in the second list in https://html.spec.whatwg.org/#non-conforming-features as something like

  • onwebkit... on all elements: use on... instead.

stephenmcgruer added a commit to stephenmcgruer/html that referenced this issue Jan 10, 2020
@stephenmcgruer
Add event handler content attributes for prefixed animation/transitio…
6e5c7cf 
…n events

Fixes whatwg#5204
@stephenmcgruer
Copy link
Contributor

PTAL at the PR (#5205); let's continue further discussion there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add event handler content attributes for prefixed animation/transition events stephenmcgruer/html
2 participants
@stephenmcgruer @annevk