Re: [whatwg] rel/rev for form ?

purposes. The use of 'class' for presentation is wrong anyway (and hopefully obsoleted in HTML 5). And yes, although it is named incorrectly, the attribute can take multiple, space-separated, values. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [WA1] INS/DEL and omitted /p tags

element so that it can correctly close all open inline elements when it sees a tag that starts a block level element? Mostly, yes. Most browsers have very specific behavior depending on the element. (Which not necessarily makes the DOM more conformant.) -- Anne van Kesteren http

[whatwg] [wf2] autofocus

Regarding http://whatwg.org/specs/web-forms/current-work/#the-autofocus. What happens when a form control is already there but its autofocus DOM attribute is set to true? Same as calling the .focus() method on the form control or same as nothing happens? Cheers, Anne -- Anne van Kesteren

Re: [whatwg] Menus, fallback, and backwards compatibility: ideas wanted

mechanism for form controls this idea is never going to make it. From that perspective using html:menu with html:li etc. is much better I guess. -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] [wf2] some comments on DOM interface section

van Kesteren http://annevankesteren.nl/

Re: [whatwg] [wf2] some comments on DOM interface section

]. Cheers, Anne -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] [wf2] DOMControlValueChanged cancelable?

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/

[whatwg] [wf2] editorial thing regarding wrap attribute

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/

Re: [whatwg] [wf2] :disabled does not address option inside disabled optgroup

earlier. -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] [wf2] change event

. That contradicts each other, not? -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [wf2] change event

of that element (2.13) says basically the same. Cheers, Anne -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Menus, fallback, and backwards compatibility: ideas wanted

optionfoo optionbar /cmd would be the same as: cmd select optionfoo optionbar /select button/ /cmd Since the first would only be supported by new UAs with no good fallback, the button would be completely unnecessary. Yeah, I meant that. And I like it now I see it :-) -- Anne van

Re: [whatwg] Menus, fallback, and backwards compatibility: ideas wanted

about that. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Menus, fallback, and backwards compatibility: ideas wanted

getElementsByTagNameNS method with the parameters http://www.w3.org/1999/xhtml; and option from the cmd element and give that element semantic meaning. (Which is essentially what is done today so it is quite backwards compatible.) -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] [wf2] form content/DOM attribute

...) Cheers, Anne -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [wf2] change event is not cancelable

. (That is in fact implemented.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [WF3] input type=selector

this. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [WF3] input type=selector

an attribute to them? Maybe that is a better solution. It would certainly degrade better than a new input type. Yeah, a global label or for attribute which can be applied to some ancestor, like html:tr. (Or only to the template (which mostly is the html:tr).) -- Anne van Kesteren http

[whatwg] [wf2] list and datalist

. The selected attribute and the form, selected,. I suggest to drop the second selected or is this one of those cases were you want to be extra explicit without it actually being necessary? Cheers, Anne -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] Attaching style sheets (was: Re: Menus, fallback, and backwards compatibility: ideas wanted)

simple testing showed that at least Firefox, Opera and Internet Explorer do not. KHTML browsers perhaps? -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] The link element and display: meta

. Something like making a link no longer a link trhough some property. Now there has been some need for such a language, but it is not presentational. It is more some semantic language to describe what kind of element it is, which attributes serve special functions, et cetera. -- Anne van Kesteren

Re: [whatwg] BIG Element

where you want to use an element both for mathematics and shouting... -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] CENTER, MENU, DIR, NL

with XHTML. Yet there has been no recommendation or standard (whatever you prefer) that contains such an element so the argument is bogus. menu on the other hand... -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] CENTER, MENU, DIR, NL

://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/ -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Definition of alt= attribute

it and have the user agent derive some information from the image URL. This will better reflect the real world situation: many authors actually omit alt (which results in an invalid page) when they actually should have written it. HTML5 is not about making the world valid. -- Anne van

[whatwg] comment parsing

