[whatwg] Remove addCueRange/removeCueRanges

2009-08-13 Thread Philip Jägenstedt
Hi, We would like to request that addCueRange/removeCueRanges be dropped from the spec before going into Last Call. We are not satisfied with it and want to see it replaced with a solution that includes (scriptless) timed text (a.k.a captions/subtitles). I don't think that this will be

Re: [whatwg] Remove addCueRange/removeCueRanges

2009-08-13 Thread Silvia Pfeiffer
I agree with this assessment. Please note that at this stage this is my personal opinion, since I haven't discussed it with other Mozilla developers yet. Regards, Silvia. On Thu, Aug 13, 2009 at 6:31 PM, Philip Jägenstedtphil...@opera.com wrote: Hi, We would like to request that

Re: [whatwg] the cite element

2009-08-13 Thread Smylers
Erik Vorhes writes: So the definition of cite in HTML5 should currently be title of work or something that could be construed as a title where one doesn't exist in the explicit sense of 'title.' But not people's names, even if they're the citation, because using cite for citations is silly.

Re: [whatwg] Make quoted attributes a conformance criteria

2009-08-13 Thread Ian Hickson
On Tue, 4 Aug 2009, Henri Sivonen wrote: On Aug 3, 2009, at 05:45, Ian Hickson wrote: Instead of preventing anyone from not using quote marks, I would instead recommend asking your validator vendor to offer you an option to require quote marks and warn you when you have forgotten them.

Re: [whatwg] Installed Apps

2009-08-13 Thread Ian Hickson
On Tue, 4 Aug 2009, Drew Wilson wrote: On Mon, Aug 3, 2009 at 8:58 PM, Ian Hickson i...@hixie.ch wrote: It seems like a direct solution to these would be to have a way for Web pages to expose a service that clients could subscribe to, which could send up database updates and

Re: [whatwg] Fullscreenable and Mouselockable attributes

2009-08-13 Thread Ian Hickson
On Tue, 4 Aug 2009, Henry Bridge wrote: With the video tag and web games gaining traction, it seems like there should be a way for apps to provide fullscreen and better control schemes to users. Of course, spoofing and clickjacking are major concerns, but I liked Alpha Omega's suggestion

Re: [whatwg] Installed Apps

2009-08-13 Thread Mike Wilson
Ian Hickson wrote: On Tue, 4 Aug 2009, Drew Wilson wrote: Sure, although I'd say that persistent storage is addressed by the Web Storage and Web Database features. Shared state is also addressed, but that's not the primary goal. If I have a tree of objects that I'd like to share

Re: [whatwg] the cite element

2009-08-13 Thread Erik Vorhes
On Thu, Aug 13, 2009 at 4:59 AM, Smylerssmyl...@stripey.com wrote: As Ian has pointed out, the above is technically non-conforming with what the HTML 4 spec claims.  But it's how I've been using cite for years, since it makes sense and has a use. I defy you to show me in the HTML 4.01

Re: [whatwg] Remove addCueRange/removeCueRanges

2009-08-13 Thread Dr. Markus Walther
Hi, please note that with cue ranges removed, the last HTML 5 method to perform audio subinterval selection is gone. AFAIK, when dropping support for 'start' and 'end' attributes it was noted on this list that cue ranges would provide a replacement to dynamically select, say, a 3-second range

Re: [whatwg] Remove addCueRange/removeCueRanges

2009-08-13 Thread Philip Jägenstedt
On Thu, 13 Aug 2009 14:34:55 +0200, Dr. Markus Walther walt...@svox.com wrote: Hi, please note that with cue ranges removed, the last HTML 5 method to perform audio subinterval selection is gone. AFAIK, when dropping support for 'start' and 'end' attributes it was noted on this list that

Re: [whatwg] the cite element

2009-08-13 Thread Remco
On Thu, Aug 13, 2009 at 2:26 PM, Erik Vorhese...@textivism.com wrote: On Thu, Aug 13, 2009 at 4:59 AM, Smylerssmyl...@stripey.com wrote: As Ian has pointed out, the above is technically non-conforming with what the HTML 4 spec claims.  But it's how I've been using cite for years, since it

