Re: [whatwg] need a way to set output format from StreamRecorder

2011-02-15 Thread Kevin Marks
On Mon, Feb 14, 2011 at 11:52 PM, Nils Dagsson Moskopp n...@dieweltistgarnichtso.net wrote: Kevin Marks kevinma...@gmail.com schrieb am Mon, 14 Feb 2011 22:33:13 -0800: On Mon, Feb 14, 2011 at 2:39 PM, Ian Hickson i...@hixie.ch wrote: […] I haven't added anything here yet, mostly

Re: [whatwg] [html5] @formaction, @formenctype, @formmethod, @formnovalidate, @formtarget

2011-02-15 Thread Anne van Kesteren
On Tue, 15 Feb 2011 03:48:10 +0100, Jens O. Meiert j...@meiert.com wrote: It was that way before, but many pages were already using those attributes and expected the browser to not do anything with them. I understand that good judgment will have been applied. Hence out of mere curiosity, do

Re: [whatwg] need a way to set output format from StreamRecorder

2011-02-15 Thread Nils Dagsson Moskopp
Kevin Marks kevinma...@gmail.com schrieb am Tue, 15 Feb 2011 00:23:00 -0800: To be fair to Safari it supports far more audio formats than other browsers, Yes, but it supports *other* formats than other browsers. That's the crux of the issue. To creators of multimedia files and web developers

Re: [whatwg] Google Feedback on the HTML5 media a11y specifications

2011-02-15 Thread Philip Jägenstedt
On Tue, 15 Feb 2011 04:28:36 +0100, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Hi Philip, On Tue, Feb 15, 2011 at 3:27 AM, Philip Jägenstedt phil...@opera.com wrote: On Wed, 09 Feb 2011 03:57:37 +0100, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: A. Feedback on the WebVTT

Re: [whatwg] Why are media event handlers defined on HTMLElement instead of HTMLMediaElement

2011-02-15 Thread Philip Jägenstedt
On Mon, 14 Feb 2011 22:54:54 +0100, David Flanagan da...@davidflanagan.com wrote: The draft specification defines 20+ medial event handler IDL attributes on HTMLElement. These events are non-bubbling and are always targeted at audio and video tags, so I wonder if they wouldn't be better

Re: [whatwg] Google Feedback on the HTML5 media a11y specifications

2011-02-15 Thread Silvia Pfeiffer
On Tue, Feb 15, 2011 at 9:09 PM, Philip Jägenstedt phil...@opera.com wrote: On Tue, 15 Feb 2011 04:28:36 +0100, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Hi Philip, On Tue, Feb 15, 2011 at 3:27 AM, Philip Jägenstedt phil...@opera.com wrote: On Wed, 09 Feb 2011 03:57:37 +0100,

Re: [whatwg] Google Feedback on the HTML5 media a11y specifications

2011-02-15 Thread Glenn Maynard
Following up on a use case discussed earlier, an alternative approach for adding mid-cue comments, such as editor notes, would be to wrap them in a class: c.ccomment/c. It's a little awkward, but has the advantage of allowing the comments to be displayed within the displayed captions just by

Re: [whatwg] Google Feedback on the HTML5 media a11y specifications

2011-02-15 Thread Philip Jägenstedt
On Tue, 15 Feb 2011 12:57:02 +0100, Glenn Maynard gl...@zewt.org wrote: Following up on a use case discussed earlier, an alternative approach for adding mid-cue comments, such as editor notes, would be to wrap them in a class: c.ccomment/c. It's a little awkward, but has the advantage of

[whatwg] Device element and the lifetime of the stream objects

2011-02-15 Thread Leandro Graciá Gil
Hi, Looking at the current state of the specification I see there is no mention about the expected lifetime of the stream objects, or to say it in another way, the period in which a page can access the selected device data. We would like to propose that the user can explicitly invalidate an

Re: [whatwg] Proposal for IsSearchProviderInstalled / AddSearchProvider

2011-02-15 Thread Bjartur Thorlacius
On 2/14/11, David Levin le...@chromium.org wrote: Problem Although the default search provider may have a significant impact on a user’s web experience, it isn’t easy for users to set this. Ideally, a search engine should be able to offer the user the ability to easily use it as the default.

Re: [whatwg] Proposal for separating script downloads and execution

2011-02-15 Thread Kyle Simpson
Although I'm not aware of anyone wrapping a 250KB style-sheet in comments, the pre-loading interface could seemingly be applied to any number of elements. Nicholas' original e-mail referenced a blog post by Stoyan Stefanov which details a way to pre-fetch both scripts and stylesheets. It's

Re: [whatwg] Why are media event handlers defined on HTMLElement instead of HTMLMediaElement

2011-02-15 Thread Philip Jägenstedt
On Tue, 15 Feb 2011 19:13:26 +0100, David Flanagan da...@davidflanagan.com wrote: On 02/15/2011 02:17 AM, Philip Jägenstedt wrote: On Mon, 14 Feb 2011 22:54:54 +0100, David Flanagan da...@davidflanagan.com wrote: The draft specification defines 20+ medial event handler IDL attributes on

Re: [whatwg] HTML5 video: frame accuracy / SMPTE

