Leif H. S. wrote:
Hi! Due to the new Revision feature I found many PI's in the
changes.html document. And in particular the one found in the title
element bothered me:
|<title><?xxe-sn hlc2iz4i 1z149g8?>Change history</title> |
Yes, we noticed that too and didn't care.
This use of PI's has two issues:
1. Except in elements such as <script> and <style>, its breaks formal
HTML5 validity: processing instructions where permitted in HTML4 and
XHTML1 but are not permitted in HTML5 documents (they are permitted
in XHTML5 documents).
2. In the title elements, PIs are permitted, however, because of
special parsing rules for the title element, browsers render PIs to
the user. (PS: This only happens when browsers parse the document as
HTML - if they parse it as XHTML, then it is not visible.)
We consider these limitations to be HTML5 design flaws. A standard like
(X)HTML5 should either fully support PIs or not claim to be XML at all.
BTW: While <!-- comments --> are permitted inside the title element,
they too get rendered in browsers, when in HTML mode. Thus, I guess, you
get the picture.
*Proposal:* How about using the data-* attribute that HTML5 permits,
instead? http://www.w3.org/TR/html5/dom.html#attr-data-* If you did go
for this solution, the above <title> element, could look one of the
following ways:
|<title data-xxe-sn="hlc2iz4i 1z149g8">Change history</title> <title
data-xxesn="hlc2iz4i 1z149g8">Change history</title> <title
data-sn="hlc2iz4i 1z149g8">Change history</title> <title
data-sn-hlc2iz4i_1z149g8="">Change history</title> |
If you take some precautions, you could even treat the data-* attribute
like an ad-hoc boolean attribute:
|<title data-sn-hlc2iz4i_-1z149g8="">Change history</title> |
Since the data-* attribute is fully HTML5-conforming, you would not risk
that some people would remove these attributes due to validity concerns
- hence, in that sence/from that angle, it would be more robust.
I'm sorry but we'll not implement what you suggest. The simplest is that
you don't use this feature at all, given the drawbacks it has for your
use case.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
