On Thu, May 22, 2014 at 1:29 AM, Anne van Kesteren ann...@annevk.nl wrote:
For blob URLs (and prolly filesystem and indexeddb) we put the origin
in the URL and define a way to extract it again so new
URL(blob).origin does the right thing.
Yup.
For fetching blob URLs (and prolly filesystem
On Thu, May 22, 2014 at 1:29 AM, Anne van Kesteren ann...@annevk.nl wrote:
How do we deal with data URLs? Obviously you can always get a resource
out of them. But when should the response of fetching one be tainted
and when should it not be? And there's a somewhat similar question for
about
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24288
Hayato Ito hay...@chromium.org changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24316
Hayato Ito hay...@chromium.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25915
Bug ID: 25915
Summary: Cross-origin requests
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25914
Bug ID: 25914
Summary: No definition of parsing blob's scheme data
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity:
Yes, Tab, your below summary is correct.
First, let me (again) stress the fact that my intention is NOT to give a
critical judgment on Web Components.
Many ways lead to Rome. Web Components is one way of implementing discrete components into a web page. And the HTML
IFRAME element is just
The plan is to implement and ship this fairly soon, so I figured I'd
ask for review now, while we're still drafting the text:
http://fetch.spec.whatwg.org/#fetch-api
In particular I'd like feedback on the design of Request and Response
classes, and the fetch() method.
--
http://fetch.spec.whatwg.org/#dom-request
Add steps to set client and context?
http://fetch.spec.whatwg.org/#cors-preflight-fetch-0
Add steps to set client and context?
http://fetch.spec.whatwg.org/#concept-legacy-fetch
http://fetch.spec.whatwg.org/#concept-legacy-potentially-cors-enabled-fetch
On May 29, 2014 at 9:02:35 AM, Anne van Kesteren (ann...@annevk.nl) wrote:
The plan is to implement and ship this fairly soon, so I figured I'd
ask for review now, while we're still drafting the text:
http://fetch.spec.whatwg.org/#fetch-api
In particular I'd like feedback on the
On Thu, May 29, 2014 at 4:58 PM, Marcos mar...@marcosc.com wrote:
enum RequestMode { same-origin, tainted cross-origin, CORS,
CORS-with-forced-preflight };
I think these are badly named (even though they use the names used in HTML
and Fetch). It's going to be annoying to type these out for
On Thu, May 29, 2014 at 9:06 AM, Jonas Sicking jo...@sicking.cc wrote:
My proposal is something like this:
Thanks!
* Add a new flag to the fetch algorithm allow inheriting origin
same-origin data URL flag? Ideally we don't do another data URL mistake.
* The default for this new flag is
Excuse my unsolicited comment here, being new to the webapps mailing list,
but here is my two cents feedback as a web developer...
I think the idea behind Web Components is good regardless of the flaws on
the spec. The idea is to create a standard built into the browser that will
allow
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25916
Bug ID: 25916
Summary: [Explainer]: Custom pseudo elements are still used in
the examples.
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
On Thu, May 29, 2014 at 8:10 AM, Tobie Langel tobie.lan...@gmail.com wrote:
On Thu, May 29, 2014 at 4:58 PM, Marcos mar...@marcosc.com wrote:
enum RequestMode { same-origin, tainted cross-origin, CORS,
CORS-with-forced-preflight };
I think these are badly named (even though they use the
Without default text input, the current proposal for
contentEditable=minimal is essentially just enabling cursors (drawing
them, dispatching events, performing default actions). Rather than calling
the mode minimal, which is ill-defined, why not explicitly call it what
it is: cursor-only? Or,
On Thu, May 29, 2014 at 9:21 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, May 29, 2014 at 9:06 AM, Jonas Sicking jo...@sicking.cc wrote:
* The default for this new flag is false
* If the flag is set to false, the origin of the URL is a unique identifier.
* When the origin is a unique
17 matches
Mail list logo
