Hi Arthur,
On Wed, Nov 23, 2011 at 10:20 PM, Arthur Barstow art.bars...@nokia.comwrote:
Hi IanF, All,
Following up on Quota API vis-à-visCharterChanges wiki [1] ...
Does the group want to add Quota API to the group's charter? If yes, where
is a draft/strawman proposal?
We have an early
On Mon, Dec 12, 2011 at 7:08 PM, Jarred Nicholls jar...@sencha.com wrote:
There's no feeding (re: streaming) of data to a parser, it's buffered until
the state is DONE (readyState == 4) and then an XML doc is created upon the
first access to responseXML or response. Same will go for the JSON
On 2011-12-12 17:57, Boris Zbarsky wrote:
On 12/12/11 6:07 AM, Lachlan Hunt wrote:
Given a selector list as input to the method, trim whitespace and then
for each complex selector, run the first step that applies:
(Note: if the selector list is , then there are 0 complex selectors in
the list
Hi Dan,
WebApps already has a relatively large number of specs in progress (see
[PubStatus]) and the group has agreed to add some additional specs (see
[CharterChanges]). As such, please provide a relatively specific
proposal about the features/specs you and other proponents would like to
As IanF mentioned before, Google would like to add a Quota API to
WebApps' charter and Kinuko has now provided a link to a document that
provides some details about this API:
http://wiki.whatwg.org/wiki/Quota
As such, this is a Call for Consensus to add this API to WebApps'
charter (see
Subject corrected ...
On 12/13/11 7:22 AM, Arthur Barstow wrote:
As IanF mentioned before, Google would like to add a Quota API to
WebApps' charter and Kinuko has now provided a link to a document that
provides some details about this API:
http://wiki.whatwg.org/wiki/Quota
As such, this
Thanks for the info, Art. To be clear, I personally am *NOT* proposing adding
any specs to WebApps, although others might. My email below as a Chair of the
group is merely to inform people of this work and ask for feedback.
I expect that your information will be useful for others who might
Following the recent blog post
http://updates.html5rocks.com/2011/12/Transferable-Objects-Lightning-Fastand
subsequent Twitter discussion regarding changes to the parameter list
of:
Worker.prototype.postMessage( message [, transfer ] ) [1]
DedicatedWorkerGlobalScope void
Hi All,
The Widgets DigSig spec [W-DigSig] has been sitting in PR for over 4
months now, blocked on the Elliptic Curve PAG [ECC-PAG]. AFAICT, this
PAG has just started its unspecified length Fishing Expedition seeking
some unspecified level of funds to pay for some type of analysis that
will
A Candidate Recommendation of the Widget Interface spec was published today:
http://www.w3.org/TR/2011/CR-widgets-apis-20111213/
If you have any implementation feedback, please send it to the
public-webapps mail list.
We at Google believe that a scripting-only (Javascript) subset of the API
defined in the Speech XG Incubator Group Final Report [1] is of appropriate
scope for consideration by the WebApps WG.
A scripting-only subset supports the majority of the use-cases and samples
in the XG proposal.
On Tue, Dec 13, 2011 at 2:11 PM, Dmitry Lomov dslo...@chromium.org wrote:
Hi Rick,
here are some clarifications.
There were many (long!) discussions on public-webapps about the new
signature for postMessage:
http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html
Hi Rick,
here are some clarifications.
There were many (long!) discussions on public-webapps about the new
signature for postMessage:
http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html
http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/0304.html
(resending to list - Rick, sorry if you get this twice)
On Tue, Dec 13, 2011 at 11:59 AM, Rick Waldron waldron.r...@gmail.com
wrote:
On Tue, Dec 13, 2011 at 2:11 PM, Dmitry Lomov dslo...@chromium.org
wrote:
window.webkitPostMessage(msg, transferables) does not really exist (it is
an
On Tue, Dec 13, 2011 at 11:24 AM, Rick Waldron waldron.r...@gmail.comwrote:
I'm unable to find documentation or discussion that would clarify the
rationale of over-using and over-loading the postMessage Identifier;
It's not strange that there are differences between methods on completely
On 12/13/11 11:11 AM, Dmitry Lomov wrote:
worker.postMessage({p:port, ab:arrayBuffer}, [post, arrayBuffer])
work. Therefore this extension to postMessage semantics is both
backwards-compatible and consistent. On the receiving side, the
'ports' property of event object will still contain
Dmitry,
Thanks for taking the time to provide these references and resources
Rick
On Tue, Dec 13, 2011 at 12:30 PM, Charles Pritchard ch...@jumis.com wrote:
On 12/13/11 11:11 AM, Dmitry Lomov wrote:
worker.postMessage({p:port, ab:arrayBuffer}, [post, arrayBuffer])
work. Therefore this extension to postMessage semantics is both
backwards-compatible and consistent. On the
On Tue, Dec 13, 2011 at 3:30 PM, Charles Pritchard ch...@jumis.com wrote:
On 12/13/11 11:11 AM, Dmitry Lomov wrote:
worker.postMessage({p:port, ab:arrayBuffer}, [post, arrayBuffer])
work. Therefore this extension to postMessage semantics is both
backwards-compatible and consistent. On the
On Tue, 2011-12-13 at 13:14 -0500, Arthur Barstow wrote:
Hi All,
The Widgets DigSig spec [W-DigSig] has been sitting in PR for over 4
months now, blocked on the Elliptic Curve PAG [ECC-PAG]. AFAICT, this
PAG has just started its unspecified length Fishing Expedition seeking
some
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15094
Ian 'Hixie' Hickson i...@hixie.ch changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15141
Ian 'Hixie' Hickson i...@hixie.ch changed:
What|Removed |Added
Status|NEW |RESOLVED
Following the discussion we had at TPAC [1], we have uploaded our draft as
an editor's draft to Mercurial:
http://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm
This is just a starting point for discussion and we're looking forward to
incorporating feedback as we move forward. We know
The current spec defines the Blob Protocol Version [1]. Our current
implementation
doesn't require a protocol version and the way protocol handlers are defined in
Internet Explorer does require this. I don't know if this is ever exposed in
the web platform. The spec says that this should be
The current spec requires the opaque string in Blob URLs to be at least
36 characters in length [1]. Our implementation doesn't currently use a
UUID and the length of the string is shorter than 36 characters. While
I have no problem with the recommendation to use UUIDs in the spec,
since it isn't
Another topic that came up at TPAC was readAsBinaryString [1]. This method
predates support for typed arrays in the FileAPI and allows binary data
to be read and stored in a string. This is an inefficient way to store
data now that we have ArrayBuffer and we'd like to not support this method.
At
Seems quite reasonable to me. We've got data URL strings for people who need
inefficiency (or portable strings).
On Dec 13, 2011, at 4:52 PM, Adrian Bateman adria...@microsoft.com wrote:
Another topic that came up at TPAC was readAsBinaryString [1]. This method
predates support for typed
At TPAC [1,2] I described our proposal for adding an isReusable flag to
createObjectURL. A common pattern we have seen is the need for a blob URL
for a single use (for example, loading into an img element) and then
revoking the URL. This requires a fair amount of boilerplate code to
handle the
+1 though it won't likely go away from implementations as easily.
On Dec 13, 2011, at 8:22 PM, Charles Pritchard ch...@jumis.com wrote:
Seems quite reasonable to me. We've got data URL strings for people who need
inefficiency (or portable strings).
On Dec 13, 2011, at 4:52 PM, Adrian
I've seen the same pattern, though mysteriously, running a revoke in the same
loop still allows the image to be loaded. I may have made a mistake in reading
those source files or it may be a special quirk in the order of event loading.
However this is approached, I think it should have firm
This proposal looks really good and matches my expectations.
Yehuda Katz
(ph) 718.877.1325
On Tue, Dec 13, 2011 at 3:53 AM, Lachlan Hunt lachlan.h...@lachy.id.auwrote:
On 2011-12-12 17:57, Boris Zbarsky wrote:
On 12/12/11 6:07 AM, Lachlan Hunt wrote:
Given a selector list as input to the
On Wed, 14 Dec 2011 01:52:04 +0100, Adrian Bateman
adria...@microsoft.com wrote:
At TPAC [1,2] I described our proposal for adding an isReusable flag to
createObjectURL. A common pattern we have seen is the need for a blob URL
for a single use (for example, loading into an img element) and
John Jensen here at Mozilla has been doing some web crawling trying to
find what barewords are used in on* attributes.
What I have so far as a result is a list of about 1.7 million barewords
used across several tens of thousands of pages. If people are
interested in the exact methodology, I
34 matches
Mail list logo
