On Wed, 23 Jun 2010, Benjamin M. Schwartz wrote:
The HTML5 spec appears to allow inside an attribute value. For
example, the following page (note the body tag) passes the experimental
HTML5 validator at w3c.org:
!DOCTYPE HTMLhtmlheadtitle/title/head
body class=32
/body/html
I think
It seems like what you want here is for browsers to parse as they do now, but
a particular
subset of browser-accepted syntax to be enshrined so that when defining your
restrictions
over content you control you can just say follow the spec instead of
follow the spec and
don't put '' in
On 6/29/10 5:56 AM, Skrol29 wrote:
It seems like what you want here is for browsers to parse as they
do now, but a particular subset of browser-accepted syntax to be
enshrined so that when defining your restrictions over content you
control you can just say follow the spec instead of follow the
On 24 Jun 2010, at 14:11, Benjamin M. Schwartz wrote:
Why would it simplify parsing?
It greatly simplifies parsing when you just want to extract entire
tags, without immediately parsing the attributes.
If you mean parsing with regular expressions, then I think that's a bad
practice and
I disagree, there are so many other things you need to take account of if
you were (for example) getting all the text out of an HTML document. Text
and markup in comment nodes would just through a spanner in the works for
starters.
It all boils down to the fact that the only thing disallowing in
On 2010-06-25 11:46, Skrol29 wrote:
A agree disallowing chars in attributes greatly simplifies parsing. Not
only with regular expressions, but any parsing.
If are allowed, it means that in order to found the end of the element
you do have to read all attributes before. This is very costy. Just
A agree disallowing chars in attributes greatly simplifies parsing. Not
only with regular expressions, but any parsing.
If are allowed, it means that in order to found the end of the element
you do have to read all attributes before. This is very costy.
You just need two extra states in the
On Fri, 2010-06-25 at 13:28 +0100, Kornel Lesinski wrote:
A agree disallowing chars in attributes greatly simplifies parsing. Not
only with regular expressions, but any parsing.
If are allowed, it means that in order to found the end of the element
you do have to read all attributes
On Thu, Jun 24, 2010 at 2:34 PM, Benjamin M. Schwartz
bmsch...@fas.harvard.edu wrote:
[...]
HTML5 is about making a spec that matches common practice, right? In
practice, no one puts in attribute values.
The data disagrees: http://philip.html5.org/data/gt-in-attribute.txt
--
Philip Taylor
-Message d'origine-
De : Lachln Hunt [mailto:lachlan.h...@lachy.id.au]
Envoyé : vendredi 25 juin 2010 14:18
À : Skrol29
Cc : 'WHAT Working Group'; b...@alum.mit.edu
Objet : Re: [whatwg] Allowing in attribute values
On 2010-06-25 11:46, Skrol29 wrote:
A agree disallowing chars
On 25.06.2010 15:52, Skrol29 wrote:
...
Allowing in attributes is a small gift of tolerance for webmasters, but
implies major complications for the industry.
Disallowing falls within the purpose of simplifying the grammar, like when
XHTML disallowed the uppercase for element and attribute
On 6/25/10 9:52 AM, Skrol29 wrote:
In another hand, in the industry the tolerance to the spec is often very low in
order build simple, fast and robust processes. They are also many parsing
purposes that care about some elements and don't care about others.
As I see it, there are two
On 06/25/2010 11:50 AM, Boris Zbarsky wrote:
It seems like what you want here is for browsers to parse as they do
now, but a particular subset of browser-accepted syntax to be enshrined
so that when defining your restrictions over content you control you can
just say follow the spec instead of
One advantage is almost the same as your footnote: JavaScript source is
permitted in the values of many attributes, and can certainly contain the
operator.
On Jun 25, 2010 12:34 PM, Benjamin M. Schwartz bmsch...@fas.harvard.edu
wrote:
On 06/25/2010 11:50 AM, Boris Zbarsky wrote:
It seems like
On Thu, 24 Jun 2010 04:13:56 +0200, Benjamin M. Schwartz
bmsch...@fas.harvard.edu wrote:
The HTML5 spec appears to allow inside an attribute value. For
example, the following page (note the body tag) passes the experimental
HTML5 validator at w3c.org:
!DOCTYPE HTMLhtmlheadtitle/title/head
Benjamin M. Schwartz bmsch...@fas.harvard.edu wrote:
The HTML5 spec appears to allow inside an attribute value. For
example, the following page (note the body tag) passes the
experimental
HTML5 validator at w3c.org:
!DOCTYPE HTMLhtmlheadtitle/title/head
body class=32
/body/html
I
On 6/24/2010 10:13 AM, Benjamin M. Schwartz wrote:
The HTML5 spec appears to allow inside an attribute value. For
example, the following page (note the body tag) passes the experimental
HTML5 validator at w3c.org:
!DOCTYPE HTMLhtmlheadtitle/title/head
body class=32
/body/html
I think should
On 24.06.2010 10:00, Henri Sivonen wrote:
Benjamin M. Schwartzbmsch...@fas.harvard.edu wrote:
The HTML5 spec appears to allow inside an attribute value. For
example, the following page (note the body tag) passes the
experimental
HTML5 validator at w3c.org:
!DOCTYPE
On 06/24/2010 03:43 AM, Anne van Kesteren wrote:
Why would it simplify parsing?
It greatly simplifies parsing when you just want to extract entire tags,
without immediately parsing the attributes.
It's rather nice to allow it for the
iframe srcdoc feature.
The srcdoc already needs to be
On 06/24/2010 05:22 AM, Brett Zamir wrote:
I do not see any reference to this in the XHTML 1.0 specification (nor
XHTML 1.1), and in XML, section 2.4, it states only that it must be
escaped if part of the sequence ]] in content, which I guess means
only element content. E4X also does not
On 24.06.2010 15:34, Benjamin M. Schwartz wrote:
On 06/24/2010 05:22 AM, Brett Zamir wrote:
I do not see any reference to this in the XHTML 1.0 specification (nor
XHTML 1.1), and in XML, section 2.4, it states only that it must be
escaped if part of the sequence ]] in content, which I guess
On 24 Jun 2010, at 14:11, Benjamin M. Schwartz wrote:
Why would it simplify parsing?
It greatly simplifies parsing when you just want to extract entire tags,
without immediately parsing the attributes.
If you mean parsing with regular expressions, then I think that's a bad
practice and
On Thu, Jun 24, 2010 at 8:20 AM, Benjamin M. Schwartz
bmsch...@fas.harvard.edu wrote:
On 06/24/2010 11:04 AM, Kornel Lesinski wrote:
If you mean parsing with regular expressions, then I think that's a bad
practice and shouldn't be encouraged.
Worldwide, regarding HTML, I'm sure there is 100
On Thu, 2010-06-24 at 09:01 -0700, Tab Atkins Jr. wrote:
On Thu, Jun 24, 2010 at 8:20 AM, Benjamin M. Schwartz
bmsch...@fas.harvard.edu wrote:
On 06/24/2010 11:04 AM, Kornel Lesinski wrote:
If you mean parsing with regular expressions, then I think that's a bad
practice and shouldn't be
On Thu, Jun 24, 2010 at 9:34 AM, Benjamin M. Schwartz
bmsch...@fas.harvard.edu wrote:
HTML5 is about making a spec that matches common practice, right? In
practice, no one puts in attribute values.
HTML5 matches common practice when necessary to ensure
interoperability. That doesn't apply to
The HTML5 spec appears to allow inside an attribute value. For
example, the following page (note the body tag) passes the experimental
HTML5 validator at w3c.org:
!DOCTYPE HTMLhtmlheadtitle/title/head
body class=32
/body/html
I think should be disallowed inside attribute values. It is
26 matches
Mail list logo
