Markup could be much cleaner if custom elements use the element name,
rather than the is attribute. fancyButton/ instead of button
is=fancyButton/
It's my understanding that if you want to define a strict parser using a
DTD that describes the markup, it's impossible to introduce arbitrary tage
names (as in there are not tag wildcards in a DTD). A document that used
arbitrary tags could not be validated.
On Sun, Aug 12, 2012 at 8:05 AM, Dave
On Sun, Aug 12, 2012 at 2:56 AM, Benjamin BERNARD
benjamin.bern...@benvii.com wrote:
Hi,
I was developing an offline music web App when I discover that is no
Content-length header specified here :
http://www.w3.org/TR/FileAPI/#ProtocolExamples
So when you play an audio/video file stored as a
On Sun, Aug 12, 2012 at 3:36 AM, Florian Bösch pya...@gmail.com wrote:
It's my understanding that if you want to define a strict parser using a DTD
that describes the markup, it's impossible to introduce arbitrary tage names
(as in there are not tag wildcards in a DTD). A document that used
Tab Atkins Jr. jackalm...@gmail.com, 2012-08-12 15:43 -0700:
What Dimitri said, but to address your comment directly, DTD-based
validation is long-dead, at least when applied to HTML. A DTD can't
capture the validity requirements that the HTML spec already imposes,
so it's irrelevant if it
Florian Bösch pya...@gmail.com, 2012-08-12 12:36 +0200:
It's my understanding that if you want to define a strict parser using a
DTD that describes the markup, it's impossible to introduce arbitrary tage
names (as in there are not tag wildcards in a DTD). A document that used
arbitrary tags