Re: [whatwg] AppCache and SharedWorkers?

2009-03-27 Thread Alexey Proskuryakov
On 27.03.2009, at 0:16, Drew Wilson wrote: Are you suggesting that user agents may want to require explicit user permission when any application invokes ApplicationCache.update()? That might be a reasonable approach if a given user agent wants to enforce some kind of no silent update

Re: [whatwg] URL decomposition on HTMLAnchorElement interface

2009-03-27 Thread Kartikaya Gupta
On Thu, 26 Mar 2009 23:01:34 -0400, Biju bijumaill...@gmail.com wrote: On Thu, Mar 26, 2009 at 5:26 PM, Kartikaya Gupta This behavior seems rather inconsistent and possibly buggy. At first look I also thought it is inconsistent But later I found Firefox is very consistent. I think reason

Re: [whatwg] URL decomposition on HTMLAnchorElement interface

2009-03-27 Thread Jonas Sicking
On Fri, Mar 27, 2009 at 4:55 AM, Kartikaya Gupta lists.wha...@stakface.com wrote: On Thu, 26 Mar 2009 23:01:34 -0400, Biju bijumaill...@gmail.com wrote: On Thu, Mar 26, 2009 at 5:26 PM, Kartikaya Gupta This behavior seems rather inconsistent and possibly buggy. At first look I also thought

Re: [whatwg] URL decomposition on HTMLAnchorElement interface

2009-03-27 Thread Jonas Sicking
On Fri, Mar 27, 2009 at 11:02 AM, Kristof Zelechovski giecr...@stegny.2a.pl wrote: Instead of setting the host name of a hyperreference to null, use the host name (of the base) of the current document instead. That seems pretty arbitrary. How about throwing or setting the whole href to null

[whatwg] Recall: URL decomposition on HTMLAnchorElement interface

2009-03-27 Thread Křištof Želechovski
Křištof Želechovski would like to recall the message, [whatwg] URL decomposition on HTMLAnchorElement interface. attachment: winmail.dat

Re: [whatwg] URL decomposition on HTMLAnchorElement interface

2009-03-27 Thread Boris Zbarsky
Kartikaya Gupta wrote: I was trying different things to see what happens and came across some particularly weird behavior in Gecko/2009021910 Firefox/3.0.7: var a = document.createElement('a'); a.setAttribute('href', 'http://example.org:123/foo?bar#baz'); a.hostname = null;

Re: [whatwg] URL decomposition on HTMLAnchorElement interface

2009-03-27 Thread Kartikaya Gupta
On Fri, 27 Mar 2009 14:14:35 -0400, Boris Zbarsky bzbar...@mit.edu wrote: This case is more fun. It's an unknown scheme, so it's assumed to be a no-authority non-hierarchical scheme and the URI is parsed that way. This does cause issues, since RFC 3986 says that i there is no authority

Re: [whatwg] Canvas - Exception on arc with negative radius

2009-03-27 Thread Martin Atkins
Dirk Schulze wrote: Another example is: http://blahbleh.com/molecools.php?name=1,2% 20dimethylcyclopropane If you turn the molecule a bit, the circles disappear with a INDEX_SIZE_ERR exception. Isn't it better to just ignore the arc and go on with the drawing, like Firefox does? And perhaps

Re: [whatwg] URL decomposition on HTMLAnchorElement interface

2009-03-27 Thread Boris Zbarsky
Kartikaya Gupta wrote: For unknown schemes, if the authority starts with //, doesn't it make sense to assume that the scheme allows an authority? I would assume that for an unknown scheme, the generic URI syntax in RFC3986 should be followed, which would interpret the stuff between // and the

Re: [whatwg] URL decomposition on HTMLAnchorElement interface

2009-03-27 Thread Anne van Kesteren
On Fri, 27 Mar 2009 22:40:08 +0100, Boris Zbarsky bzbar...@mit.edu wrote: This is an option, but it's not obviously correct, just as it's not obviously correct (and in fact would break pages) to parse http:foo.com/ without an authority. Which pages would break? That URL does not work in

Re: [whatwg] localStorage + worker processes

