This page is part of a searchable archive of the Code Style site log. Technical implementation notes that shed light on when, why and how the site has evolved since 2000.
Follow the latest entries to the site log.
Updated the Code Style font survey results with the latest submissions and third place ranking of the Verdana font in the "hot fonts" include file. Added Safari 125, Firebird 0.5 MultiZilla 1.6.0.0.e and Galeon 1.3.8 to browser validation script and distinguished a range of Gecko based browsers in the browser look-up table:
Increased the field width of all standard feedback forms and adjusted the table column proportions to 30%:70% to accommodate.
Actions: Ask a question about this log entry, seek clarification or offer a correction.
Added a FAQ: Site Design link to the local navigation panel for the FAQ section and corrected a fragment anchor link. Restored the contents of the Anchor Points: Fonts and foundries to the main body of the document rather than a server side include.
Actions: Ask a question about this log entry, seek clarification or offer a correction.
Added numerous new answers to the FAQ section, as follows.
Included the FAQ: Site Manager links in the Custom error 400, bad request article for cross reference and re-arranged the links to bring the HTTP error questions to the top of the list. Also removed the Drop down menu FAQ and FAQ: Site Design links from their parent FAQ sections and replaced with "see also" links.
Strengthened the RSS references in the Help and Frequently Asked Questions section. Updated a Linotype link in the Anchor Points: Fonts and foundries listing. Corrected a bad Anchor Points: Cascading Style Sheets link to the CIWAS FAQ.
Set auto-reload properties for servlet classes and files on the production host to false to improve performance.
Actions: Ask a question about this log entry, seek clarification or offer a correction.
Recorded media dependent style sheet conformance results for the Safari browser in screen mode, awaiting results on print mode rendering to complete and publish. Simplified the server side include format of the test case documents.
Actions: Ask a question about this log entry, seek clarification or offer a correction.
Find technical implementation notes on all aspects of the Code Style site.
For a summary overview, see the annotated site log contents.