On Mon, 18 Jan 2010 13:58:16 +0100, Ian Hickson <i...@hixie.ch> wrote:
I'd like at some point to introduce some sort of "semantic" textContent
that handles <br>, <pre>, <bdo>, dir="", <img alt>, <del>, space-
collapsing, and newline elimination, but there hasn't been much
enthusiasm
around the idea, and it's not clear what else it would be good for.
I've changed the example, at least, to have it work ok, and added a
comment in the example about it.
OK. Won't hold my breath for semantic textContent, but it sounds like a
good solution.
On Thu, 19 Nov 2009, Philip Jägenstedt wrote:
In a (slightly edited) Jack Bauer example [1], Chrome, Firefox and
presumably Safari has the meta elements moved to head. This will
severely break script-based implementation of microdata, which are
likely to be used for the time being until the DOM API is implemented
natively. I can't see any workaround for this, so I suggest that <meta>
simply not be used for microdata, preferably by making it non-conforming
and removing it from the definitions/algorithms.
This is a short-term problem that only affects scripted implementations
that are shipped with the pages, so the workaround is simple: don't use
<meta> and <link>. Any implementations outside of the page can just fix
their parser to be HTML5-compatible.
OK, fair enough.
Thanks for all the other fixes, still reviewing the algorithm change...
--
Philip Jägenstedt
Core Developer
Opera Software
