-
Notifications
You must be signed in to change notification settings - Fork 31
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
Justify the built-ins. #78
Conversation
index.bs
Outdated
Note: The normative values of these constants are found below. The derivation | ||
of these are explained here, with an implementation in the [[DEFAULTS]] | ||
script. It is expected that these values will change before this | ||
specifcation is finalized. Also, we expect these |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
specifcation is finalized. Also, we expect these | |
specification is finalized. Also, we expect these |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
(There was a second instance; also fixed.)
index.bs
Outdated
- The [no-longer conforming](https://html.spec.whatwg.org/#non-conforming-features) | ||
`<frame>`, `<frameset>`, and `<applet>` tags, which are | ||
outdated versions companions of several elements listed above. | ||
- The `<noframes>`, `<noembed>`, and `<nolayer>` elements. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The `<noframes>`, `<noembed>`, and `<nolayer>` elements. | |
- The `<noscript>`, `<noframes>`, `<noembed>`, and `<nolayer>` elements. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, done!
8f2f3b9
to
7deccfc
Compare
This picks up comments from several sources, including our "spec mentor", the TAG, and issue #69. It provides an explanation where our defaults are coming from, and links those to the HTML spec, so that a reader can go back and forth to understand the issue.
Linking is, honestly, best effort since some elements/attributes don't have good link targets. Particularly the legacy / non-conforming ones don't seem to have a "nice" linkable definition in HTML.