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

Defer onfocusin and onfocusout #715

Closed
takenspc opened this issue Jul 14, 2019 · 1 comment · Fixed by #740
Closed

Defer onfocusin and onfocusout #715

takenspc opened this issue Jul 14, 2019 · 1 comment · Fixed by #740

Comments

@takenspc
Copy link
Contributor

In SVG 2 spec, elements have graphical event attributes (onfocusin and onfocusout) while SVG 2 spec doesn't have formal definition of them.

Example:
https://svgwg.org/svg2-draft/struct.html#SVGElement

graphical event attributes — ‘onfocusin’, ‘onfocusout’

On the other hand, HTML Standard has a few issues about formalization of onfocusin and onfocusout.

I think it is better to drop onfocusin and onfocusout for a while and update global event attributes once onfocusin and onfocusout were defined in HTML Standard.

@css-meeting-bot
Copy link
Member

The SVG Working Group just discussed Defer onfocusin and onfocusout, and agreed to the following:

  • RESOLUTION: Remove from SVG2 but automatically include again when defined by HTML. Add a note.
The full IRC log of that discussion <krit> topic: Defer onfocusin and onfocusout
<krit> GitHub: https://github.com//issues/715
<krit> AmeliaBR: it really depends on the feedback we get from HTML
<krit> AmeliaBR: I wonder if we could have some wording. I wonder why we have them part of the events. They don't seem to be part of the standard mixing.
<krit> s/mixing/mixins/
<krit> AmeliaBR: If HTML gets them we get them automatically.
<krit> myles: sounds like a good argument to defer until HTML gets them.
<krit> AmeliaBR: we should not be defining them other than by using HTMLs mixins and definition
<krit> krit: were they part of SVG 1.1?
<krit> AmeliaBR: no, we don't say anything anywhere. They are just listed in the element definitions and the definitions have disappeared.
<krit> AmeliaBR: Propose to remove them for now. Assuming that they will be included by HTML's mixins, they will get included in HTML.
<krit> AmeliaBR: They actually were in SVG 1.1
<krit> krit: Still support your proposal but should add a note then
<krit> AmeliaBR: we have a note for other events where we now use HTML's definition. We can add a note that they should only be implemented in a way theat they are consistent with HTML.
<krit> RESOLUTION: Remove from SVG2 but automatically include again when defined by HTML. Add a note.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants