You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Emit a warning if the spec is not written in HTML5 (Check new navigation element #281 kind of does that; although ideally it should be a top-level warning, well visible and pointing to some mail message or page explaining that support for doctypes other than HTML5 will be abandoned during 2016)
MAY
Check expected back-to-top link #288 Append back-to-top link at end of document: <p role=navigation id="back-to-top"><a href="#toc"><abbr title="Back to Top">↑</abbr>
Make sure spec illustrations/tables fit within an A4 sheet of paper when printed; use .overlarge class if needed to improve experience on-screen for things that overflow (but note that they might still be issues)
The text was updated successfully, but these errors were encountered:
Upcoming changes so far:
MUST use
/TR/StyleSheets/2016/base.css
MUST use
nav.toc
MUST use meta view port
MAY use
<p role=navigation id="back-to-top">
see http://fantasai.inkedblade.net/style/design/w3c-restyle/2016/sample
[List below added by @tripu, 18 Jan 2016]
<meta name="viewport">
)<nav id="toc">
)w3.org/StyleSheets/TR/2016/
)fixup.js
)//www.w3.org/StyleSheets/TR/2016/logos/W3C
)<ol class="toc">
for the table of contents)<span class="secno">
)<p role=navigation id="back-to-top"><a href="#toc"><abbr title="Back to Top">↑</abbr>
.example
,.def
,.note
,.marker
, and other special box markup.index
for index lists and tables.overlarge
class if needed to improve experience on-screen for things that overflow (but note that they might still be issues)The text was updated successfully, but these errors were encountered: