The specification does not really say whether it is cancelable or not
explicitly. Taking into account the text surrounding the event it is probably
not cancelable, but I guess that should be noted.
Also s/fired an/fired on/
Cheers,
Anne
--
Anne van Kesteren
http://annevankesteren.nl/
Matthew Raymond wrote:
Lachlan Hunt wrote:
No, command in the current spec represents an abstract form control for
sharing features among several real form controls.
The command element is most certainly not a form control, since it
can't be submitted
I know that, I said *abstract* form
2.14. Extensions to the textarea element
# 'white-space' property values based on the wrap element
# for textarea elements
There is no such thing as a wrap element.
Cheers,
Anne
--
Anne van Kesteren
http://annevankesteren.nl/
On Thu, 1 Dec 2005, Anne van Kesteren wrote:
The specification does not really say whether it is cancelable or not
explicitly. Taking into account the text surrounding the event it is
probably not cancelable, but I guess that should be noted.
Also s/fired an/fired on/
Fixed.
--
Ian
On Thu, 1 Dec 2005, Anne van Kesteren wrote:
It only addresses form controls nested in a fieldset. However, setting
optgroup to disabled should cause descendents of that, either optgroup
or option, to become disabled as well.
Fixed.
--
Ian Hickson U+1047E
Quoting Ian Hickson [EMAIL PROTECTED]:
It only addresses form controls nested in a fieldset. However, setting
optgroup to disabled should cause descendents of that, either optgroup
or option, to become disabled as well.
Fixed.
This also applies to :enabled. Sorry for not bringing that up
On Thu, 1 Dec 2005, Anne van Kesteren wrote:
Quoting Ian Hickson [EMAIL PROTECTED]:
It only addresses form controls nested in a fieldset. However, setting
optgroup to disabled should cause descendents of that, either optgroup
or option, to become disabled as well.
Fixed.
This
Lachlan Hunt wrote:
Matthew Raymond wrote:
Lachlan Hunt wrote:
AIUI, the difference between them can be illustrated as follows:
menu
cmd !-- Menu command item --
button/!-- [Label] for command menu --
select/!-- The menu items --
/cmd
li !-- Menu
Section 4.2 states: Change and input events must never be triggered by scripted
changes to the control value.
Section 2.13 states: Whenever the value attribute changes (whether directly or
because the DOM under the element was mutated), a change event is fired on the
output element.
That
On Fri, 2 Dec 2005, Anne van Kesteren wrote:
Section 4.2 states: Change and input events must never be triggered by
scripted
changes to the control value.
Section 2.13 states: Whenever the value attribute changes (whether directly
or
because the DOM under the element was mutated), a
On Thu, 1 Dec 2005, Ian Hickson wrote:
On Fri, 2 Dec 2005, Anne van Kesteren wrote:
Section 4.2 states: Change and input events must never be triggered by
scripted
changes to the control value.
Section 2.13 states: Whenever the value attribute changes (whether
directly or
Quoting Ian Hickson [EMAIL PROTECTED]:
output is not a control.
Section 1.10 states: The term form control refers to input, output, select,
textarea and button elements. It does not include form, label, datalist,
option, optgroup, or fieldset elements.
The first line of the description of
12 matches
Mail list logo
