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

follow up to css revision #2433

Open
4 tasks
pkra opened this issue Feb 12, 2025 · 1 comment
Open
4 tasks

follow up to css revision #2433

pkra opened this issue Feb 12, 2025 · 1 comment
Assignees
@pkra
Labels
editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo good first issue

Comments

@pkra
Copy link
Member

pkra commented Feb 12, 2025 •
edited
Loading

Follow up to #2410.

Reviewing the spec css identified various other issues. Let's collect them here

  • [spec HTML] nested .rfc2119 -- look like simple authoring errors
    • ARIA:

      aria/index.html

      Line 423 in 077621f

      <p>Normative sections provide requirements that authors and [=user agents=] must follow for an implementation to conform to this specification. The keywords <em class="rfc2119">MUST</em>, <em class="rfc2119">MUST NOT</em>, <em class="rfc2119">REQUIRED</em>, <em class="rfc2119">SHALL</em>, <em class="rfc2119">SHALL NOT</em>, <em class="rfc2119">SHOULD</em>, <em class="rfc2119">RECOMMENDED</em>, <em class="rfc2119">MAY</em>, and <em class="rfc2119">OPTIONAL</em> in this document are to be interpreted as described in <cite><a href="http://www.rfc-editor.org/rfc/rfc2119.txt">Keywords for use in RFCs to indicate requirement levels</a></cite> [[!RFC2119]]. RFC-2119 keywords are formatted in uppercase and contained in an element with <code>class="rfc2119"</code>. When the keywords shown above are used, but do not share this format, they do not convey formal information in the RFC 2119 sense, and are merely explanatory, i.e., informative. As much as possible, such usages are avoided in this specification.</p>
    • other specs have similar<em class="rfc2119">....</em> which should be removed.
  • [spec HTML] highlight.js failing to identify snippet language -- add explicit source info
  • aria.js: dl with .compact (for lists of roles and states&props - 5.4, 6.8) - class no longer used
  • [respec?] configure highlightjs theme (to be more accessible)
@pkra pkra added the editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo label Feb 12, 2025
@pkra pkra self-assigned this Feb 12, 2025
pkra added a commit that referenced this issue Feb 12, 2025
@pkra
editorial(common.css): remove dl.compact dt
e031ae4 
As per editors discussion, we switch to the default respec style.
Cf. #2433 for follow up on aria.js (which generates these elements).

Part of #2410
@pkra pkra mentioned this issue Feb 12, 2025
Open
37 tasks
@pkra
Copy link
Member Author

pkra commented Feb 12, 2025

Some of these items are good first issues (e.g., fixing the HTML source).

pkra added a commit that referenced this issue Feb 13, 2025
@pkra
editorial(common.css): remove dl.compact dt
49fd1e4 
As per editors discussion, we switch to the default respec style.
Cf. #2433 for follow up on aria.js (which generates these elements).

Part of #2410
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pkra pkra

Labels
editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo good first issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pkra