On Thu, 06 May 2010 17:20:41 +0200, Simon Pieters sim...@opera.com wrote:
On Tue, 20 Apr 2010 16:00:36 +0200, Simon Pieters sim...@opera.com
wrote:
[[
WebSocket object with an open connection must not be garbage collected
if there are any event listeners registered for message events.
]]
On 20 May 2010 00:38, David Gerard dger...@gmail.com wrote:
x264 don't think much of VP8, they think it's just not ready:
http://x264dev.multimedia.cx/?p=377
OTOH, that may not end up mattering.
Greg Maxwell thinks it's only about as much of a car crash as VP3 was
when it was released:
On Thu, May 20, 2010 at 4:27 AM, David Gerard dger...@gmail.com wrote:
On 20 May 2010 00:38, David Gerard dger...@gmail.com wrote:
x264 don't think much of VP8, they think it's just not ready:
http://x264dev.multimedia.cx/?p=377
OTOH, that may not end up mattering.
Greg Maxwell thinks
I just became aware that application/octet-stream is excluded from being a
type the user agent knows it cannot render.
http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#a-type-that-the-user-agent-knows-it-cannot-render
Apparently this was done in response to a bug report:
2010/5/20 Peter Beverloo pe...@lvp-media.com:
Microsoft has announced playback support for VP8 in Internet Explorer 9[1]
under the condition that one has to install a VP8 codec manually, albeit via
inclusion in another program: In its HTML5 support, IE9 will support
playback of H.264 video as
On Thu, May 20, 2010 at 9:55 PM, Robert O'Callahan rob...@ocallahan.orgwrote:
I just became aware that application/octet-stream is excluded from being a
type the user agent knows it cannot render.
On Thu, 20 May 2010 17:55:42 +0800, David Gerard dger...@gmail.com wrote:
2010/5/20 Peter Beverloo pe...@lvp-media.com:
Microsoft has announced playback support for VP8 in Internet Explorer
9[1]
under the condition that one has to install a VP8 codec manually,
albeit via
inclusion in
On 20 May 2010 11:03, Philip Jägenstedt phil...@opera.com wrote:
On Thu, 20 May 2010 17:55:42 +0800, David Gerard dger...@gmail.com wrote:
I don't. They're trying to make if you install it yourself, it'll
work look like they're actually doing anything at all. But they're
not, because the same
On Thu, 20 May 2010 17:34:49 +0800, Conan Kudo (ニール・ゴンパ)
ngomp...@gmail.com wrote:
On Thu, May 20, 2010 at 4:27 AM, David Gerard dger...@gmail.com wrote:
On 20 May 2010 00:38, David Gerard dger...@gmail.com wrote:
x264 don't think much of VP8, they think it's just not ready:
On Thu, 20 May 2010 17:59:42 +0800, Robert O'Callahan
rob...@ocallahan.org wrote:
On Thu, May 20, 2010 at 9:55 PM, Robert O'Callahan
rob...@ocallahan.orgwrote:
I just became aware that application/octet-stream is excluded from
being a
type the user agent knows it cannot render.
On Thu, May 20, 2010 at 11:55, David Gerard dger...@gmail.com wrote:
2010/5/20 Peter Beverloo pe...@lvp-media.com:
Microsoft has announced playback support for VP8 in Internet Explorer
9[1]
under the condition that one has to install a VP8 codec manually, albeit
via
inclusion in another
On 20 May 2010 17:55, David Gerard dger...@gmail.com wrote:
2010/5/20 Peter Beverloo pe...@lvp-media.com:
Microsoft has announced playback support for VP8 in Internet Explorer 9[1]
under the condition that one has to install a VP8 codec manually, albeit via
inclusion in another program: In its
On Thu, 20 May 2010 11:55:01 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
I just became aware that application/octet-stream is excluded from being
a
type the user agent knows it cannot render.
On Thu, 20 May 2010 12:36:36 +0200, Simon Pieters sim...@opera.com wrote:
On Thu, 20 May 2010 11:55:01 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
I just became aware that application/octet-stream is excluded from
being a
type the user agent knows it cannot render.
On Thu, May 20, 2010 at 8:16 PM, Adam Harvey a...@adamharvey.name wrote:
On 20 May 2010 17:55, David Gerard dger...@gmail.com wrote:
2010/5/20 Peter Beverloo pe...@lvp-media.com:
Microsoft has announced playback support for VP8 in Internet Explorer 9[1]
under the condition that one has to
On Thu, May 20, 2010 at 1:32 PM, Anne van Kesteren ann...@opera.com wrote:
On Thu, 20 May 2010 14:29:16 +0200, Bjorn Bringert bring...@google.com
wrote:
It should be possible to drive input type=speech with keyboard
input, if the user agent chooses to implement that. Nothing in the API
On Thu, 20 May 2010 12:46:16 +0200, Simon Pieters sim...@opera.com wrote:
On Thu, 20 May 2010 12:36:36 +0200, Simon Pieters sim...@opera.com
wrote:
On Thu, 20 May 2010 11:55:01 +0200, Robert O'Callahan
rob...@ocallahan.org wrote:
I just became aware that application/octet-stream is
On 5/20/10 5:59 AM, Robert O'Callahan wrote:
Hmm. I guess it doesn't add any implementation requirements beyond what
you need to handle the complete absence of a Content-Type (which we
currently don't handle, but I suppose we should).
For what it's worth, the above-necko layer in Gecko never
On Thu, 20 May 2010 14:18:56 +0100, Bjorn Bringert bring...@google.com wrote:
On Thu, May 20, 2010 at 1:32 PM, Anne van Kesteren ann...@opera.com wrote:
On Thu, 20 May 2010 14:29:16 +0200, Bjorn Bringert bring...@google.com
It should be possible to drive input type=speech with
Did anyone revise the registration of application/octet-stream to add
parameters?
On May 20, 2010, at 3:36 , Simon Pieters wrote:
On Thu, 20 May 2010 11:55:01 +0200, Robert O'Callahan rob...@ocallahan.org
wrote:
I just became aware that application/octet-stream is excluded from being a
On May 19, 2010, at 21:48 , Sir Gallantmon (ニール・ゴンパ) wrote:
Google's patent license states that anyone that attempts to sue over VP8 will
automatically lose their patent license. That's a huge deterrent.
only to potential practitioners...not trolls :-( (i.e. non-practicing patent
owners)
On Thu, 20 May 2010 18:44:12 +0200, David Singer sin...@apple.com wrote:
Did anyone revise the registration of application/octet-stream to add
parameters?
No. It's just error handling.
--
Simon Pieters
Opera Software
It's an error to have a parameter that isn't valid for the mime type, so are
you suggesting (a) that you throw away the parameter as it's invalid or (b)
since it's an error to supply application/octet-stream as the mime type in the
first place, we may as well process its invalid parameter in an
On Thu, 20 May 2010 20:18:43 +0200, David Singer sin...@apple.com wrote:
It's an error to have a parameter that isn't valid for the mime type, so
are you suggesting (a) that you throw away the parameter as it's invalid
or (b) since it's an error to supply application/octet-stream as the
On May 11, 2010, at 11:58 AM, Sterling Swigart wrote:
I'm working with David Levin, and based on the feedback received regarding
offscreen canvas, the proposal has been changed to address more specific
scenarios. The main use case was resizing images, so we are proposing an
asynchronous
On Thu, May 20, 2010 at 11:30 AM, Maciej Stachowiak m...@apple.com wrote:
I'm not clear on why this API is needed. ... This API seems much less
general than offscreen canvas, so it's subject to the same criticism and you
can't even make the argument that it also serves other use cases.
The
On Fri, May 21, 2010 at 2:00 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 5/20/10 5:59 AM, Robert O'Callahan wrote:
Hmm. I guess it doesn't add any implementation requirements beyond what
you need to handle the complete absence of a Content-Type (which we
currently don't handle, but I
On May 20, 2010, at 1:00 PM, David Levin wrote:
On Thu, May 20, 2010 at 11:30 AM, Maciej Stachowiak m...@apple.com wrote:
I'm not clear on why this API is needed. ... This API seems much less
general than offscreen canvas, so it's subject to the same criticism and
you can't even
On May 20, 2010, at 5:48 PM, Maciej Stachowiak wrote:
On May 20, 2010, at 1:00 PM, David Levin wrote:
On Thu, May 20, 2010 at 11:30 AM, Maciej Stachowiak m...@apple.com wrote:
I'm not clear on why this API is needed. ... This API seems much less
general than offscreen canvas, so
On Fri, May 21, 2010 at 12:50 PM, Maciej Stachowiak m...@apple.com wrote:
I'd also love to hear from Mike Shaver and others from the original thread
what they think of this API proposal.
I think Shaver's feedback still applies: on any device with a GPU, we can
optimize canvas and/or rendering
On May 20, 2010, at 6:24 PM, Robert O'Callahan wrote:
On Fri, May 21, 2010 at 12:50 PM, Maciej Stachowiak m...@apple.com wrote:
I'd also love to hear from Mike Shaver and others from the original thread
what they think of this API proposal.
I think Shaver's feedback still applies: on any
On Thu, May 20, 2010 at 7:55 PM, Maciej Stachowiak m...@apple.com wrote:
On May 20, 2010, at 6:24 PM, Robert O'Callahan wrote:
On Fri, May 21, 2010 at 12:50 PM, Maciej Stachowiak m...@apple.com wrote:
I'd also love to hear from Mike Shaver and others from the original thread
what they
On May 20, 2010, at 8:13 PM, David Levin wrote:
On Thu, May 20, 2010 at 7:55 PM, Maciej Stachowiak m...@apple.com wrote:
On May 20, 2010, at 6:24 PM, Robert O'Callahan wrote:
On Fri, May 21, 2010 at 12:50 PM, Maciej Stachowiak m...@apple.com wrote:
I'd also love to hear from Mike
On Thu, May 20, 2010 at 5:48 PM, Maciej Stachowiak m...@apple.com wrote:
On May 20, 2010, at 1:00 PM, David Levin wrote:
On Thu, May 20, 2010 at 11:30 AM, Maciej Stachowiak m...@apple.com wrote:
I'm not clear on why this API is needed. ... This API seems much less
general than
On Thu, May 20, 2010 at 3:38 AM, Benjamin Smedberg
benja...@smedbergs.us wrote:
On 5/19/10 5:41 AM, Kühn Wolfgang wrote:
C++
WebCore.html.HTMLCanvasElement (WebKit)
dom.nsIDOMHTMLCanvasElement (Firefox)
Mozilla nsI* interfaces, if they continue to exist, should be treated as
35 matches
Mail list logo