2011-02-15 Thread Kevin Marks
Returning to this discussion, I think it is lacking in use cases. Consider the controllers we are used to - they tend to have frame step, chapter step and some kind of scrub bar. Frame stepping is used when you want to mark an accurate in or our point, or catch a still frame. This needs to be

Re: [whatwg] HTML5 video: frame accuracy / SMPTE

2011-02-15 Thread Rob Coenen
Rather than trying to sum up all use cases I think that the media asset should be fully random accessible and frame accurate to cover any current and future us ecasse. You should be able to write Javascripts that tell the asset to go to any point in time. That way a web developer (or implementers

Re: [whatwg] Proposal for IsSearchProviderInstalled / AddSearchProvider

2011-02-15 Thread Kornel Lesiński
On Mon, 14 Feb 2011 21:34:27 -, David Levin le...@chromium.org wrote: IsSearchProviderInstalled(string url) returns * 2 if the origin in the given url is the default search provider * 1 if the origin in the given url is a search provider but not the default. * 0 otherwise If the

Re: [whatwg] Proposal for IsSearchProviderInstalled / AddSearchProvider

2011-02-15 Thread Bjoern Hoehrmann
* Kornel Lesi?ski wrote: Change of default search engine may have security implications — there are less tech-savvy people who rely on search engine for *everything* they do on the net and blindly trust the results (see famous facebook login case). (There are in fact many people who do not

Re: [whatwg] Google Feedback on the HTML5 media a11y specifications

2011-02-15 Thread Glenn Maynard
On Tue, Feb 15, 2011 at 11:26 AM, Philip Jägenstedt phil...@opera.com wrote: Related to line breaking, should there be an nbsp; escape?  Inserting nbsp literally into files is somewhat annoying for authoring, since they're indistinguishable from regular spaces. I would kind of prefer not

Re: [whatwg] Device element and the lifetime of the stream objects

2011-02-15 Thread timeless
2011/2/15 Leandro Graciá Gil leandrogra...@chromium.org: Given the above case, we don't think that the lifetime of the Stream objects should be controlled exclusively by the Web application. We think that the specification should state the UA must allow the user to explicitly revoke access.

Re: [whatwg] Why are media event handlers defined on HTMLElement instead of HTMLMediaElement

2011-02-15 Thread David Flanagan
On 02/15/2011 12:44 PM, Philip Jägenstedt wrote: On Tue, 15 Feb 2011 19:13:26 +0100, David Flanagan da...@davidflanagan.com wrote: What about Document and Window? What's the justification for defining the media event handler attributes on those objects? Huh, it is on Window, I hadn't seen

Re: [whatwg] Proposal for separating script downloads and execution

2011-02-15 Thread Nicholas Zakas
As much as I love you guys, please make sure that only one of my email addresses is being used. I've had to remove my personal email address from this thread at least twice and it keeps magically reappearing. :) I do believe that preloading of style sheets is a very different use case than

Re: [whatwg] Google Feedback on the HTML5 media a11y specifications

2011-02-15 Thread Silvia Pfeiffer
On Wed, Feb 16, 2011 at 3:26 AM, Philip Jägenstedt phil...@opera.com wrote: On Tue, 15 Feb 2011 12:57:02 +0100, Glenn Maynard gl...@zewt.org wrote: Following up on a use case discussed earlier, an alternative approach for adding mid-cue comments, such as editor notes, would be to wrap them in

Re: [whatwg] Proposal for separating script downloads and execution

2011-02-15 Thread Glenn Maynard
On Tue, Feb 15, 2011 at 6:33 PM, Nicholas Zakas nza...@yahoo-inc.com wrote: That being said, I think we're going a bit off-track now. Both Kyle's and my proposals are based on already-existing functionality that we know doesn't break the web (code hacks aside). We'd both like to formalize

Re: [whatwg] Google Feedback on the HTML5 media a11y specifications

2011-02-15 Thread Glenn Maynard
On Tue, Feb 15, 2011 at 7:01 PM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: I would prefer if we could stick with a line based approach to this issue and something that can be resolved without having to look at a style sheet. If we do it this way, it doesn't become a pre-processor type

Re: [whatwg] Google Feedback on the HTML5 media a11y specifications

2011-02-15 Thread Silvia Pfeiffer
Can you provide some good examples where mid-cue comments make sense? I'm just wondering if it is really an 80% use case. I suppose, you can always do c.comment and then style it as display:none, but this would only work in a browser unless offline caption applications start supporting style

Re: [whatwg] Google Feedback on the HTML5 media a11y specifications

2011-02-15 Thread Glenn Maynard
On Tue, Feb 15, 2011 at 7:36 PM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Can you provide some good examples where mid-cue comments make sense? I'm just wondering if it is really an 80% use case. Editors marking words and sentences that need attentionc.glenn***/c, commenting on word

[whatwg] Allowing size and maxlength attributes for all new input types would provide better fallbacks

2011-02-15 Thread Jukka K. Korpela
The current version disallows the size and maxlength attributes in input elements when type=time, type=date, type=datetime, type=datetime-local, type=number, type=range, or type=color is used. I suppose the reason is that for other new input types, browsers are expected to use advanced user