Re: [whatwg] the cite element

2009-08-13 Thread Erik Vorhes
On Thu, Aug 13, 2009 at 4:59 AM, Smylerssmyl...@stripey.com wrote: For words that you wish to have no distinct presentation from the surrounding text -- words that readers don't need calling out to them as being in any way 'special' -- simply don't mark them up. Interesting point. Should the

Re: [whatwg] the cite element

2009-08-13 Thread Smylers
Erik Vorhes writes: On Thu, Aug 13, 2009 at 4:59 AM, Smylerssmyl...@stripey.com wrote: As Ian has pointed out, the above is technically non-conforming with what the HTML 4 spec claims.  But it's how I've been using cite for years, since it makes sense and has a use. I defy you to show

Re: [whatwg] Spec comments, sections 3.1-4.7

2009-08-13 Thread Smylers
Tab Atkins Jr. writes: On Wed, Aug 12, 2009 at 7:43 PM, Aryeh Gregorsimetrical+...@gmail.com wrote: I haven't noticed many progress bars on the web You see them a lot more in the indeterminate form, as a 'spinner' image or the like. ... I suspect, though, that there are a lot of

Re: [whatwg] Issues with Web Sockets API

2009-08-13 Thread Alexey Proskuryakov
13.08.2009, в 4:42, Ian Hickson написал(а): A note explaining that the close event will be dispatched at server's discretion (or on subsequent connection timeout), potentially long time after close() is called, would likely make the intention clearer. It won't be long after the close().

Re: [whatwg] the cite element

2009-08-13 Thread Smylers
Erik Vorhes writes: On Thu, Aug 13, 2009 at 4:59 AM, Smylerssmyl...@stripey.com wrote: For words that you wish to have no distinct presentation from the surrounding text -- words that readers don't need calling out to them as being in any way 'special' -- simply don't mark them up.

[whatwg] size limits on web databases

2009-08-13 Thread Rob Kroeger
From http://dev.w3.org/html5/webdatabase/: The openDatabase() method on the Window and WorkerUtils interfaces must return a newly constructed Database object that represents the database requested. The spec does not make it clear what the UA on an extremely resource-constrained device (e.g. a

Re: [whatwg] Remove addCueRange/removeCueRanges

