Re: [whatwg] javascript API for element

On Jun 2, 2007, at 5:40 AM, Silvia Pfeiffer wrote: Hi all, the Annodex Association and Xiph Foundation are in the process of implementing a small-footprint library and firefox plugin called OggPlay that provides native Ogg Theora support. There's a javascript API in the process of being speci

[whatwg] Setting innerHTML to null or undefined

For .innerHTML = null Opera and Internet Explorer act as if the literal string "null" was used. Firefox acts as if "" was used. For .innerHTML = undefined Opera, Firefox and Internet Explorer act as if the literal string "undefined" was used. -- Anne van Kesteren

[whatwg] typos in HTMLElement IDL

* tabindex -> tabIndex * contenteditable -> contentEditable * The irrelevant DOM attribute currently doesn't link because there's no around its definition. -- Anne van Kesteren

Re: [whatwg] ISO-8859-* and the C1 control range

On Jun 2, 2007, at 15:58, Øistein E. Andersen wrote: 2) Safari and IE5.5/Mac treat C1 characters from all (supported) ISO-8859-* characters as Windows-1252; Interesting. That's true for the latest release version of Safari. I tested with a nightly for which that's no longer true and the

Re: [whatwg] ISO-8859-* and the C1 control range

On 29 May 2007, at 11:13AM, Henri Sivonen wrote: > Surely there are other ISO-8859 family encodings besides ISO-8859-1 > that require decoding using the corresponding Windows-* family decoder? For the following reasons, this is not entirely obvious: 1) Several of the windows-* encodings are more

[whatwg] javascript API for element

Hi all, the Annodex Association and Xiph Foundation are in the process of implementing a small-footprint library and firefox plugin called OggPlay that provides native Ogg Theora support. There's a javascript API in the process of being specified - and I think it would be valuable for others to

Re: [whatwg] No-DOM HTML

Le 2007-06-02 à 4:39, Anne van Kesteren a écrit : On Wed, 30 May 2007 15:22:39 +0200, Michel Fortin <[EMAIL PROTECTED]> wrote: 3) Emit events until you reach a point where it may be possible that some events should be reordered, in which case you build a local DOM-like tree and wait until y

Re: [whatwg] No-DOM HTML

On Jun 2, 2007, at 11:39, Anne van Kesteren wrote: Sending mutation events is probably the only way to go. Of course, real-world apps that want to use a streaming API probably want a drop-in SAX replacement and don't want to maintain a non- parser-exposed private DOM that could respond to t

Re: [whatwg] Issues concerning the element and xml:base

On Thu, 31 May 2007 01:44:57 +0200, Jonas Sicking <[EMAIL PROTECTED]> wrote: I would be hesitant to drop support for multiple s in firefox actually. Implementation wise it was very easy to implement, and it is known that many pages out there break, though the percentage is small, there are a

Re: [whatwg] HTMLDocument.title and SVGDocument

On Jun 2, 2007, at 1:31 AM, Anne van Kesteren wrote: On Sat, 02 Jun 2007 01:06:12 +0200, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: I like the "check the root element" option. That way, one could use the exact same Document object implementation for SVG and XHTML, while remaining compati

Re: [whatwg] No-DOM HTML

On Wed, 30 May 2007 15:22:39 +0200, Michel Fortin <[EMAIL PROTECTED]> wrote: 3) Emit events until you reach a point where it may be possible that some events should be reordered, in which case you build a local DOM- like tree and wait until you can emit all pending events with a certainty th

Re: [whatwg] HTMLDocument.title and SVGDocument

On Sat, 02 Jun 2007 01:06:12 +0200, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: I like the "check the root element" option. That way, one could use the exact same Document object implementation for SVG and XHTML, while remaining compatible with expected behavior for existing content in both

Re: [whatwg] HTMLMediaElement.volume

On Jun 1, 2007, at 6:03 PM, Ian Hickson wrote: On Fri, 23 Mar 2007, Anne van Kesteren wrote: Wouldn't it be better if no INDEX_SIZE_ERR was raised but instead the previous value was retained? For consistency with CanvasRenderingContext2D.globalAlpha for instance. It's not really important, bu