Hi Dimitri,
made quite a few tweaks to the custom element semantics section after
feedback.
Appreciate a review of the PR https://github.com/w3c/webcomponents/pull/31
when you get a chance.
--
Regards
SteveF
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27762
Bug ID: 27762
Summary: [Custom]: what happens with Unresolved Elements when
removed from the tree?
Product: WebAppsWG
Version: unspecified
Hardware: All
It's not clear to me from
https://w3c.github.io/webcomponents/spec/custom/#es6 how the upgrade
works. From the pre-ES6 setup you can work out through inference that
upgrading is supposed to mutate the prototype of the element in
question.
But it seems that mutating the prototype is not sufficient
On Tue, Jan 6, 2015 at 10:38 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Jan 6, 2015 at 7:06 PM, Dimitri Glazkov dglaz...@google.com
wrote:
Yes to the first question. I wasn't planning on doing anything different
there.
It seems simple prototype munging but not actually changing
On Tue, Jan 6, 2015 at 10:59 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Jan 6, 2015 at 7:54 PM, Dimitri Glazkov dglaz...@google.com
wrote:
Right, that's why to create a valid custom element that subclasses
HTMLInputElement, you should use type extensions. With type extensions,
On Nov 7, 2014, at 12:25 PM, Ryosuke Niwa rn...@apple.com wrote:
On Nov 5, 2014, at 7:54 AM, cha...@yandex-team.ru wrote:
we have had a (northern) spring meeting in California for the last few
years, co-located with HTML.
The HTML group is considering having a meeting in may(ish) 2015 in
On Tue, Jan 6, 2015 at 7:54 PM, Dimitri Glazkov dglaz...@google.com wrote:
Right, that's why to create a valid custom element that subclasses
HTMLInputElement, you should use type extensions. With type extensions, the
HTMLInputElement is what's instantiated.
But without using type extensions
https://github.com/w3c/selection-api/issues/40
Trident (since IE10) and Gecko both return a live Range, which can be modified
to update selection. WebKit and Blink both return a clone Range so that any
changes to the Range doesn't update the selection.
It appears that there is a moderate
On Tue, Jan 6, 2015 at 5:44 PM, Olli Pettay o...@pettay.fi wrote:
On 01/07/2015 12:32 AM, Ryosuke Niwa wrote:
https://github.com/w3c/selection-api/issues/40
Trident (since IE10) and Gecko both return a live Range, which can be
modified to update selection. WebKit and Blink both return a
For what it's worth as a user of the range and selection APIs, updating a
live range is convenient and preferable, but since this has never worked in
all browsers, I never do it and have never recommended it to anyone else.
Therefore if Gecko changes, nothing really changes for me, so I don't
Cross-posting as is now usual ...
What: IndieUI Task Force Teleconference
When: Wednesday 7 January
2:00 PMSan Francisco -- U.S. Pacific Time (PST: UTC -8)
4:00 PMAustin -- U.S. Central Time(CST: UTC -6)
5:00 PMBoston --
I'm not sure if any sites depend on the Gecko/Trident behavior, but I imagine
any such sites also work in Webkit/Blink. So I'm fine with changing this unless
anyone knows of an important dependency.
-Original Message-
From: Ryosuke Niwa [mailto:rn...@apple.com]
Sent: Tuesday, January
On 01/07/2015 12:32 AM, Ryosuke Niwa wrote:
https://github.com/w3c/selection-api/issues/40
Trident (since IE10) and Gecko both return a live Range, which can be modified
to update selection. WebKit and Blink both return a clone Range so that any
changes to the Range doesn't update the
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27775
Bug ID: 27775
Summary: [Shadow]: Define the behavior of *closed* shadow
trees.
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27544
Philippe Le Hegaret p...@w3.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
This is all intimately tied to the still-ongoing how-to-subclass-builtins
discussion that is unfortunately happening on a private TC39 thread. The
essential idea, however, is that as long as you do
```js
class MyInputElement extends HTMLInputElement {
constructor() {
super(); // this is
Thanks! Merged.
:DG
On Tue, Jan 6, 2015 at 1:46 AM, Steve Faulkner faulkner.st...@gmail.com
wrote:
Hi Dimitri,
made quite a few tweaks to the custom element semantics section after
feedback.
Appreciate a review of the PR https://github.com/w3c/webcomponents/pull/31
when you get a
On Tue, Jan 6, 2015 at 6:13 PM, Dimitri Glazkov dglaz...@google.com wrote:
That section needs to be updated, because the ES6 spec had shifted a little
bit with regard to @@create. Filed
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27769.
Yeah, there's issues in general there, such as ES6
On Tue, Jan 6, 2015 at 9:56 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Jan 6, 2015 at 6:13 PM, Dimitri Glazkov dglaz...@google.com
wrote:
That section needs to be updated, because the ES6 spec had shifted a
little
bit with regard to @@create. Filed
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27769
Bug ID: 27769
Summary: [Custom]: ES6 section needs to be updated
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity:
That section needs to be updated, because the ES6 spec had shifted a little
bit with regard to @@create. Filed
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27769.
Conceptually, when I wrote it I'd imagined that the constructor will be
called only when you explicitly invoke it (new
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27768
Bug ID: 27768
Summary: [Custom]: Parsing Custom Elements
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27770
Bug ID: 27770
Summary: [Custom]: Improve the wording in element upgrade
algorithm
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
On Tue, Jan 6, 2015 at 7:06 PM, Dimitri Glazkov dglaz...@google.com wrote:
Yes to the first question. I wasn't planning on doing anything different
there.
It seems simple prototype munging but not actually changing identity
will fail for all but the basic cases of subclassing. E.g. if I
24 matches
Mail list logo
