Hi Marcin,
On Oct 5, 2009, at 12:12 , Marcin Hanclik wrote:
The mode in VMMF could be added, are we going to change PC as well?
The all value from PC is a catch-all value.
I'd rather avoid changing P+C unless we need to — VMMF should be the
superseding document on this topic.
--
Robin
Hi Robin,
OK.
E.g. all is currently not in VMMF, I am adding it now.
What do you mean by superseding in this context?
Shall we assume that VMMF will change (invalidate or possibly only add) PC in
this matter?
Thanks,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 |
The problem is finding the right amount of flexibility without making it
too complicated or opening unwanted security holes.
The beauty of the system proposed by the WAF group way back is that it
seems to achieve this in that:
example.com - matches all URIs on example.com
Marcos, All,
During the processing of content in Step 7, if the custom start
file is bogus (and the spec indicates a few reasons why it could be
bogus), widget start file will be null when the UA completes Step
7. In this case, we presumably want the UA to run all of Step 8, in
When scanning the Test Suite Version of the PC spec I noticed some
MAY and OPTIONAL assertions for which there are no associated test
assertions. This implies these assertions aren't really necessary
and should be removed or made non-Normative (e.g. hints to an
implementor).
Section 2:
Hi All,
A couple of comment to the Widgets 1.0: View Modes Media Feature document [1]
1)
all value
What about the behavior of UA in case all is specified in CSS?
Does it mean that the UA must pick any other view-mode and set it or does it
mean that we do not care about the combination of the
I updated CORS over the past few days:
http://dev.w3.org/2006/waf/access-control/
Summary:
* Redirects only work for simple requests
* Origin header semantics are left to the draft that defines the Origin
header, apart from the requirement as to what the initial origin should be.
*
On Oct 5, 2009, at 11:31 AM, ext Anne van Kesteren wrote:
I updated CORS over the past few days:
http://dev.w3.org/2006/waf/access-control/
I suggest we try to resolve the remaining open issues in the issue
tracker
during the F2F.
In case someone doesn't know about WebApps' issue
On Fri, Sep 18, 2009 at 8:37 AM, Per-Erik Brodin
per-erik.bro...@ericsson.com wrote:
We recently landed an implementation of server-sent events in WebKit
(see http://trac.webkit.org/changeset/47323).
As an implementor of the specification, I would like to share my
thoughts on a couple of
