On Wed, Jan 26, 2011 at 10:23 PM, Brett Zamir wrote:
> For example, we want the designer guy to be able to freely change the colors
> in the stylesheet for indicating say a successful transition (green), an
> error (red), or waiting (yellow) for an Ajax request. The JavaScript girl
> does not want
On 1/27/2011 11:21 AM, Tab Atkins Jr. wrote:
On Wed, Jan 26, 2011 at 6:47 PM, Brett Zamir wrote:
While it can already be done dynamically by iterating through
document.stylesheets, in order to allow full separation of presentation from
content in a convenient way and foster best practices, I th
On Wed, Jan 26, 2011 at 6:47 PM, Brett Zamir wrote:
> While it can already be done dynamically by iterating through
> document.stylesheets, in order to allow full separation of presentation from
> content in a convenient way and foster best practices, I think it would be
> helpful to have a built-
While it can already be done dynamically by iterating through
document.stylesheets, in order to allow full separation of presentation
from content in a convenient way and foster best practices, I think it
would be helpful to have a built-in method to obtain a CSS property for
a given selector.
I was alluding to a simple robots.txt like solution with the static
'allow' file, but it seems like CORS could work too, it is more
burdensome to setup due to the additional HTTP headers.
GET /some-resource
Origin: https://acme.com
HTTP/1.x 200 OK
Access-Control-Allow-Origin: * | https://acme.com
On Wed, 08 Dec 2010 00:48:42 +0100, Ian Hickson wrote:
[...]
I finally updated XMLHttpRequest to make use of your changes. Thanks!
(I.e. it no longer mentions cookie-free as that is implied and it now
defines the origin of Document objects.)
http://dev.w3.org/2006/webapi/XMLHttpRequest-2
Hi,
I was noticing how you were suggesting to change
addRemoteConfiguration to setRemoteConfiguration as it appears as a
single-point-to-single-point connection, is this part of the current
specification or could single-point-to-multiple-points connections (or
"clouds") be implemented using the sam
On Tue, 25 Jan 2011 19:05:32 +0100, David Flanagan
wrote:
I don't see the point of that, if all it does is save one call to
URL.createObjectURL() (and also one call to revokeObjectURL())?
The point is that authors will not have to do any cleanup. Objects get
cleaned up automatically. So be
Oh, thanks!
Your question is a good one. We're looking into precisely that, and expect to
learn more in our continued implementation work.
We're also participating in the discussion on these matters in RTC-Web
[http://rtc-web.alvestrand.com/].
-- Patrik
-Original Message-
From: Anne
On Wed, 26 Jan 2011 10:34:11 +0100, Anne van Kesteren
wrote:
Could you elaborate more on the details of the protocol?
Handshake/framing/etc. Is it something that can be independently
implemented? Agreement on that is what is holding back this API at the
moment.
Oh, and also, extremely aw
On Wed, 26 Jan 2011 10:04:22 +0100, Patrik Persson J
wrote:
We have done some experimentation with the ConnectionPeer API. We have
an initial implementation of a subset of the API, using ICE (RFC 5245)
for the peer-to-peer handshaking. Our implementation is
WebKit/GTK+/gstreamer-based, and we
We have done some experimentation with the ConnectionPeer API. We have
an initial implementation of a subset of the API, using ICE (RFC 5245)
for the peer-to-peer handshaking. Our implementation is
WebKit/GTK+/gstreamer-based, and we of course intend to submit it to
WebKit, but the implementation
On Tue, 25 Jan 2011 23:37:55 +0100, Michael Nordman
wrote:
Would the public-webapps list be better for discussing appcache
feature requests?
It's not a feature drafted in any of the WebApps WG specifications. If you
want to discuss at the W3C the appropriate place would be the HTML WG.
Al
13 matches
Mail list logo