-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Editorial: make http-equiv attributes table consistent #9850
Editorial: make http-equiv attributes table consistent #9850
Conversation
476c515
to
8f4bcdf
Compare
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.
I think this ends up losing information. Perhaps it would be clearer to state after the table which keywords are non-conforming and for "Brief description" actually have a brief description.
8f4bcdf
to
dcd892c
Compare
@annevk I've taken the first line from each of the state subheadings and copied it into the description, and - as suggested - listed the non-comforming attributes at the bottom of the table. Let me know if this works. |
dcd892c
to
94eb5cd
Compare
This one has been updated following guidance on #9851 (comment) |
94eb5cd
to
8cd5990
Compare
This formats the wording & HTML around
http-equiv
attribute such that it is consistent with the format described in #9832Note that this table wasn't listed in the OP in #9832 but as it matches the format I figured it should also be included.
/semantics.html ( diff )