|
| 1 | +<!doctype html> |
| 2 | +<html> |
| 3 | +<head> |
| 4 | + <title>Dillo RFC 004 - Optimized-for META tag</title> |
| 5 | +<style> |
| 6 | +body { |
| 7 | + background: white; |
| 8 | + line-height: 1.5; |
| 9 | + margin: 3em; |
| 10 | + font-family: sans-serif; |
| 11 | + max-width: 72ch; |
| 12 | +} |
| 13 | +h1 { margin-bottom: 1em; } |
| 14 | +header { border: solid 1px #ddd; background: #f5f5f5; padding: 0.25em 1em } |
| 15 | +dt { font-weight: bold } |
| 16 | +dd { margin-left: 2ch; } |
| 17 | +pre { padding-left: 4ch; } |
| 18 | +</style> |
| 19 | +</head> |
| 20 | +<body> |
| 21 | + |
| 22 | +<h1>Dillo RFC 004 - Optimized-for META tag</h1> |
| 23 | + |
| 24 | +<header> |
| 25 | +<dl> |
| 26 | +<dt>State</dt><dd>Draft</dd> |
| 27 | +<dt>Date</dt><dd>Draft on 2025-08-02</dd> |
| 28 | +<dt>Author</dt><dd>Rodrigo Arias Mallo |
| 29 | + < <a href=" mailto:[email protected]" >[email protected]</a>> </dd> |
| 30 | +</dl> |
| 31 | +</header> |
| 32 | + |
| 33 | +<h2>Abstract</h2> |
| 34 | + |
| 35 | +<blockquote> |
| 36 | +<p>This document proposes the <em>optimized-for</em> meta tag to indicate |
| 37 | +web browsers that the authors have explicitly made an effort to improve the page |
| 38 | +for an specific browser.</p> |
| 39 | +</blockquote> |
| 40 | + |
| 41 | +<h2>Background</h2> |
| 42 | + |
| 43 | +<p>Some HTML authors have optimized their websites by removing features that are |
| 44 | +not yet supported in Dillo or by adjusting the CSS rules so that some |
| 45 | +limitations or bugs are not present. |
| 46 | + |
| 47 | +<p>The effect of this behavior causes pages to appear well rendered in Dillo, |
| 48 | +which is a priori an improvement in the overall experience. However, if a page |
| 49 | +has been optimized or not for a given browser is often not easy to determine |
| 50 | +unless explicitly stated. |
| 51 | + |
| 52 | +<p>When testing Dillo on a set of real websites, we need to be sure that those |
| 53 | +pages are not optimized for Dillo, as otherwise it would skew our perception. |
| 54 | + |
| 55 | +<h2>Proposal</h2> |
| 56 | + |
| 57 | +<p>To address this issue, web authors are encouraged to tag their pages if they |
| 58 | +were optimized for Dillo (or other web browsers). We propose the following meta |
| 59 | +tag:</p> |
| 60 | + |
| 61 | +<pre><code> |
| 62 | +<meta name="optimized-for" content="dillo"> |
| 63 | +</code></pre> |
| 64 | + |
| 65 | +<p>Multiple entries must be specified in multiple tags: |
| 66 | + |
| 67 | +<pre><code> |
| 68 | +<meta name="optimized-for" content="dillo"> |
| 69 | +<meta name="optimized-for" content="elinks"> |
| 70 | +<meta name="optimized-for" content="w3m"> |
| 71 | +</code></pre> |
| 72 | + |
| 73 | +<p>The version of the web browser can be <em>optionally</em> specified after the |
| 74 | +<code>/</code> separator, like it would appear in the <code>User-Agent</code> |
| 75 | +HTTP header: |
| 76 | + |
| 77 | +<pre><code> |
| 78 | +<meta name="optimized-for" content="dillo/3.2.0"> |
| 79 | +<meta name="optimized-for" content="elinks/0.11"> |
| 80 | +</code></pre> |
| 81 | + |
| 82 | +<p>Including the version is encouraged, as it will let developers know which |
| 83 | +features were available when the optimization was performed. Multiple version |
| 84 | +lines can also be provided for the same web browser. |
| 85 | + |
| 86 | +<h2>Parsing</h2> |
| 87 | + |
| 88 | +<p>When a web browser loads an HTML page which has an <code>optimized-for</code> |
| 89 | +meta tag that matches the current browser, it can <em>optionally</em> show such |
| 90 | +information in the user interface, so that developers are aware that they are |
| 91 | +seeing a optimized page for that browser. |
| 92 | + |
| 93 | +</body> |
| 94 | +</html> |
0 commit comments