Ian,
Not sure if you still use a "live" copy of unicode.xml
and hopefully there will never be a need to change the
HTML character entity definitions but anyway
The editor's draft of the entities spec has been moved to github
https://w3c.github.io/xml-entities/
(The old URL at
On 14/07/2014 09:43, Dirk Schulze wrote:
However, I would like to know what use cases and problems Dirk is trying to
solve by moving these attributes from HTMLElement to Element. Dirk, could you
elaborate on that?
If you add contentEditable to an HMTL element and an SVG element is an
On 26/06/2014 19:06, Tab Atkins Jr. wrote:
On Thu, Jun 26, 2014 at 10:40 AM, Chris Lilley ch...@w3.org wrote:
Better integration of HTML and SVG (and blocking any further
element copying beyond the four existing elements) is really
important.
Much more important than maintaining rendering of
On 27/06/2014 19:01, Tab Atkins Jr. wrote:
On Fri, Jun 27, 2014 at 2:16 AM, David Carlisle dav...@nag.co.uk wrote:
If the parser is changing here could we also change it so that HTML elements
don't auto close math
for which there was also only ever fragile justification.
Yes, no reason
On 13/05/2014 10:26, Dirk Schulze wrote:
Hi,
contentEditable can be fairly useful in SVG as well. It partly works
for inline SVG content in web browsers today.
The question is, should SVGElement add support for
contentEditable/isContentEditable and add it to its interface? Or
should both
On 05/02/2014 13:24, Simon Pieters wrote:
Is there a situation in which it is conforming to use html:title
outside the head in a document where the root is html:html? In
math:annotation-xml?
My reading is yes, and validator.nu at least agrees this is valid
!DOCTYPE html
html
On 12/09/2013 10:24, Anne van Kesteren wrote:
Yeah, we should have to do it for everything we classify as
hyperlink. a, svg:a, area, and link I suppose. I'm not
sure what in MathML would need covering.
more or less anything in MathML takes an href attribute (and then should
act like a href,
On 12/07/2013 18:21, Ian Hickson wrote:
On Wed, 6 Feb 2013, Cameron McCormack wrote:
As part of aligning SVG with some not-so-HTML-specific features of
HTML, the SVG WG would like to support data-* attributes on SVG
elements. In mixed HTML/SVG documents, it seems like you would
want to be
On 06/02/2013 06:41, Cameron McCormack wrote:
As part of aligning SVG with some not-so-HTML-specific features of
HTML, the SVG WG would like to support data-* attributes on SVG
elements. In mixed HTML/SVG documents, it seems like you would want
to be able to use these attributes regardless of
This is a further attempt to resolve the bug report (currently with
status wontfix) regarding XHTML entity definitions.
(whatwg)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17798
(w3c)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13409
By adding
-//W3C//ENTITIES HTML MathML
On 17/01/2013 18:58, Ian Hickson wrote:
On Thu, 17 Jan 2013, David Carlisle wrote:
By adding
-//W3C//ENTITIES HTML MathML Set//EN//XML
To the list in
13.2 Parsing XHTML documents
Of Identifiers that are recognised when parsing XHTML syntax documents.
What problem does this solve?
We
On 17/01/2013 23:31, Ian Hickson wrote:
On Thu, 17 Jan 2013, David Carlisle wrote:
http://www.w3.org/2003/entities/2007doc/xhtmlpubid.html
But basically it solves the problem that the existing list leads to
a situation where data corruption and user confusion are both
inevitable as the only
On 11/09/2012 09:32, Robin Berjon wrote:
.
MathML has similar issues of course (but simpler probably as it doesn't
have the separate font and layout issues that svg has). In its html(5)
incarnation, as well as annotation-xml (which is the traditional mathml
element for foreign stuff (cf
13 matches
Mail list logo
