This document proposes the optimized-for meta tag to indicate web browsers that the authors have explicitly made an effort to improve the page for an specific browser.
Some HTML authors have optimized their websites by removing features that are not yet supported in Dillo or by adjusting the CSS rules so that some limitations or bugs are not present.
The effect of this behavior causes pages to appear well rendered in Dillo, which is a priori an improvement in the overall experience. However, if a page has been optimized or not for a given browser is often not easy to determine unless explicitly stated.
When testing Dillo on a set of real websites, we need to be sure that those pages are not optimized for Dillo, as otherwise it would skew our perception.
To address this issue, web authors are encouraged to tag their pages if they were optimized for Dillo (or other web browsers). We propose the following meta tag:
<meta name="optimized-for" content="dillo">
Multiple entries must be specified in multiple tags:
<meta name="optimized-for" content="dillo">
<meta name="optimized-for" content="elinks">
<meta name="optimized-for" content="w3m">
The version of the web browser can be optionally specified after the
/ separator, like it would appear in the User-Agent
HTTP header:
<meta name="optimized-for" content="dillo/3.2.0">
<meta name="optimized-for" content="elinks/0.11">
Including the version is encouraged, as it will let developers know which features were available when the optimization was performed. Multiple version lines can also be provided for the same web browser.
When a web browser loads an HTML page which has an optimized-for
meta tag that matches the current browser, it can optionally show such
information in the user interface, so that developers are aware that they are
seeing a optimized page for that browser.