Hi Vincent,
I have by no means reviewed the entire spec, but while reviewing the
test cases, I noticed some room for improvement. Comments below.
In the 4. pointerlockchange and pointerlockerror Events section [1]:
… with its |bubble| attribute set …
should be |bubbles|. Probably best to
Hi,
I have subscribed to this list because my colleague Gabor (CC) and I
found a few issues with Content Security Policies applied to HTML imports.
The current draft
(http://w3c.github.io/webcomponents/spec/imports/#imports-and-csp, Jan
9) suggests that import loading is restricted through a
On Thu, Jan 9, 2014 at 5:17 AM, Arthur Barstow art.bars...@nokia.comwrote:
Hi Dimitri All,
FYI, yesterday I moved all of the Web Components specs in PubStatus to its
own table [PubStatus-WC] to help address the so, what is the status of Web
Components standardization in WebApps use case (as
On Wed, Jan 8, 2014 at 8:17 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 1/6/14 8:52 PM, Goktug Gokdogan wrote:
function MyCustomElement() {};
MyCustomElement.prototype = Object.create(HTMLElement.prototype);
document.appendChild(new MyCustomElement());
If this were actually
On 1/9/14 8:39 PM, Goktug Gokdogan wrote:
Is it really part of the plans (i.e. making HTMLElement constructible)?
Ideally, yes. The main problem with making HTMLElement constructible is
this: What tag name should it use when it constructs? If it were not
for that, it would already be
On Thu, Jan 9, 2014 at 5:41 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 1/9/14 8:39 PM, Goktug Gokdogan wrote:
Is it really part of the plans (i.e. making HTMLElement constructible)?
Ideally, yes. The main problem with making HTMLElement constructible is
this: What tag name should it use
On 1/9/14 8:50 PM, Goktug Gokdogan wrote:
Can't it be passed by constructor call?
Possibly, yes. The spec was in flux for a while, but looks like
@@create does in fact get passed the constructor arguments, so it can
create different objects based on those.
-Boris
Hi Frederik,
Thanks for bringing it up!
As you pointed out, CSP of imported documents essentially extends the
set of allowed domains. I thought I was useful for component authors to
specify their own domains, like one of their own CDN.
I'm not sure how it is threatening because components won't
Jonas, William, Ted, and I had some discussion about this last month. (Sorry
for the delayed response).
On Dec 5, 2013, at 10:58 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 12/6/13 1:49 AM, Ryosuke Niwa wrote:
Then how do we define a custom element using ES6 classes? Are we going to
not
On 1/9/14 10:57 PM, Ryosuke Niwa wrote:
Given that, we could maybe cheat and in fact do some sort of delayed calling of the
constructor of ES6 subclasses of elements. You'd still be able to observe these objects
in an unconstructed state from the subclass pov, but at least it wouldn't be
a
On Thu, Jan 9, 2014 at 9:27 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 1/9/14 10:57 PM, Ryosuke Niwa wrote:
Given that, we could maybe cheat and in fact do some sort of delayed
calling of the constructor of ES6 subclasses of elements. You'd still be
able to observe these objects in an
11 matches
Mail list logo