2009-08-13 Thread David Singer
At 10:31 +0200 13/08/09, Philip Jägenstedt wrote: Hi, We would like to request that addCueRange/removeCueRanges be dropped from the spec before going into Last Call. We are not satisfied with it and want to see it replaced with a solution that includes (scriptless) timed text (a.k.a

Re: [whatwg] Installed Apps

2009-08-13 Thread Jeremy Orlow
On Thu, Aug 13, 2009 at 4:07 AM, Ian Hickson i...@hixie.ch wrote: Additionally, any server-side-feed-based solution has the implication that it won't work for offline apps. If I am using a web calendar, I want my event notifications regardless of whether I'm online or offline (the event

Re: [whatwg] Spec comments, sections 3.1-4.7

2009-08-13 Thread Anne van Kesteren
On Thu, 13 Aug 2009 19:34:47 +0200, Aryeh Gregor simetrical+...@gmail.com wrote: I'd think that the author in this use-case is not likely to be happy using an unstyle-able progress element and getting some kind of unknown appearance that might clash with their color scheme or such. You seem

Re: [whatwg] Installed Apps

2009-08-13 Thread Drew Wilson
On Thu, Aug 13, 2009 at 4:07 AM, Ian Hickson i...@hixie.ch wrote: Sure, although I'd say that persistent storage is addressed by the Web Storage and Web Database features. Shared state is also addressed, but that's not the primary goal. If I have a tree of objects that I'd like to share

Re: [whatwg] Installed Apps

2009-08-13 Thread Drew Wilson
On Thu, Aug 13, 2009 at 5:13 AM, Mike Wilson mike...@hotmail.com wrote: Maybe I'm mistaken, but I think Drew wanted handling of live objects, where each window gets access to the same concrete objects (possibly protected by private proxy objects) so the graph can be walked without cloning.

Re: [whatwg] Spec comments, sections 3.1-4.7

2009-08-13 Thread Tab Atkins Jr.
On Thu, Aug 13, 2009 at 4:00 PM, Aryeh Gregorsimetrical+...@gmail.com wrote: On Thu, Aug 13, 2009 at 2:11 PM, Anne van Kesterenann...@opera.com wrote: You seem to base most of your argument on that progress will not be stylable. I think the idea is that it will be stylable though. Yes, I

Re: [whatwg] HTML5 History Management

2009-08-13 Thread Ian Hickson
On Wed, 5 Aug 2009, Nathan Hammond wrote: With regards to pushState not triggering a hashchange event, I like it, but I do want to be absolutely sure that all implementers get this right. So, could we clarify this in the spec? Right now I think that the spec could be read where since it

Re: [whatwg] Remove addCueRange/removeCueRanges

2009-08-13 Thread Silvia Pfeiffer
On Fri, Aug 14, 2009 at 3:31 AM, David Singersin...@apple.com wrote: At 10:31  +0200 13/08/09, Philip Jägenstedt wrote: Hi, We would like to request that addCueRange/removeCueRanges be dropped from the spec before going into Last Call. We are not satisfied with it and want to see it

Re: [whatwg] AppCache online whitelist wildcard bypasses restriction on scheme

2009-08-13 Thread Ian Hickson
On Wed, 5 Aug 2009, Jenn Braithwaite (�~C��~E��~K~R) wrote: In the AppCache section of the HTML5 spec, the new wildcard value '*' for the online whitelist section allows one to 'whitelist all' regardless of scheme. However, the spec requires a URL in the online whitelist section to have

Re: [whatwg] Remove addCueRange/removeCueRanges

2009-08-13 Thread Silvia Pfeiffer
Hi Markus, 2009/8/13 Dr. Markus Walther walt...@svox.com: please note that with cue ranges removed, the last HTML 5 method to perform audio subinterval selection is gone. Not quite. You can always use the video.currentTime property in a javascript to directly jump to a time offset in a video.

Re: [whatwg] Section 1.4: Editorial: Avoid passive voice

2009-08-13 Thread Ian Hickson
On Wed, 5 Aug 2009, Elliotte Rusty Harold wrote: Section 1.4 currently states: Work on HTML 5 originally started in late 2003, as a proof of concept to show that it was possible to extend HTML 4's forms to provide many of the features that XForms 1.0 introduced, without requiring browsers

Re: [whatwg] Editorial, section 1.5

2009-08-13 Thread Ian Hickson
On Wed, 5 Aug 2009, Elliotte Rusty Harold wrote: I suggest simply deleting It must be admitted that many aspects of HTML appear at first glance to be nonsensical and inconsistent. I would disagree with nonsensical, and in any case this sentence adds nothing to the text. However if this

Re: [whatwg] Editorial section 1.5.1 serialising

2009-08-13 Thread Ian Hickson
On Wed, 5 Aug 2009, Elliotte Rusty Harold wrote: completely serialising the execution of all scripts. -- serializing (i.e. use the American spelling used throughout the rest of the document.) Thanks. Fixed. -- Ian Hickson U+1047E)\._.,--,'``.fL

Re: [whatwg] object behavior

2009-08-13 Thread Ian Hickson
On Thu, 6 Aug 2009, Andrew Oakley wrote: The rules in the HTML5 spec for which plugin to load for an object do not seem to be followed by any browser, and in some cases are different to behavior that is common to Opera, Webkit and Gecko (I haven't tested with IE due to its lack of nsplugin

Re: [whatwg] Section 1.7 abstract language

2009-08-13 Thread Ian Hickson
On Thu, 6 Aug 2009, Elliotte Rusty Harold wrote: This specification defines an abstract language for describing documents and applications, and some APIs for interacting with in-memory representations of resources that use this language. The phrase abstract language concerns me. It's not

Re: [whatwg] HTML5: compatible with all legacy Web browsers

2009-08-13 Thread Ian Hickson
On Thu, 6 Aug 2009, Elliotte Rusty Harold wrote: Section 1.7: The first such concrete syntax is HTML5. This is the format recommended for most authors. It is compatible with all legacy Web browsers. I challenge the claim that HTML5 is compatible with *all* legacy Web browsers. I can

Re: [whatwg] Section 1.7 abstract language

2009-08-13 Thread Kevin Benson
On Thu, Aug 13, 2009 at 10:10 PM, Ian Hicksoni...@hixie.ch wrote: On Thu, 6 Aug 2009, Elliotte Rusty Harold wrote: This specification defines an abstract language for describing documents and applications, and some APIs for interacting with in-memory representations of resources that use this

Re: [whatwg] Section 1.7 editorial

2009-08-13 Thread Ian Hickson
On Thu, 6 Aug 2009, Elliotte Rusty Harold wrote: The first such concrete syntax is HTML5. This is the format recommended for most authors. It is compatible with all legacy Web browsers. If a document is transmitted with the MIME type text/html, then it will be processed as an HTML5

Re: [whatwg] Editorial: 1.9 DOCTYPE HTML

2009-08-13 Thread Ian Hickson
On Thu, 6 Aug 2009, Elliotte Rusty Harold wrote: Section 1.9 uses this DOCTYPE twice: !DOCTYPE HTML Unless the intention is to demonstrate case-insensisitivity, which doesn't seem to be the case since that's not otherwise mentioned in this section, I think this should be: !DOCTYPE

Re: [whatwg] 2.1.1 (they are in the per-element partition)

2009-08-13 Thread Ian Hickson
On Thu, 6 Aug 2009, Elliotte Rusty Harold wrote: I suggest deleting the parenthetical remark (they are in the per-element partition). I'm not sure what this term means. I've never encountered either partition or per-element partition in an XML namespace context before. It was a term from

Re: [whatwg] HTML 5 Script Tag

2009-08-13 Thread Ian Hickson
On Thu, 6 Aug 2009, Cready, James wrote: Is there any good reason why a script tag with the src attribute specified can�t be self-closing? No elements in text/html can be self-closing. In the case of script in particular, allowing it would be a compatibility problem at best and a security

Re: [whatwg] 2.2 editorial

2009-08-13 Thread Ian Hickson
On Thu, 6 Aug 2009, Elliotte Rusty Harold wrote: Applications and tools that process HTML and XHTML documents for reasons other than to either render the documents or check them for conformance should act in accordance to the semantics of the documents that they process. 2.2 editorial

Re: [whatwg] 2.2 Performant

2009-08-13 Thread Ian Hickson
On Thu, 6 Aug 2009, Elliotte Rusty Harold wrote: In particular, the algorithms defined in this specification are intended to be easy to follow, and not intended to be performant. Yech. The recently coined word performant just grates on my ears; and I'm not the only one as a Google search

[whatwg] Section 4.10.4.1.4 and Section 9.1.2.6

2009-08-13 Thread Kevin Benson
In section 4.10.4.1.4 URL state, the text reads: The input element represents a control for editing a single absolute URL given in the element's value. If the is mutable, the user agent should allow the user to change the URL represented by its value. I believe that last line should read: If

Re: [whatwg] Possible typo in application cache section

2009-08-13 Thread Ian Hickson
On Thu, 6 Aug 2009, Darin Adler wrote: 6.9.4, paragraph 7 says, �applications caches never include fragment identifiers� and I think this should just be �application caches�. Fixed, thanks. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/

Re: [whatwg] Section 4.10.4.1.4 and Section 9.1.2.6

2009-08-13 Thread Ian Hickson
On Fri, 14 Aug 2009, Kevin Benson wrote: In section 4.10.4.1.4 URL state, the text reads: The input element represents a control for editing a single absolute URL given in the element's value. If the is mutable, the user agent should allow the user to change the URL represented by its