On Tue, 4 Aug 2009, Henri Sivonen wrote:
On Aug 3, 2009, at 05:45, Ian Hickson wrote:
Instead of preventing anyone from not using quote marks, I would
instead recommend asking your validator vendor to offer you an option
to require quote marks and warn you when you have forgotten them.
On Aug 3, 2009, at 05:45, Ian Hickson wrote:
On Thu, 23 Jul 2009, Keryx Web wrote:
No suggested text, but a rewrite will be necessary if quotation
marks becomes
a conformance criterion.
Instead of preventing anyone from not using quote marks, I would
instead
recommend asking your
On Thu, 23 Jul 2009, Keryx Web wrote:
I'd say it is safe to say that using quotation marks for attribute
values, always, except perhaps for collapsed, boolean attributes, has
been regarded as best practice for a long time now. Speaking as an
instructor for newbies, enforcing quotation
On Sat, 25 Jul 2009 12:08:23 +0200, Eduard Pascual herenva...@gmail.com
wrote:
On Fri, Jul 24, 2009 at 9:52 PM, Keryx Webwebmas...@keryx.se wrote:
On 2009-07-23 20:32, Eduard Pascual wrote:
While I don't consider a hard requirement would be appropriate, there
is an audience sector this
On Fri, Jul 24, 2009 at 9:52 PM, Keryx Webwebmas...@keryx.se wrote:
On 2009-07-23 20:32, Eduard Pascual wrote:
While I don't consider a hard requirement would be appropriate, there
is an audience sector this discussion seems to be ignoring: Authoring
Tools' developers. IMO, it would be highly
From: Eduard Pascual herenva...@gmail.com
Sent: Saturday, July 25, 2009 5:08 AM
To: Keryx Web webmas...@keryx.se; Bil Corry b...@corry.biz
Cc: whatwg@lists.whatwg.org; Aryeh Gregor simetrical+...@gmail.com
Subject: Re: [whatwg] Make quoted attributes a conformance criteria
On Fri, Jul 24, 2009
On 2009-07-23 20:32, Eduard Pascual wrote:
While I don't consider a hard requirement would be appropriate, there
is an audience sector this discussion seems to be ignoring: Authoring
Tools' developers. IMO, it would be highly desirable to have some
guidelines for these tools to determine when
Keryx Web wrote on 7/24/2009 2:52 PM:
In that post I talked about a common scenario. One developer works on
the business logic. It puts out attribute values. Another developer
works on the presentation logic. He makes templates. Dev 2 omits the
quotes and for a long time it might work, since
On Fri, Jul 24, 2009 at 6:26 PM, Bil Corryb...@corry.biz wrote:
That's a classic XSS vulnerability. The backend developer must know if there
are quotes or not in the template, then encode/sanitize the value accordingly.
It's not XSS if the values are statically provided by the first
developer
Aryeh Gregor wrote on 7/24/2009 5:44 PM:
On Fri, Jul 24, 2009 at 6:26 PM, Bil Corryb...@corry.biz wrote:
That's a classic XSS vulnerability. The backend developer must know if
there are quotes or not in the template, then encode/sanitize the value
accordingly.
It's not XSS if the values
On 23 Jul 2009, at 13:35, Keryx Web wrote:
I'd say it is safe to say that using quotation marks for attribute
values, always, except perhaps for collapsed, boolean attributes,
has been regarded as best practice for a long time now. Speaking as
an instructor for newbies, enforcing quotation
I'd say it is safe to say that using quotation marks for attribute values,
always, except perhaps for collapsed, boolean attributes, has been regarded
as best practice for a long time now.
This always rather seemed like a preference to me, one that gets
supported by consistency considerations
However, the quotation marks being *sometimes* optional is quite
dangerous, since an author needs to exactly remember when they are
needed and when they aren't; and using always quotation marks does
avoid this problem.
If author does not remember he can always use quotes and avoid
this
On Thu, Jul 23, 2009 at 5:28 PM, Rimantas Liubertasriman...@gmail.com wrote:
However, the quotation marks being *sometimes* optional is quite
dangerous, since an author needs to exactly remember when they are
needed and when they aren't; and using always quotation marks does
avoid this
On Thu, Jul 23, 2009 at 8:35 AM, Keryx Webwebmas...@keryx.se wrote:
Hello!
I'd say it is safe to say that using quotation marks for attribute values,
always, except perhaps for collapsed, boolean attributes, has been regarded
as best practice for a long time now. Speaking as an instructor for
On Thu, Jul 23, 2009 at 7:35 PM, Aryeh Gregorsimetrical+...@gmail.com wrote:
Add:
In order to avoid errors and increase readability, using quotes is highly
recommended for all non-omitted attribute values.
I don't think there's any value in having the spec take a stance like
this. It's a
On Thu, 23 Jul 2009 19:32:28 +0100, Eduard Pascual herenva...@gmail.com
wrote:
I don't think there's any value in having the spec take a stance like
this. It's a matter of taste, IMO.
While I don't consider a hard requirement would be appropriate, there
is an audience sector this discussion
17 matches
Mail list logo