someone explaining to me what I did wrong when reading the specification. -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] [wf2] required attribute and pseudo-classes

In http://whatwg.org/specs/web-forms/current-work/#relation I think the text on :required and :optional should be clarified so that it is clear that these pseudo-classes only apply to elements to which the required attribute applies. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] The link element and display: meta

is in). However, I'm still not sure what problem is being solved here. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Comment Syntax and Parsing

of chracters are allowed there (including - for instance). -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] Web Forms 2 Test Suite

need to be covered as well. Feedback, new tests and other things are appreciated. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Web Forms 2 Test Suite

see the beginnings of a test suite. Thanks. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Comment Syntax and Parsing

handling for the moment. So you could use Opera 8.5 if you do not want SGML comment handling. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Tag Soup: Blocks-in-inlines

parsers did funny things on error recovery. -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] [wf2] addition and attributes of type ID

. (Multiple IDs for the same element is less of a problem imho.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Adoption Agency Algorithm

to be reparsed when the user disables scripting or frames. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [wf2] changing the size DOM attribute of select

Quoting Jim Ley [EMAIL PROTECTED]: I simply don't see the value in standardising the error behaviour here. Just setting it to 1, which is an appropriate value, does not give interoperable behavior either. (The selected option is not the same.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [wf2] changing the size DOM attribute of select

Quoting Jim Ley [EMAIL PROTECTED]: On 2/11/06, Anne van Kesteren [EMAIL PROTECTED] wrote: Quoting Jim Ley [EMAIL PROTECTED]: I simply don't see the value in standardising the error behaviour here. Just setting it to 1, which is an appropriate value, does not give interoperable behavior

Re: [whatwg] HTML5 Parsing spec first draft ready

be good if that was specified as well. And if all the browsers implement the same parsing model, then HTML interoperability on the Web will take a huge leap forward. T'would be save everyone a lot of time. Would be a good thing indeed. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] False orthogonal nature :read-only and :disabled in WF2

this implemented correctly... -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] diffed versions (CVS)

February as opposed to the one from 22 February 2006... Best thing would be if there was some list to which CVS diff-logs would be e-mailed or so. Would make it a lot easier to track changes. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Targetting different anchors after submitting the form

to multiple forms? One submits to one place, the other submits to another place. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Targetting different anchors after submitting the form

version to assist with making test-cases of the spec. Feel free to download a weekly build of Opera 9.0: http://my.opera.com/desktopteam/ ... and test how it works. -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] [html5] createPattern() with image being of the wrong type

van Kesteren http://annevankesteren.nl/

[whatwg] limitations of del and ins (was: Re: [WA1] INS/DEL and omitted /p tags)

neither table nor ul can't contain ins... Can this be helped somehow? That could be solved using an attribute I guess, similar to edit in some XHTML 2.0 proposal. Inserting and removing table cells on the other hand... -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] The problem of duplicate ID as a security issue

Quoting Alexey Feldgendler [EMAIL PROTECTED]: I'm not sure that the answers to these questions are the same for all modern browsers. You can speculate forever or just find out. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] JSONRequest

anyway I'd rather have that the WHATWG, W3C came up with a more broader solution to the cross domain security problem. (AFAIK some work is going on at the W3C in that area.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Select conformance

Quoting Henri Sivonen [EMAIL PROTECTED]: Whoa! It's even interoperably supported in Firefox and Opera. http://hsivonen.iki.fi/test/wa10/adhoc/option-selected-disabled.html It would be interesting to see what happens if it wasn't the first option element child. -- Anne van Kesteren http

Re: [whatwg] [wf2] Omission of legend

a useful purpose of grouping on its own. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] id and xml:id

that Opera recently changed its behavior to match the others with id=' c '): Bah. I hope we can revert that... Do you have a similar test for xml:id? Opera does (did?) passes the following for example: http://annevankesteren.nl/test/xml/xml-id/008.xml Cheers, Anne -- Anne van Kesteren http

