I was wondering if 13 of
http://whatwg.org/specs/web-forms/current-work/#addition perhaps could be
changed to say that all attributes where isId returns true should be removed
instead of just the one that was chosen as name of the repetetition template.
This to avoid duplicate IDs in the document.
On Fri, 27 Jan 2006 13:36:46 +0600, Ian Hickson [EMAIL PROTECTED] wrote:
2. With the described algorithm it's possible to build DOM with, for
example, two TITLE nodes, which is invalid. At what point should it be
handled?
Not sure what you are asking. The title parsing is fully defined in
On Fri, 27 Jan 2006, Gervase Markham wrote:
I'd like to present to the group for comment my Content Restrictions
proposal. http://www.gerv.net/security/content-restrictions/
My first impression is that it is far too complex and over-engineered.
The problem with security is that people don't
On Fri, 27 Jan 2006, Alexey Feldgendler wrote:
Sadly, that's not compatible with the Web.
UAs that support frames treat noframes as CDATA. That mea, e.g.,
that script tags inside noframes don't get executed, and that
input elements inside noscript don't get added to forms. We can't
Ian Hickson wrote:
On Sat, 28 Jan 2006, Lachlan Hunt wrote:
Why can't it just be defined that noframes and noscript content gets
parsed exactly as regular markup
Because there are a _lot_ of side-effects of parsing as regular markup.
e.g.
noframes
style.../style
i Foo
On Sat, 28 Jan 2006, Lachlan Hunt wrote:
Ok, I think the noframes case can be handled something like this and the
noscript can probably be handled in a similar way.
link and style
Moved to the document head (just like normal erroneous link element
in the body).
If frames are
Just a note to those of you who reviewed the new parsing rules yesterday:
I changed them today to take into account some feedback from Hyatt.
Basically the old algorithm was creating too many nodes. This is now
fixed, the algorithm only moves the nodes that are being closed, not the
other
Hello folks,
I just read a bit of the spec on w3.org and soon found a point to complain.
How nice that I can do so immediately.
Authors should avoid setting the autofocus attribute on multiple enabled
elements in a document. If multiple elements with the autofocus attribute
set are inserted into
