Hi Charles,
Le 10/08/2011 23:19, Charles Pritchard a écrit :
On 8/9/2011 1:00 AM, Cyril Concolato wrote:
Hi Charles,
I believe that GPAC seeks through large SVG files via offsets and small
buffers, from what I understood at SVG F2F.
http://gpac.wp.institut-telecom.fr/
The technique is
On 08/11/2011 03:44 AM, Rafael Weinstein wrote:
Although everyone seems to agree that mutations should be delivered
after the DOM operations which generated them complete, the question
remains:
When, exactly, should mutations be delivered?
The four options I'm aware of are:
1) Immediately
[ Topic changed to how to organize the group's DOM specs ... ]
Hi Adrian, Anne, Doug, Jacob, All,
The WG is chartered to do maintenance on the DOM specs so a question for
us is how to organize the DOM specs, in particular, whether Anne's DOM
spec should be constrained (or not) to some set of
Hi Art,
(CCing some people you apparently forget to CC, but who might have an
opinion on this matter, and a stake in the outcome of the discussion.)
On 08/11/2011 12:28 PM, Arthur Barstow wrote:
[ Topic changed to how to organize the group's DOM specs ... ]
Hi Adrian, Anne, Doug, Jacob,
Hi Art,
+1 for publication of the LCWD.
Bryan
On 8/10/11 7:24 AM, Arthur Barstow art.bars...@nokia.com wrote:
Given Hixie's recent set of bug fixes, the Server-sent Events spec now
has zero bugs. As such, it appears this spec is ready to proceed on the
Recommendation track and this is a
On Thu, Aug 11, 2011 at 6:28 AM, Arthur Barstow art.bars...@nokia.com wrote:
Before we publish a new WD of Anne's DOM spec, I would like comments on how
the DOM specs should be organized. In particular: a) whether you prefer the
status quo (currently that is DOM Core plus D3E) or if you want
Thanks Olli. I think this is now a fairly complete summary of the
issues identified thus far.
It'd be great to get some additional views -- in particular from folks
representing UAs that haven't yet registered any observations or
opinons.
Note: I think what Olli has listed is fair, but I'm
On 08/11/2011 06:13 PM, Rafael Weinstein wrote:
Con:
Since the approach is bound to tasks, it is not clear what should happen
if event loop spins while handling the task. What if some other task
modifies the DOM[1], when should the mutation callbacks fire?
Because of this issue, tasks, which may
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13761
Summary: Now that event data can be discarded (if there is no
newline before eof), the last id field value received
should be stored in a buffer and set as the
EventSource's
On Thu, Aug 11, 2011 at 9:12 AM, Olli Pettay olli.pet...@helsinki.fi wrote:
On 08/11/2011 06:13 PM, Rafael Weinstein wrote:
Con:
Since the approach is bound to tasks, it is not clear what should happen
if event loop spins while handling the task. What if some other task
modifies the DOM[1],
Generally speaking, browsers have been moving away from triggering
authentication dialogs for subresource loads because they are more
often used for phishing than for legitimate purposes. A WebSocket
connection is much like a subresource load.
Adam
On Wed, Aug 10, 2011 at 9:36 PM, Brian Raymor
Greetings WebApps WG,
The latest editor's draft of the File API can be found here:
http://dev.w3.org/2006/webapi/FileAPI/
Changes are based on feedback on this listserv, as well as the URI
listserv (e.g. [1][2][3]).
Chrome team: some of the feedback is to more rigorously define the
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13634
Aryeh Gregor a...@aryeh.name changed:
What|Removed |Added
Status|NEW |RESOLVED
Þann mán 8.ágú 2011 20:31, skrifaði Simon Heckmann:
Well, not directly an answer to your question, but the use case I had in mind
is the following:
A large encrypted video (e.g. HD movie with 2GB) file is stored using the File
API, I then want to decrypt this file and start playing with only
See below!
Am 11.08.2011 um 23:24 schrieb Bjartur Thorlacius svartma...@gmail.com:
Þann mán 8.ágú 2011 20:31, skrifaði Simon Heckmann:
Well, not directly an answer to your question, but the use case I had in
mind is the following:
A large encrypted video (e.g. HD movie with 2GB) file is
FYI I'm working on an experimental extension to Chromium to allow media data
to be streamed into a media element via JavaScript. Here is the draft
spechttp://html5-mediasource-api.googlecode.com/svn/tags/0.2/draft-spec/mediasource-draft-spec.html
and
pending WebKit patch
Comments inline...
On Wed, Aug 10, 2011 at 2:05 PM, Charles Pritchard ch...@jumis.com wrote:
On 8/9/2011 9:38 AM, Aaron Colwell wrote:
FYI I'm working on an experimental extension to Chromium to allow media
data to be streamed into a media element via JavaScript. Here is the draft
You actually can get mouse delta info in windows using raw WM_INPUT data
see: http://msdn.microsoft.com/en-us/library/ee418864(VS.85).aspx. This is
also the only way to take advantage of 400dpi mice, which is useful for
FPS games.
As for mouse locking isn't that a completely distinct feature
I came across this while implementing support for the new Transferable[1]
interface for Chromium. initMessageEvent is defined[2] as:
void initMessageEvent(in DOMString typeArg, in boolean canBubbleArg, in
boolean cancelableArg, in any dataArg, in DOMString originArg, in DOMString
On Tue, 9 Aug 2011, Luke Zarko wrote:
I came across this while implementing support for the new
Transferable[1] interface for Chromium. initMessageEvent is defined[2]
as:
void initMessageEvent(in DOMString typeArg, in boolean canBubbleArg,
in boolean cancelableArg, in any dataArg, in
On Thu, Aug 11, 2011 at 12:43 PM, Arun Ranganathan a...@mozilla.com wrote:
Greetings WebApps WG,
The latest editor's draft of the File API can be found here:
http://dev.w3.org/2006/webapi/**FileAPI/http://dev.w3.org/2006/webapi/FileAPI/
Changes are based on feedback on this listserv, as
For FileReader.abort(), we should only fire abort and loadend
events if there is a load currently in progress. If no load is in
progress then no events should be fired.
Basically the invariant we want to enforce is that for each
loadstart event there is one and exactly one loadend event as well
Re Rob:
Is there a need to provide mouse-locking on a per-element basis? It seems
to
me it would be enough for mouse-locking to be per-DOM-window (or
per-DOM-document) and deliver events to the focused element. This
simplifies
the model a little bit by not having to define new state for the
On Fri, Aug 12, 2011 at 2:27 PM, Vincent Scheib sch...@google.com wrote:
Re Rob:
Is there a need to provide mouse-locking on a per-element basis? It seems
to
me it would be enough for mouse-locking to be per-DOM-window (or
per-DOM-document) and deliver events to the focused element. This
24 matches
Mail list logo
