1) For experimentation with CSS, many browsers have a web tool box that can be opened with ctrl-shift-i or similar shortcut and can change the CSS on-the-fly manually. That is a quick way test CSS rules such as the viewport [1] rule being discussed. This seems to be the CSS equivalent of the meta element draft:
@viewport{ zoom: 1.0; width: extend-to-zoom; } 2) Regarding CSS, keeping the viewport settingsin the CSS would allow the presentation and structure to remain more separate. The cgi.c would continue to handle the structure and stay unchanged and the CSS would continue to handle everything pertaining to appearance. So something more-or-less similar to the change below would keep the presentation in the CSS and leave the programming to handle the structure. /Lars [1] https://www.w3.org/TR/css-device-adapt-1/#example-0efe9d5c ----- Index: src/usr.bin/mandoc/mandoc.css =================================================================== RCS file: /cvs/src/usr.bin/mandoc/mandoc.css,v retrieving revision 1.13 diff -u -p -u -r1.13 mandoc.css --- src/usr.bin/mandoc/mandoc.css 9 May 2018 00:45:33 -0000 1.13 +++ src/usr.bin/mandoc/mandoc.css 18 May 2018 15:32:47 -0000 @@ -4,6 +4,8 @@ */ /* Global defaults. */ +@viewport{ zoom: 1.0; + width: extend-to-zoom; } html { max-width: 100ex; } body { font-family: Helvetica,Arial,sans-serif; }