On Oct 11, 2007, at 6:47 PM, Robert O'Callahan wrote:
On Oct 12, 2007 12:53 PM, Ian Hickson [EMAIL PROTECTED] wrote:
The problem with isLocallyAvailable() -- as noted by Maciej on IRC
-- is
mostly one of race conditions. What if the resource was removed in
between
you asking for it and
Ian Hickson wrote:
On Sat, 6 Oct 2007, Adam Roben wrote:
Here are some comments and questions about section 4.6 Offline Web
applications:
Thanks for the feedback! It was very useful in making the spec better.
Please do continue reviewing the spec!
Glad to hear it!
Can
On Tue, 25 Sep 2007, Maciej Stachowiak wrote:
I agree that the actual I/O to the database should be done up front.
However, it should be possible to make the conversion from SQLite's
native data types to JavaScript datatypes lazy (such type conversion can
have nontrivial cost, especially
On Oct 12, 2007, at 9:42 AM, Adam Roben wrote:
Darin Adler wrote:
On Oct 12, 2007, at 6:11 AM, Adam Roben wrote:
It may be worth stating in this section what the behavior is
when a section or opportunistic caching namespace appears
multiple times. The parsing algorithm makes this clear,
Darin Adler wrote:
On Oct 12, 2007, at 6:11 AM, Adam Roben wrote:
It may be worth stating in this section what the behavior is when a
section or opportunistic caching namespace appears multiple times.
The parsing algorithm makes this clear, but it would be clearer
still to also state the
On Fri, 12 Oct 2007, Maciej Stachowiak wrote:
The race-free approach would be to provide APIs to load resources only
from the cache and to error out immediately if the the request can't be
served locally.
That's what the offline caching system does right now for any URI not on
the
On Oct 12, 2007, at 6:11 AM, Adam Roben wrote:
It may be worth stating in this section what the behavior is when
a section or opportunistic caching namespace appears multiple
times. The parsing algorithm makes this clear, but it would be
clearer still to also state the behavior in this
On 10/12/07, Anne van Kesteren [EMAIL PROTECTED] wrote:
On Fri, 12 Oct 2007 20:46:52 +0200, Ian Hickson [EMAIL PROTECTED] wrote:
Certainly that would be reasonable. I have added it. People should let me
know if they want me to remove or add error codes, by the way.
I think there should be
On Fri, 12 Oct 2007 20:46:52 +0200, Ian Hickson [EMAIL PROTECTED] wrote:
Certainly that would be reasonable. I have added it. People should let me
know if they want me to remove or add error codes, by the way.
I think there should be an error code for the database being full. For
some
On Fri, 12 Oct 2007, Adam Roben wrote:
(Now step 20.) It does. Which is to say, it being on the online
whitelist has no effect. Should it have an effect? We can omit the
caching of such files if you want.
Given that section 4.6.5.1 says that resources in the online whitelist
are
On Wed, 21 Mar 2007, Kornel Lesinski wrote:
This however is a little help to users who want to bookmark videos or
share links to certain parts of them - without a standard way of doing
it UA's won't be able to provide UI for it. Even if you implement that
for yourself using UserJS, you
On Wed, 21 Mar 2007, Mihai Sucan wrote:
Shouldn't the video API include a way to toggle full screen on/off? This
is a rather basic feature of videos. If it will not be available, video
sites will hack around missing full screen support.
The current spec doesn't define it.
Currently, the
On Wed, 21 Mar 2007, Martin Hassman wrote:
I feel conflict here:
a) UA provide some Fullscreen item in popup menu (from the discussion
seems for me that there shouldn't be any UA-GUI in page than popup menu)
b) web author give some Fullscreen button inside his video controls (to
look
On Wed, 21 Mar 2007, Kornel Lesinski wrote:
Couldn't this be protected in a similar way pop-up blocking works? If
not, browsers could simply display confirmation dialog box before
entering fullscreen (some sort of protection is neccessary to protect
against phishing and annoyance).
The
On Wed, 21 Mar 2007, Robert Brodrecht wrote (in response to Apple's
proposal, quoted):
If the presentation of timed media by the user agent has been disabled, if
the resource has an unsupported type, or if the preparations for its
presentation fail either because of a protocol failure or
On Oct 12, 2007, at 12:16 PM, Ian Hickson wrote:
On Fri, 12 Oct 2007, Maciej Stachowiak wrote:
The race-free approach would be to provide APIs to load resources
only
from the cache and to error out immediately if the the request
can't be
served locally.
That's what the offline caching
On Wed, 21 Mar 2007, Robert Sayre wrote:
My two cents: we should put off events and other API pieces that address
editing applications. It is possible to write web versions of things
like iMovie and SoundEdit in Flash right now, but I don't think it is
realistic to capture that stuff in a
On Sat, 4 Nov 2006, Anne van Kesteren wrote:
On Sat, 04 Nov 2006 07:37:32 +0100, Ian Hickson [EMAIL PROTECTED] wrote:
* It should probably mention 'img.src = foo' (that loading directly
starts). I thought that 'img.setAttribute(src, foo)' even did
different things in browsers (when
On Oct 12, 2007 9:39 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Oct 11, 2007, at 6:47 PM, Robert O'Callahan wrote:
On Oct 12, 2007 12:53 PM, Ian Hickson [EMAIL PROTECTED] wrote:
The problem with isLocallyAvailable() -- as noted by Maciej on IRC -- is
mostly one of race conditions.
On Thu, 22 Mar 2007, Sander Tekelenburg wrote:
http://webkit.org/specs/HTML_Timed_Media_Elements.html
I'm worried about The controller attribute is a boolean attribute. If
the attribute is present, the user agent must display a user interface
which allows the user to control the media
On Thu, 22 Mar 2007, Dave Raggett wrote:
From an accessibility perspective the proposal lacks support for
captioning. There should be a mechanism for enabling/disabling captions
to avoid disadvantaging people who have difficulties with hearing the
audio. It should further be possible to
On Thu, 22 Mar 2007, ddailey wrote:
As a newcomer to this group, please forgive my ignorance of discussions
that, undoubtedly, have already taken place, but as I have been reading
these threads on video and timed media and object, a couple of
questions have come to mind:
1. why not just
On Thu, 22 Mar 2007, Nicholas Shanks wrote:
Volume has the range 0-100 in the DOM interface, but 0.0-1.0 in CSS. These
should be consistent (I favour zero to one and allowing percentages).
The spec now uses a float and 0.0 .. 1.0.
I think that the ERROR state attribute should have a value
At 0:30 + 13/10/07, Ian Hickson wrote:
On Thu, 22 Mar 2007, Dave Raggett wrote:
From an accessibility perspective the proposal lacks support for
captioning. There should be a mechanism for enabling/disabling captions
to avoid disadvantaging people who have difficulties with hearing the
At 0:34 + 13/10/07, Ian Hickson wrote:
On Thu, 22 Mar 2007, ddailey wrote:
As a newcomer to this group, please forgive my ignorance of discussions
that, undoubtedly, have already taken place, but as I have been reading
these threads on video and timed media and object, a couple of
On Thu, 22 Mar 2007, Dan Brickley wrote:
I've not followed it, ... but there's a SMIL subset integrated with
XHTML at http://www.w3.org/TR/XHTMLplusSMIL/ ... if you find SMIL too
large, perhaps this or another profile is less intimidating?
This profile doesn't seem to define error handling,
On Fri, 23 Mar 2007, Anne van Kesteren wrote:
I don't really like this element. The name is confusing especially with
an attribute named src=. It also introduces yet another void element,
can't we just reuse param? The value= attribute of param would
point to a resource and the type=
On Fri, 23 Mar 2007, Nicholas Shanks wrote:
How about:
playlistol
liaudio src=foo type=...Audio fallback/audio/li
livideo src=bar type=...Video fallback/video/li
/ol/playlist
User agents that don't support playlist, audio and video just get an ordered
list of fallback
On Mon, 2 Apr 2007, Kevin Calhoun wrote:
I've been evaluating the behavior of the HTMLMediaElement in the current
working draft in light of the various network protocols and player
behaviors that I'm familiar with, and I think the current specification
of loading behavior and the
29 matches
Mail list logo
