On Mon, 12 Dec 2005, Gorm Haug Eriksen wrote:
The title in the specification is a bit strange. Perhaps form should be
removed from the chapter title (3. The repetition model for repeating
form controls)?
Well, the original use case was repeating form controls, and it's in a
forms-related
On Tue, 13 Dec 2005, Dean Edwards wrote:
Ian Hickson wrote:
Is this only because it is easier to implement the DOM interface on a
limited set of elements than on all elements?
Basically, yes. As far as the DOM is concerned it is nigh on impossible
to support dynamic creation of
On Thu, 15 Dec 2005, Lachlan Hunt wrote:
form action=redirect.cgi
menu type=commands
menu label=Select site...
select name=goto
onchange=if (this.options[this.selectedIndex].value)
location =
On Dec 19, 2005, at 2:40 PM, Ian Hickson wrote:
Untrusted content is unclear. It implies the existence of
something that isn't untrusted content, i.e. trusted content.
Where is that defined? I do not believe it is defined anywhere, in
which case specifying its behavior seems non-useful.
I
On Thu, 15 Dec 2005, Lachlan Hunt wrote:
I think the fact that a supports rel= gives us a way to drop
link altogether, actually.
What about link rel=stylesheet? I don't expect a rel=stylesheet
to perform the same function.
I didn't mean altogether, my bad. There are various rel=
On Thu, 15 Dec 2005, Alexey Feldgendler wrote:
On Thu, 15 Dec 2005 04:31:05 +0600, Lachlan Hunt [EMAIL PROTECTED]
wrote:
I'm guessing nesting a select within another select will break current
UAs.
Sub-menus like that will be handled with nested optgroup elements.
Are current
On Thu, 15 Dec 2005, Nate H. wrote:
Many people have tried this kind of thing in the past, with little
success. As far as I can tell, there is little interest from Web
authors in describing their site map (which is more a graph than a
tree, and which is getting all the more