Re: [whatwg] id and xml:id

template also allows for characters that are compatible with XML ID. Of course, this is only for valid documents... All things should still be defined in a way that they take into account invalid, yet well-formed, documents as well. (And HTML documents...) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] image captions

number... -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [wf2] repeat-min and max

to allow non- negative integers so that repetition could be dynamically forbidden or allowed by changing the attribute value? ... -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [wf2] repeat-min and max

. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [wf2] repeat-min and max

/repetition/attributes/repeat-max/004.htm ... -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] The embed element

. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] proposed canvas 2d API additions

security considerations as for toDataURL() should apply. I suggest adding that somewhere. One other problem I had with it was that the colors are restricted to 8 bit. That may potentially lead to data loss but I guess it's not a major concern yet. -- Anne van Kesteren http

Re: [whatwg] proposed canvas 2d API additions

saying it's a 1x1 pixel canvas just that within that 1x1 pixel there could be different subpixels with different colors you could try to get using floating points instead of integers. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] fullscreen event?

and the mediaList contains 'print'. If you go to projection mode it contains 'print' etc. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] toDataURL() and unsupported formats

checks to see if that succeeded is more error prone than just doing `if(c.toDataURL(test))` or a try/catch(e) statement. -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] Audio(): loop() with 0 or negative value as argument

, unless someone has a better suggestion. (Note that loop() without arguments can be used for infinite repetition.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Mathematics on HTML5

=site%3Aopera.com+mathml ... didn't work out. Then again, I'm also unaware of an Opera browser developers site :-) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Mathematics in HTML5

to specify what happens when people don't do it properly. Besides designing the actual language, that's probably the hardest bit. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Mathematics in HTML5

Quoting Henri Sivonen [EMAIL PROTECTED]: You do need to know how to write it though... Need to know how to write a normative DTD??? No, how to write the math markup. Probably based on some English prose. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Mathematics in HTML5

actually write down a submark followed by marker followed by matrix? I guess these issues are mostly relevant for parsing (styling is pretty clear once that's defined), but it should be clear what the semantics are in such cases as well. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Mathematics in HTML5

Ruby is already supported by Internet Explorer in HTML (I think the XHTML module was based on that implementation) and it makes sense to have it for certain foreign (to me at least) use cases. [2]: http://www.w3.org/TR/ruby/ [3]: http://www.w3.org/TR/css3-ruby/ -- Anne van Kesteren http

Re: [whatwg] Simple numbers

, it probably does for the top50 use cases or so. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] input type=text accept=

not commonly used. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Mathematics in HTML5

for MathML (at this time). And all on non-normative forums or non-normative articles. (Opera has no official position regarding MathML, fwiw.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] input type=text accept=

about aiding users. As far as I understand that's what the inline spell checking is for. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] input type=text accept=

is not strictly needed, but I'm unsure if it's really just presentation... -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] [html5] HTMLMapElement.images

definition. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [html5] HTMLMapElement.images

Quoting Ian Hickson [EMAIL PROTECTED]: On 6/13/06, Anne van Kesteren [EMAIL PROTECTED] wrote: Before I forget about this hereby a proposal to give the HTMLMapElement interface a new (readonly) member called `images` or equivalent representing an HTMLCollection consisting of HTMLImageElement

Re: [whatwg] [html5] HTMLMapElement.images

Quoting Shadow2531 [EMAIL PROTECTED]: On 6/13/06, Anne van Kesteren [EMAIL PROTECTED] wrote: Before I forget about this hereby a proposal to give the HTMLMapElement interface a new (readonly) member called `images` or equivalent representing an HTMLCollection consisting of HTMLImageElement

Re: [whatwg] Mathematics in HTML5

Quoting [EMAIL PROTECTED]: Since MathML does not fit into the WHATWG philosophy, I would aknowledge information about your own solution to the problem of mathematical markup on the web. Oh please, cut the crap. Did you miss the message from Ian saying how it could integrate? -- Anne van