2009-03-27 Thread Michael Nordman
On Tue, Mar 24, 2009 at 2:11 AM, Ian Hickson i...@hixie.ch wrote: I've updated the specs as follows: - removed localStorage from Web Workers for now. - extended the implicit lock mechanism that we had for storage to also cover document.cookie, and made the language more explicit about

Re: [whatwg] localStorage + worker processes

2009-03-27 Thread Michael Nordman
sessionLifetime + tabSpecificScope doesn't make much sense since you get a new set of tabs when starting a new session Sorry... make that persistentLifetime + tabScope doesn't make sense. On Fri, Mar 27, 2009 at 3:29 PM, Michael Nordman micha...@google.comwrote: On Tue, Mar 24, 2009 at

[whatwg] Canvas Shadows - Unnecessary Barrier to Entry

2009-03-27 Thread Charles Pritchard
All, It's my firmly held belief that #shadow should be removed from the HTML 5 Canvas specs, as soon as possible. We've been working on Javascript / Canvas projects for two years now. We're in the process of releasing full implementations targeting the Common Runtime Language, Java AWT,

Re: [whatwg] URL decomposition on HTMLAnchorElement interface

2009-03-27 Thread Boris Zbarsky
Anne van Kesteren wrote: On Fri, 27 Mar 2009 22:40:08 +0100, Boris Zbarsky bzbar...@mit.edu wrote: This is an option, but it's not obviously correct, just as it's not obviously correct (and in fact would break pages) to parse http:foo.com/ without an authority. Which pages would break? That

[whatwg] Canvas - toTempURL - A dangerous proposal

2009-03-27 Thread Charles Pritchard
toTempURL( format ) returns string temporary file path. I'd like to solicit feedback from the community about a work-around we're [likely] including in one of our Internet Explorer Canvas implementations. Legacy clients may have terrible support for extensibility. I think we know which

Re: [whatwg] Canvas - toTempURL - A dangerous proposal

2009-03-27 Thread Boris Zbarsky
Charles Pritchard wrote: The draw back of this scheme is that Canvas can now write to a users hard drive. A Denial of Service exploit could run toTempURL in an infinite loop, filling up the users temporary files directory until the browser puts a stop to the sillyness. Even worse, doesn't

Re: [whatwg] Canvas - toTempURL - A dangerous proposal

2009-03-27 Thread Charles Pritchard
Having thought a little more about it (thank you for the feedback), returning a reference to a custom URL handler (up to the implementation) would resolve the security issues. toTempURL returning... customHandler://randomData.png [any kind of reference], would work in the legacy platforms

Re: [whatwg] Canvas - toTempURL - A dangerous proposal

2009-03-27 Thread Boris Zbarsky
Charles Pritchard wrote: Having thought a little more about it (thank you for the feedback), returning a reference to a custom URL handler (up to the implementation) would resolve the security issues. toTempURL returning... customHandler://randomData.png [any kind of reference], would work in

Re: [whatwg] URL decomposition on HTMLAnchorElement interface

2009-03-27 Thread Kartikaya Gupta
On Fri, 27 Mar 2009 17:40:08 -0400, Boris Zbarsky bzbar...@mit.edu wrote: Kartikaya Gupta wrote: - Attempts to set pathname to null should throw, since the path is a required component of a URI. Setting pathname to anything else should be allowed and should update the path component

[whatwg] Worker feedback

2009-03-27 Thread Ian Hickson
On Thu, 5 Mar 2009, Jonas Sicking wrote: Allowing cookie to be set would unfortunately create a synchronous communication channel between the worker and the main window. This is something that we need to avoid to prevent users from having to deal with locking and other thread related

Re: [whatwg] Canvas - toTempURL - A dangerous proposal

2009-03-27 Thread Tab Atkins Jr.
On Fri, Mar 27, 2009 at 7:55 PM, Charles Pritchard ch...@jumis.com wrote: I asked myself the same question, a few minutes after posting my reply. At this point, I'm really not sure. My concern is that the string length for a URL may be limited, somewhere in the platform. If that's the case,

[whatwg] video and acceleration

2009-03-27 Thread Benjamin M. Schwartz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear What, Short: video won't work on slow devices. Help! Long: The video tag has great potential to be useful on low-powered computers and computing devices, where current internet video streaming solutions (such as Adobe's Flash) are too