Re: [whatwg] setting location.hash property and browser reload

2009-07-08 Thread Boris Zbarsky
Ian Hickson wrote: HTML5 requires that there not be a reload. Setting location.hash eventually (if you follow the admittedly convoluted definitions) is equivalent to running the navigation algorithm: http://www.whatwg.org/specs/web-apps/current-work/#navigate ...which, in step 4, just scro

Re: [whatwg] setting location.hash property and browser reload

2009-07-08 Thread Ian Hickson
On Wed, 8 Jul 2009, Peter Michaux wrote: > > When setting the location.hash property, some older browsers reloaded > the entire page. The newest versions of the major browsers doe not > reload the page when setting location.hash. This seems to be now de > facto standard behavior. Sites like Yaho

[whatwg] setting location.hash property and browser reload

2009-07-08 Thread Peter Michaux
When setting the location.hash property, some older browsers reloaded the entire page. The newest versions of the major browsers doe not reload the page when setting location.hash. This seems to be now de facto standard behavior. Sites like Yahoo Maps! depends on the page not reloading when setting

Re: [whatwg] Need UNIFIED UI for web browser plugin security settings.

2009-07-08 Thread Jonas Sicking
On Tue, Jul 7, 2009 at 9:14 PM, Biju wrote: > On Tue, Jul 7, 2009 at 11:10 PM, Nils Dagsson > Moskopp wrote: >>> So in browsers, we need a UNIFIED UI for plugin security settings. >> >> Actually, do we ? I don't think so. Like with UI for and >> , implementors can very well compete on this. > > I

Re: [whatwg] A Selector-based metadata proposal (was: Annotating structured data that HTML has no semantics for)

2009-07-08 Thread Ian Hickson
On Wed, 10 Jun 2009, Eduard Pascual wrote: > > > > I think this is a level of indirection too far -- when something is a > > heading, it should _be_ a heading, it shouldn't be labeled opaquely > > with a transformation sheet elsewhere defining that is maps to the > > heading semantic. > > That d

Re: [whatwg] Limit on number of parallel Workers.

2009-07-08 Thread Michael Nordman
> This type of UA-specific setting is something best left outside the spec entirely. Yup On Wed, Jul 8, 2009 at 10:08 AM, Drew Wilson wrote: > I think Ian's decision to add no language to the spec is the correct one. > To be clear, we were never asking for Ian to put a limit in the spec - > rat

Re: [whatwg] Limit on number of parallel Workers.

2009-07-08 Thread Drew Wilson
I think Ian's decision to add no language to the spec is the correct one. To be clear, we were never asking for Ian to put a limit in the spec - rather, given the de facto existence of limits on some platforms, we wanted to discuss how those platforms should behave to ensure that they were still co

Re: [whatwg] Codecs for and

2009-07-08 Thread Charles Pritchard
On 7/8/09 2:20 AM, Philip Jagenstedt wrote: On Tue, 07 Jul 2009 22:45:41 +0200, Charles Pritchard wrote: At some point, a Blob / Stream API could make things like this easier. If the idea is to write a Vorbis decoder in JavaScript that would be quite cool in a way, but for vendors already impl

Re: [whatwg] Limit on number of parallel Workers.

2009-07-08 Thread Eduard Pascual
On Wed, Jul 8, 2009 at 1:59 AM, Ian Hickson wrote: > > I include below, for the record, a set of e-mails on the topic of settings > limits on Workers to avoid DOS attacks. > > As with other such topics, the HTML5 spec allows more or less any > arbitrary behaviour in the face of hardware limitations

Re: [whatwg] Codecs for and

2009-07-08 Thread Philip Jagenstedt
On Tue, 07 Jul 2009 22:45:41 +0200, Charles Pritchard wrote: On 7/7/09 1:10 PM, Philip Jagenstedt wrote: On Tue, 07 Jul 2009 17:52:29 +0200, Charles Pritchard wrote: Philip Jagenstedt wrote: For all of the simpler use cases you can already generate sounds yourself with a data uri. For