justification for base tag; relative base might be OK in practice

diff --git a/doc/todo/design_for_cross-linking_between_content_and_CGI.mdwn b/doc/todo/design_for_cross-linking_between_content_and_CGI.mdwn
index d00368bfbdb826b41786e41058b9966ba0d20b02..64b3e848c056dd5ae29b85593c4fb8ffda5c87fd 100644 (file)
--- a/doc/todo/design_for_cross-linking_between_content_and_CGI.mdwn
+++ b/doc/todo/design_for_cross-linking_between_content_and_CGI.mdwn
@@ -32,8 +32,10 @@ rather than solving one bug at the cost of exacerbating another.
 * URIs in RSS feeds must be absolute, because feed readers do not have
   any consistent semantics for the base of relative links
 
-* If we have a `<base href>` then the HTML spec says it must be
-  absolute
+* If we have a `<base href>` then HTML 4.01 says it must be
+  absolute, although HTML 5 does relax this by defining semantics
+  for a relative `<base href>` - it is interpreted relative to the
+  "fallback base URL" which is the URL of the page being viewed
   ([[bugs/trouble_with_base_in_search]],
   [[bugs/preview_base_url_should_be_absolute]])
 
@@ -62,6 +64,11 @@ rather than solving one bug at the cost of exacerbating another.
   [[forum/Using_reverse_proxy__59___base_URL_is_http_instead_of_https]],
   [[forum/Dot_CGI_pointing_to_localhost._What_happened__63__]])
 
+* For relative links in page-previews to work correctly without
+  having to have global state or thread state through every use of
+  `htmllink` etc., `cgitemplate` needs to make links in the page body
+  work as if we were on the page being previewed.
+
 # "Would be nice"
 
 * In general, the more relative the better