[whatwg] XML/XSL attributes - Disposing of vendor specific XSL javascript

2010-07-21 Thread Doc
OK , there is a lot of fanboy-isim for exciting topics like video. Nothing wrong with that , I think Video , device and other topics are worthy subjects. I do though think that in the rush for the fab topics that we are ignoring some valuable subjects. I have suggested in the past that we

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Mike Shaver
On Wed, Jul 21, 2010 at 9:10 AM, Nils Dagsson Moskopp nils-dagsson-mosk...@dieweltistgarnichtso.net wrote: (clients try to guess based on incorrect information and you end up with stupid switches). Could you be more specific about the incorrect information? My understanding, from this thread

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Henri Sivonen
While the robustness principle is indeed a good start, this is a situation where we are mostly starting with a clean slate. No reason to muddy the waters without having actual problems in the wild, or else it's the tag soup situation all again (clients try to guess based on incorrect

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Mike Shaver
On Wed, Jul 21, 2010 at 9:43 AM, Nils Dagsson Moskopp nils-dagsson-mosk...@dieweltistgarnichtso.net wrote: Mike Shaver mike.sha...@gmail.com schrieb am Wed, 21 Jul 2010 09:15:18 -0400: and furthermore that the appropriate MIME type for ogg-with-VP8 vs ogg-with-theora isn't clear (or possibly

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Philip Jägenstedt
On Wed, 21 Jul 2010 15:15:18 +0200, Mike Shaver mike.sha...@gmail.com wrote: On Wed, Jul 21, 2010 at 9:10 AM, Nils Dagsson Moskopp nils-dagsson-mosk...@dieweltistgarnichtso.net wrote: (clients try to guess based on incorrect information and you end up with stupid switches). Could you be

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Mike Shaver
On Wed, Jul 21, 2010 at 9:46 AM, Chris Double chris.dou...@double.co.nz wrote: How much data are you willing to sniff to find out if the Ogg file contains Theora and/or Vorbis? You have to read the header packets contained within the Ogg file to get this. A few kilobytes certainly seems

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Philip Jägenstedt
On Wed, 21 Jul 2010 15:51:40 +0200, Mike Shaver mike.sha...@gmail.com wrote: On Wed, Jul 21, 2010 at 9:46 AM, Chris Double chris.dou...@double.co.nz wrote: How much data are you willing to sniff to find out if the Ogg file contains Theora and/or Vorbis? You have to read the header packets

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Mike Shaver
On Wed, Jul 21, 2010 at 9:51 AM, Philip Jägenstedt phil...@opera.com wrote: On Wed, 21 Jul 2010 15:15:18 +0200, Mike Shaver mike.sha...@gmail.com wrote: Could you be more specific about the incorrect information?  My understanding, from this thread and elsewhere, is that video formats are

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Chris Double
On Thu, Jul 22, 2010 at 1:53 AM, Philip Jägenstedt phil...@opera.com wrote: Opera does not, that would lead to an extra network roundtrip. Instead, when the MIME type is not one of the allowed ones, the connection is closed immediately. Same with Firefox. There's also no guarantee that after

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Philip Jägenstedt
On Wed, 21 Jul 2010 15:55:24 +0200, Mike Shaver mike.sha...@gmail.com wrote: On Wed, Jul 21, 2010 at 9:51 AM, Philip Jägenstedt phil...@opera.com wrote: On Wed, 21 Jul 2010 15:15:18 +0200, Mike Shaver mike.sha...@gmail.com wrote: Could you be more specific about the incorrect information?

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Mike Shaver
On Wed, Jul 21, 2010 at 10:04 AM, Philip Jägenstedt phil...@opera.com wrote: Right, sniffing is currently only done in the context of video, at least in Opera. The problem could be fixed by adding more sniffing, certainly. A warning that you're about to open a 5MB text document might be humane

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Chris Double
On Thu, Jul 22, 2010 at 1:59 AM, Mike Shaver mike.sha...@gmail.com wrote: That's what I expected, so I guess I don't understand what the how much are you willing to sniff? question is about. When content sniffing are we ignoring the mime type served by the server and always sniffing? If so then

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Mike Shaver
On Wed, Jul 21, 2010 at 10:07 AM, Chris Double chris.dou...@double.co.nz wrote: When content sniffing are we ignoring the mime type served by the server and always sniffing? If so then incorrectly configured servers can result in more downloaded data due to having to read the data looking for

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Chris Double
On Thu, Jul 22, 2010 at 2:15 AM, Mike Shaver mike.sha...@gmail.com wrote: ...I would probably suggest that the developers of said browser implement basic Ogg support (enough to say this is Ogg, so we don't support it), and go back to solving more pressing problems! Or the developers of said

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Mike Shaver
On Wed, Jul 21, 2010 at 10:24 AM, Chris Double chris.dou...@double.co.nz wrote: On Thu, Jul 22, 2010 at 2:15 AM, Mike Shaver mike.sha...@gmail.com wrote: ...I would probably suggest that the developers of said browser implement basic Ogg support (enough to say this is Ogg, so we don't support

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Philip Jägenstedt
On Wed, 21 Jul 2010 16:26:20 +0200, Mike Shaver mike.sha...@gmail.com wrote: On Wed, Jul 21, 2010 at 10:24 AM, Chris Double chris.dou...@double.co.nz wrote: On Thu, Jul 22, 2010 at 2:15 AM, Mike Shaver mike.sha...@gmail.com wrote: ...I would probably suggest that the developers of said

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Benjamin M. Schwartz
On 07/21/2010 10:24 AM, Chris Double wrote: Or the developers of said browser could obey the mime type that the server sent, not have to write or maintain error prone content sniffing code that could behave differently across browsers (Chrome content sniffs this as Ogg but you dont!!, etc),

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Boris Zbarsky
On 7/21/10 9:10 AM, Nils Dagsson Moskopp wrote: While the robustness principle is indeed a good start, this is a situation where we are mostly starting with a clean slate. Maciej's point was that Safari doesn't feel like it's starting with a clean slate. Lets not forget that the broken

[whatwg] Scrollable Tables and HTML5

2010-07-21 Thread Schalk Neethling
Hi all, I have been working on getting scrollable tables working across all browsers. While there exists jQuery plugins that does the job for the most part, I have to find one that works 100% and works at all in Chrome. The reason I am putting this to the HTML5 list is because I am wondering

[whatwg] iframes with potential for independent navigation controls

2010-07-21 Thread Brett Zamir
I would like to see attributes be added to allow iframes to have independent navigation controls, or rather, to allow a parent document to have ongoing access to the navigation history of its iframes (say to be informed of changes to their histories via an event) so that it could create such

Re: [whatwg] Scrollable Tables and HTML5

2010-07-21 Thread Boris Zbarsky
On 7/21/10 2:43 PM, Schalk Neethling wrote: The only browser, including the IE9 previews, that has implemented this behavior is Firefox. Note that the Firefox implementation was removed, because it violated the CSS2.1 spec, caused compatibility problems for other browsers, and was buggy to

[whatwg] Web Workers

2010-07-21 Thread Ryan Heise
Web Workers offer reliability and performance benefits on multi-core CPUs to a certain class of parallelisable tasks that are primarily concerned with raw computation over data access. It can clearly be seen that the lower the ratio of data access to raw computation, the more performance benefits

Re: [whatwg] Web Workers

2010-07-21 Thread Drew Wilson
On Wed, Jul 21, 2010 at 1:11 PM, Ryan Heise r...@ryanheise.com wrote: For all of the reasons above, I would like to see something like threads in Javascript. Yes, threads give rise to race conditions and deadlocks, but this seems to be in line with Javascript's apparent philosophy of doing

Re: [whatwg] Web Workers

2010-07-21 Thread Boris Zbarsky
On 7/21/10 4:11 PM, Ryan Heise wrote: Note that things might have been different had Javascript been a purely functional language. If this were the case, then there would be much safer and more efficient alternatives to making whole copies of data that could be implemented under the hood.

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Chris Double
On Thu, Jul 22, 2010 at 6:10 AM, Boris Zbarsky bzbar...@mit.edu wrote: I don't like sniffing any more than the next guy, but the work needed to properly MIME label a modern media format (with the whole container and multiple streams thing) is ... excessive.  I doubt anyone's going to do it, so

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Robert O'Callahan
On Thu, Jul 22, 2010 at 2:07 AM, Chris Double chris.dou...@double.co.nzwrote: When content sniffing are we ignoring the mime type served by the server and always sniffing? If so then incorrectly configured servers can result in more downloaded data due to having to read the data looking for a

Re: [whatwg] video application/octet-stream

2010-07-21 Thread Chris Double
On Thu, Jul 22, 2010 at 12:22 PM, Robert O'Callahan rob...@ocallahan.org wrote: Also, in your example the author could have provided type= attributes on the source elements to control what gets downloaded. I assume that no-one is proposing we ignore those. This is true but the provider of the