Re: [whatwg] Mathematics in HTML5

is the difference between writing style sheet for microformat and writing style sheet for XML based markup? There is no difference. Perhaps you should read up on Microformats. It's not really about writing a style sheet for a bunch of classes associated with elements. -- Anne van Kesteren http

Re: [whatwg] Mathematics in HTML5

? :-) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Spellchecking proposal #2

but enabled for its Subject line? By having something like type=email for multiple e-mail addresses? (Or reusing type=email in some way would work as well I suppose.) -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Spellchecking proposal #2

? As in, what would be the impact on the proposal? -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Spellchecking proposal #2

in such cases just to turn it off/on. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] [HTML5] Named start values for lists?

Quoting Lachlan Hunt [EMAIL PROTECTED]: However, there are several issues that would need to be addressed: [List of good points] * How does it interact with CSS counters. -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] contenteditable= needs fixing

-- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] contenteditable= needs fixing

on this? Can you give me a good reason to deviate from what Internet Explorer does? -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] contenteditable= needs fixing

would work. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] Broken references links to IETF website

to work. -- Anne van Kesteren http://annevankesteren.nl/

Re: [whatwg] XMLHttpRequest: getAllResponseHeaders

PROTECTED] -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [whatwg] Dynamic content accessibility in HTML today

it accessible. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [whatwg] [WF2] Label with empty for attribute

with a control in it that the label is not associated with? I don't know. What's the point again of having a form control inside a form, but not being associated with anything (including the form)? -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

[whatwg] XHTML and document.write()

element and try again... Ouch! Not sure if nested html:script element would make things harder here... -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

[whatwg] Some comments on server-sent events

happens to command lines. * The ctrlKey field would be ignored[...] should probably say keyIdentifier as that's what's used in the example. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [whatwg] input type=country?

to by default select the user's country when they encounter such a list in a page's form. Opera supports RFC 2706 http://ietf.org/rfc/rfc2706 for form controls which basically allows page authors to indicate what certain form controls are for allowing them to be pre-filled. -- Anne van

Re: [whatwg] href on any element

these days. Another thing that some author seem to want is to make an entire block a link, including its header and footer. Currently such things are solved with markup similar to: a href= span class=header/span span class=text/span /a ... -- Anne van Kesteren http

Re: [whatwg] proposed canvas 2d API additions

. As you pointed out some to me, not for percentage rgb color values. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

[whatwg] return lowercase hex values for fillStyle and strokeStyle

Instead of returning an uppercase six digit hex value I suggest returning a lowercase value for compatibility with what UAs (including IE) currently do for CSS already and what Mozilla already does for canvas. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [whatwg] Lists, ins/del, and a

markup. (As for my myself, I only partially agree with that sentiment.) -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [whatwg] Lists, ins/del, and a

users have with them is their visual appearance). [1] http://www.w3.org/TR/xhtml2/mod-edit.html -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [whatwg] href on any element

obviously. Seems like a good reason to put it in HTML5! -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [whatwg] Hacking away on forms ... (fwd)

or not such an element is treated as empty varies from browser to browser. Converting the node name to uppercase also seems like the right thing to do for text/html documents although HTML5 might change bits of that... -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [whatwg] Hacking away on forms ... (fwd)

On Sun, 10 Sep 2006 12:41:51 +0200, Francisco Monteiro [EMAIL PROTECTED] wrote: What does tags have to do with the DOM? Exactly, is this thread becoming a Opera marketing ploy? ? -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

[whatwg] Editorial: parsing section

When you have phrases like 'Change the insertion mode to in select.' it would be nice if in select was a pointer to the relevant section. Currently insertion mode is a pointer and that's hardly useful. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

[whatwg] Fwd: Re: [xhtml-role] Extensibility of XHTML 1 and XHTML 1.1 (PR#9627)

namespace as XHTML1, and there will not be two modules. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

  1   2   3   4   5   6   7   8   9   10   >