On Apr 27, 2015, at 7:32 PM, Steve Orvell sorv...@google.com wrote:
Perhaps we need to make childrenChanged optionally get called when
attributes of child nodes are changed just like the way you can configure
mutation observers to optionally monitor attribute changes.
Wow, let me
On Apr 27, 2015, at 12:25 AM, Justin Fagnani justinfagn...@google.com wrote:
On Sun, Apr 26, 2015 at 11:05 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Sat, Apr 25, 2015 at 10:49 PM, Ryosuke Niwa rn...@apple.com wrote:
If we wanted to allow non-direct child descendent (e.g. grand child
On Apr 27, 2015, at 7:04 PM, Jonas Sicking jo...@sicking.cc wrote:
On Mon, Apr 27, 2015 at 1:57 AM, Glen Huang curvedm...@gmail.com wrote:
Intuitively, querySelector('.class') only needs to find the first matching
node, whereas getElementsByClassName('.class')[0] needs to find all matching
the progress
easily in one place. I'm not fan of the discussion being scattered. :)
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18429
On Sat, Apr 25, 2015 at 9:32 AM Anne van Kesteren ann...@annevk.nl wrote:
On Sat, Apr 25, 2015 at 12:17 AM, Ryosuke Niwa rn...@apple.com wrote
On Apr 25, 2015, at 9:28 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Sat, Apr 25, 2015 at 12:17 AM, Ryosuke Niwa rn...@apple.com wrote:
In today's F2F, I've got an action item to come up with a concrete workable
proposal for imperative API. I had a great chat about this afterwards
On Apr 25, 2015, at 9:28 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Sat, Apr 25, 2015 at 12:17 AM, Ryosuke Niwa rn...@apple.com wrote:
In today's F2F, I've got an action item to come up with a concrete workable
proposal for imperative API. I had a great chat about this afterwards
On Apr 25, 2015, at 1:17 PM, Olli Pettay o...@pettay.fi wrote:
On 04/25/2015 09:28 AM, Anne van Kesteren wrote:
On Sat, Apr 25, 2015 at 12:17 AM, Ryosuke Niwa rn...@apple.com wrote:
In today's F2F, I've got an action item to come up with a concrete workable
proposal for imperative API. I
Just to clarity, I obviously haven't had a time to discuss this with my
colleagues so I don't know which one (or something else entirely) we (Apple)
end up endorsing/opposing at the end.
On Apr 25, 2015, at 12:14 AM, Ryosuke Niwa rn...@apple.com wrote:
Hi all,
In today's F2F, I've got
Hi,
Could someone give me a concrete use cases for node redistributions where the
second and subsequent insertion points need to redistribute a subset of nodes
that have been redistributed to an insertion point in an earlier shadow DOM?
Maybe someone at Google working on Polymer would have
Hi all,
In today's F2F, I've got an action item to come up with a concrete workable
proposal for imperative API. I had a great chat about this afterwards with
various people who attended F2F and here's a summary. I'll continue to work
with Dimitri Erik to work out details in the coming
On Apr 24, 2015, at 2:23 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Wed, Apr 22, 2015 at 5:04 PM, Ryosuke Niwa rn...@apple.com wrote:
I find it decidedly relevant given I'm pointing out that attribute-specified
slots Domenic mentioned isn't what you described. Since the only venue
On Apr 21, 2015, at 11:08 PM, Domenic Denicola d...@domenic.me wrote:
From: Ryosuke Niwa [mailto:rn...@apple.com]
At the conceptual level, they're equivalent. However, we didn't find the
extra flexibility of using CSS selectors compelling as we mentioned in our
proposal [1
On Apr 22, 2015, at 3:48 PM, Justin Fagnani justinfagn...@google.com wrote:
On Wed, Apr 22, 2015 at 2:37 PM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
On Apr 22, 2015, at 10:16 AM, Justin Fagnani justinfagn...@google.com
mailto:justinfagn...@google.com wrote:
On Tue
On Apr 22, 2015, at 3:54 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Wed, Apr 22, 2015 at 2:53 PM, Ryosuke Niwa rn...@apple.com wrote:
On Apr 22, 2015, at 2:38 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Wed, Apr 22, 2015 at 2:29 PM, Ryosuke Niwa rn...@apple.com wrote:
On Apr
On Apr 22, 2015, at 8:52 AM, Domenic Denicola d...@domenic.me wrote:
Between content-slot-specified slots, attribute-specified slots,
element-named slots, and everything-else-slots, we're now in a weird place
where we've reinvented a micro-language with some, but not all, of the power
On Apr 22, 2015, at 2:38 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Wed, Apr 22, 2015 at 2:29 PM, Ryosuke Niwa rn...@apple.com wrote:
On Apr 22, 2015, at 8:52 AM, Domenic Denicola d...@domenic.me wrote:
Between content-slot-specified slots, attribute-specified slots,
element-named
...@google.com
mailto:justinfagn...@google.com wrote:
On Tue, Apr 21, 2015 at 10:40 PM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
On Apr 21, 2015, at 10:23 PM, Justin Fagnani justinfagn...@google.com
mailto:justinfagn...@google.com wrote:
I do want the ability
On Apr 22, 2015, at 10:16 AM, Justin Fagnani justinfagn...@google.com wrote:
On Tue, Apr 21, 2015 at 10:40 PM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
On Apr 21, 2015, at 10:23 PM, Justin Fagnani justinfagn...@google.com
mailto:justinfagn...@google.com wrote
Hi all,
Following WebApps discussion last year [1] and earlier this year [2] about
template transclusions and inheritance in shadow DOM, Jan Miksovsky at
Component Kitchen, Ted O'Connor and I (Ryosuke Niwa) at Apple had a meeting
where we came up with changes to the way shadow DOM distributes
On Apr 21, 2015, at 10:17 PM, Brian Kardell bkard...@gmail.com wrote:
On Apr 21, 2015 8:22 PM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
Hi all,
Following WebApps discussion last year [1] and earlier this year [2] about
template transclusions and inheritance
/template
Here, the content elements are both creating slots and fulfilling slots.
- R. Niwa
On Tue, Apr 21, 2015 at 8:19 PM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
Hi all,
Following WebApps discussion last year [1] and earlier this year [2] about
template
On Apr 21, 2015, at 10:23 PM, Justin Fagnani justinfagn...@google.com wrote:
I do want the ability to redirect distributed nodes into a holes in the base
template, so that part is welcome to me. However, my first reaction to the
slot idea is that forcing users to add the content-slot
On Mar 26, 2015, at 10:53 AM, Travis Leithead travis.leith...@microsoft.com
wrote:
Today’s ShadowDOM model is designed around only adding shadow roots to
element in the ‘light side’. I assume this is intentional, but was hoping
someone could describe why this design was chosen? Or said
On Mar 26, 2015, at 1:23 PM, Travis Leithead travis.leith...@microsoft.com
wrote:
You make a series of excellent points.
In the sense that you have a new set of nodes to manage holistically, then
having some sort of “document” container does makes sense for that (a
ShadowRoot) in
On Mar 16, 2015, at 3:14 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
[Sorry for the reply-chain breaking; Gmail is being super weird about
your message in particular, and won't let me reply directly to it.
Some bug.]
Karl Dubost said:
The intersection seems to be:
['a', 'style',
On Mar 18, 2015, at 2:19 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Wed, Mar 18, 2015 at 2:06 PM, Ryosuke Niwa rn...@apple.com wrote:
On Mar 16, 2015, at 3:14 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
Karl Dubost said:
The intersection seems to be:
['a', 'style', 'script
On Mar 12, 2015, at 5:46 PM, Travis Leithead travis.leith...@microsoft.com
wrote:
Has the idea of loading/parsing a Shadow DOM directly from a URL been
discussed already? (e.g., a sort-of “micro-import” or an import that parses
its document directly into the ShadowRoot container?)
On Feb 23, 2015, at 6:42 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 2/23/15 4:27 AM, Anne van Kesteren wrote:
1) If we run the constructor synchronously, even during cloning. If
the constructor did something unexpected, is that actually
problematic? It is not immediately clear to me
On Feb 12, 2015, at 4:50 AM, Steve Faulkner faulkner.st...@gmail.com wrote:
On 12 February 2015 at 10:58, Anne van Kesteren ann...@annevk.nl
mailto:ann...@annevk.nl wrote:
which is a very different problem from what you want to solve, no?
The problem I think needs solving for minimum
One more thing. I think it's nice to have a new comprehensive list of use cases
participants have come up over the years on the same document since the wiki
page is quite outdated.
- R. Niwa
On Feb 8, 2015, at 10:14 AM, Ryosuke Niwa rn...@apple.com wrote:
Hi Dimitri,
Thanks for writing
Hi Dimitri,
Thanks for writing up that page. I think it's valuable to have some
documentation like this since the discussion has been scatters across many
threads and a long time span.
Another point of contention appears to be how show isolation is done
particularly in the world where we've
On Feb 6, 2015, at 9:27 AM, Michaela Merz michaela.m...@hermetos.com wrote:
Well .. may be some folks should take a deep breath and think what they are
doing. I am 'just' coding web services and too often I find myself asking:
Why did the guys think that this would make sense? Indexeddb
On Feb 5, 2015, at 9:41 AM, Dimitri Glazkov dglaz...@google.com wrote:
On Thu, Feb 5, 2015 at 5:46 AM, Olli Pettay o...@pettay.fi
mailto:o...@pettay.fi wrote:
On 02/05/2015 02:24 AM, Dimitri Glazkov wrote:
However, I would like to first understand if that is the problem that the
group
On Feb 5, 2015, at 3:51 PM, Dimitri Glazkov dglaz...@google.com wrote:
On Thu, Feb 5, 2015 at 2:53 PM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
On Feb 5, 2015, at 9:41 AM, Dimitri Glazkov dglaz...@google.com
mailto:dglaz...@google.com wrote:
On Thu, Feb 5, 2015
On Feb 4, 2015, at 4:56 AM, Olli Pettay o...@pettay.fi wrote:
On 02/03/2015 04:22 PM, Brian Kardell wrote:
On Tue, Feb 3, 2015 at 8:06 AM, Olli Pettay o...@pettay.fi
mailto:o...@pettay.fi wrote:
On 02/02/2015 09:22 PM, Dimitri Glazkov wrote:
Brian recently posted what
On Feb 4, 2015, at 7:59 AM, Domenic Denicola d...@domenic.me wrote:
In IRC Anne and I were briefly discussing how type= is the is= of Web
Applications 1.0. That is, input type=date is similar to img is=x-gif
or similar---it has a reasonable fallback behavior, but in reality it is a
See https://lists.w3.org/Archives/Public/public-webapps/2015JanMar/0435.html
https://lists.w3.org/Archives/Public/public-webapps/2015JanMar/0435.html
first.
On Feb 4, 2015, at 6:43 AM, Chris Bateman chrisb...@gmail.com wrote:
Assuming a situation where a native element – with custom
On Feb 4, 2015, at 11:26 AM, Alice Boxhall aboxh...@google.com wrote:
So a web page author would write
x-slider min=-100 ... etc.
and then the custom element would sprout an input type=range ...etc with
the attribute values copied across?
No. The page author would write x-sliderinput
On Feb 4, 2015, at 10:54 AM, Alice Boxhall aboxh...@google.com wrote:
On Wed, Feb 4, 2015 at 10:36 AM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
On Feb 4, 2015, at 10:12 AM, Brian Kardell bkard...@gmail.com
mailto:bkard...@gmail.com wrote:
On Wed, Feb 4, 2015 at 12
On Feb 4, 2015, at 11:11 AM, Chris Bateman chrisb...@gmail.com wrote:
Ugh, I forgot about that. Without subclassing - terseness is a very minor
drawback, but remapping the interface is a big pain.
Could you give us a concrete use case in which remapping the interface is
necessary or
On Feb 4, 2015, at 9:05 AM, Steve Faulkner faulkner.st...@gmail.com wrote:
On 4 February 2015 at 16:51, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
my-custom-formatterinput/my-custom-formatter
I think if this worked. i.e. hid the styling and allowed styling over top
, 2015 at 10:36 AM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
On Feb 4, 2015, at 10:12 AM, Brian Kardell bkard...@gmail.com
mailto:bkard...@gmail.com wrote:
On Wed, Feb 4, 2015 at 12:41 PM, Chris Bateman chrisb...@gmail.com
mailto:chrisb...@gmail.com wrote:
Yeah, I had
On Feb 4, 2015, at 3:20 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Wed, Feb 4, 2015 at 11:56 PM, Olli Pettay o...@pettay.fi wrote:
Why do we need shadow DOM (or something similar) at all if we expose it
easily to the outside world.
One could even now just require that elements in
On Feb 3, 2015, at 7:13 AM, Chris Bateman chrisb...@gmail.com wrote:
Why don't we just make all input elements support these new attributes we're
adding?
In my opinion, I'd say because you can't possibly cover every case - what
about doing the same kind of formatting for social
On Jan 31, 2015, at 10:40 AM, Chris Bateman chrisb...@gmail.com wrote:
The -webkit-appreance CSS is definitely another issue, so here's an example
with just JS behavior:
input is=number-input decimals=2
This component would only allow numeric input, and insert decimals, commas,
etc.
On Jan 30, 2015, at 10:22 AM, Alice Boxhall aboxh...@google.com wrote:
On Fri, Jan 30, 2015 at 8:46 AM, Anne van Kesteren ann...@annevk.nl
mailto:ann...@annevk.nl wrote:
On Fri, Jan 30, 2015 at 11:05 AM, Steve Faulkner
faulkner.st...@gmail.com mailto:faulkner.st...@gmail.com wrote:
In
On Jan 29, 2015, at 7:52 AM, Steve Faulkner faulkner.st...@gmail.com wrote:
On 29 January 2015 at 15:37, Anne van Kesteren ann...@annevk.nl
mailto:ann...@annevk.nl wrote:
I don't have enough technical understanding to know what is viable or not,
you and others are saying that the current
On Jan 16, 2015, at 4:07 PM, Dimitri Glazkov dglaz...@google.com wrote:
On Fri, Jan 16, 2015 at 1:14 PM, Ryosuke Niwa rn...@apple.com wrote:
On Jan 15, 2015, at 7:25 PM, Dimitri Glazkov dglaz...@google.com wrote:
On Thu, Jan 15, 2015 at 6:43 PM, Ryosuke Niwa rn...@apple.com wrote:
When
On Jan 16, 2015, at 9:58 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Fri, Jan 16, 2015 at 2:29 AM, Ryosuke Niwa rn...@apple.com wrote:
And I'm suggesting to do the same (picking the simplest design) in HTML
custom elements by only supporting synchronous definition of elements
On Jan 15, 2015, at 7:25 PM, Dimitri Glazkov dglaz...@google.com wrote:
On Thu, Jan 15, 2015 at 6:43 PM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
When an author imports a ES6 module, we don't create a fake object which gets
resolved later by rewriting its prototype
On Jan 15, 2015, at 11:28 AM, Domenic Denicola d...@domenic.me wrote:
From: Dimitri Glazkov [mailto:dglaz...@google.com]
Why is Not having identity at creation-time is currently a mismatch with
the rest of the platform a problem? Why does it all have to be consistent
across the board?
On Jan 15, 2015, at 3:17 PM, Domenic Denicola d...@domenic.me wrote:
From: Ryosuke Niwa [mailto:rn...@apple.com]
If ES6 classes' constructor doesn't fundamentally work with custom elements,
then why don't we change the design of ES6 classes.
We would essentially be saying
On Jan 14, 2015, at 12:52 PM, Dimitri Glazkov dglaz...@google.com wrote:
FWIW, I think that element upgrade is sort of fundamental to the usefulness
of custom elements. In a world where most scripts are non-blocking (that's
hopefully the modern world we should aim for), I'll effectively
On Jan 15, 2015, at 11:47 AM, Brian Kardell bkard...@gmail.com wrote:
Not to sidetrack the discussion but Steve Faulker made what I think was a
valid observation and I haven't seen a response... Did I miss it?
When and in which thread? Could you give us a pointer?
- R. Niwa
On Jan 14, 2015, at 12:25 PM, Domenic Denicola d...@domenic.me wrote:
From: Ryosuke Niwa [mailto:rn...@apple.com]
Let me restate the problem using an example. Suppose we're parsing
my-element/my-elementmy-other-element/my-other-element.
Once the HTML is parsed, the DOM tree
On Jan 14, 2015, at 10:41 AM, Domenic Denicola d...@domenic.me wrote:
From: Ryosuke Niwa [mailto:rn...@apple.com]
See Boris' responses in another thread [1] and [2]. Jonas outlined how this
could work in the same thread [3]
Thanks for the references. But avoiding this problem
On Jan 14, 2015, at 6:45 AM, Anne van Kesteren ann...@annevk.nl wrote:
I've been trying to think of the smallest setup that adds value, can
get broad agreement, and is therefore hopefully interoperable fast.
* ES6-style class syntax to declare the imperative constructor.
* No subclassing
On Jan 14, 2015, at 9:50 AM, Domenic Denicola d...@domenic.me wrote:
From: Anne van Kesteren [mailto:ann...@annevk.nl]
Could you explain how this works in more detail?
I haven't checked, but my impression was we could just use the same
processing model the current spec uses for
On Jan 13, 2015, at 11:43 AM, Domenic Denicola d...@domenic.me wrote:
I imagine this has all been discussed before, but why do __proto__-munging
when adopting cross document? That seems bizarre, and causes exactly these
problems. When you put an object in a Map from another realm, it
On Jan 13, 2015, at 10:22 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 1/13/15 1:18 PM, Ryosuke Niwa wrote:
I agree. It's unusual for a constructor of a super class to automatically
instantiate an arbitrary subclass based on its arguments. And we usually
solve that convenience problem
On Jan 13, 2015, at 4:21 AM, Arthur Barstow art.bars...@gmail.com wrote:
On 1/13/15 6:54 AM, cha...@yandex-team.ru wrote:
13.01.2015, 05:31, Boris Zbarsky bzbar...@mit.edu:
On 1/12/15 1:56 PM, Olivier Forget wrote:
Unfortunately
multiple range selections are not a nice to have. All
On Jan 13, 2015, at 9:25 AM, Domenic Denicola d...@domenic.me wrote:
From: Boris Zbarsky [mailto:bzbar...@mit.edu]
But it also means that user-space code that has to create an HTML element
generically now has to go through document.createElement instead of being
able to do |new
On Jan 13, 2015, at 8:26 PM, Domenic Denicola d...@domenic.me wrote:
From: Bjoern Hoehrmann [mailto:derhoe...@gmx.net]
I know that this a major concern to you, but my impression is that few if
any other people regard that as anything more than nice to have,
especially if you equate
On Jan 13, 2015, at 11:31 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 1/13/15 1:33 PM, Ryosuke Niwa wrote:
Shouldn't we throw in this case because the concert type of somename is
HTMLUnknownElement?
Oh, hmm.
Yes, I guess so. That's very non-obvious to an author.
Even less obvious
On Jan 13, 2015, at 7:05 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Jan 13, 2015 at 6:15 AM, Ryosuke Niwa rn...@apple.com wrote:
As far as I tested, WebKit and Blink keep the old __proto__ while Gecko
changes it to the adopted document's prototype. There is a bug in DOM
On Jan 13, 2015, at 10:45 AM, Domenic Denicola d...@domenic.me wrote:
From: Ryosuke Niwa [mailto:rn...@apple.com]
Shouldn't we throw in this case because the concert type of somename is
HTMLUnknownElement?
Yes, that's exactly the current design. Hidden a bit:
https://github.com
On Jan 13, 2015, at 4:15 AM, cha...@yandex-team.ru wrote:
13.01.2015, 00:57, Ryosuke Niwa rn...@apple.com:
On Jan 12, 2015, at 4:13 AM, cha...@yandex-team.ru wrote:
09.01.2015, 16:42, Anne van Kesteren ann...@annevk.nl:
I'm wondering if it's feasible to provide developers
On Jan 13, 2015, at 11:27 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Jan 13, 2015 at 8:15 PM, Ryosuke Niwa rn...@apple.com wrote:
By the same thing, do you mean that they will manually change __proto__
themselves?
Yes.
Let's say we have MyElement that inherits from
On Jan 13, 2015, at 3:46 PM, Brian Kardell bkard...@gmail.com wrote:
On Tue, Jan 13, 2015 at 2:07 PM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
To separate presentational information (CSS) from the semantics (HTML).
Defining both style isolation boundaries
On Jan 13, 2015, at 10:53 AM, Domenic Denicola d...@domenic.me wrote:
From: Ryosuke Niwa [mailto:rn...@apple.com]
Or, we could always throw an exception in the constructor of
HTMLUnknownElement so that nobody could do it. It would mean that libraries
and frameworks that do support
On Jan 13, 2015, at 10:06 AM, Ryosuke Niwa rn...@apple.com wrote:
On Jan 13, 2015, at 4:21 AM, Arthur Barstow art.bars...@gmail.com wrote:
On 1/13/15 6:54 AM, cha...@yandex-team.ru wrote:
13.01.2015, 05:31, Boris Zbarsky bzbar...@mit.edu:
On 1/12/15 1:56 PM, Olivier Forget wrote
On Jan 12, 2015, at 4:13 AM, cha...@yandex-team.ru wrote:
09.01.2015, 16:42, Anne van Kesteren ann...@annevk.nl:
I'm wondering if it's feasible to provide developers with the
primitive that the combination of Shadow DOM and CSS Scoping provides.
Namely a way to isolate a subtree from
On Jan 12, 2015, at 1:28 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Fri, Jan 9, 2015 at 5:40 AM, Anne van Kesteren ann...@annevk.nl wrote:
I'm wondering if it's feasible to provide developers with the
primitive that the combination of Shadow DOM and CSS Scoping provides.
Namely a
On Jan 12, 2015, at 2:07 PM, Brian Kardell bkard...@gmail.com wrote:
On Mon, Jan 12, 2015 at 4:57 PM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
On Jan 12, 2015, at 4:13 AM, cha...@yandex-team.ru
mailto:cha...@yandex-team.ru wrote:
09.01.2015, 16:42, Anne van
On Jan 12, 2015, at 5:16 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Sun, Jan 11, 2015 at 9:13 PM, Domenic Denicola d...@domenic.me wrote:
However, I don't understand how to make it work for upgraded elements at all
Yes, upgrading is the problem. There's two strategies as far as I
On Jan 12, 2015, at 2:37 PM, Brian Kardell bkard...@gmail.com wrote:
On Mon, Jan 12, 2015 at 5:18 PM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
[snip]
I agree that having both style isolation and subtree isolation is desirable
in some use cases such as Web app
On Jan 12, 2015, at 3:51 PM, Ryosuke Niwa rn...@apple.com wrote:
On Jan 12, 2015, at 2:41 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Mon, Jan 12, 2015 at 2:14 PM, Ryosuke Niwa rn...@apple.com wrote:
On Jan 12, 2015, at 1:28 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
Let's
On Jan 12, 2015, at 4:28 PM, Brian Kardell bkard...@gmail.com wrote:
On Mon, Jan 12, 2015 at 7:23 PM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
On Jan 12, 2015, at 4:16 PM, Brian Kardell bkard...@gmail.com
mailto:bkard...@gmail.com wrote:
Sure, here are some
On Jan 12, 2015, at 2:41 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Mon, Jan 12, 2015 at 2:14 PM, Ryosuke Niwa rn...@apple.com wrote:
On Jan 12, 2015, at 1:28 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
Let's assume we did it, though. We'd have to have some mechanism
On Jan 12, 2015, at 5:41 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
[ryosuke, your mail client keeps producing flattened replies. maybe
send as plain-text, not HTML?]
Weird. I'm not seeing that at all on my end.
The style defined for bar *in bar's setup code* (that is, in a
style
On Jan 12, 2015, at 2:59 PM, Domenic Denicola d...@domenic.me wrote:
From: Ryosuke Niwa [mailto:rn...@apple.com]
As we have repeatedly stated elsewhere in the mailing list, we support
option 1 since authors and frameworks can trivially implement 2 or choose to
set prototype without us
On Jan 12, 2015, at 4:10 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Mon, Jan 12, 2015 at 3:51 PM, Ryosuke Niwa rn...@apple.com wrote:
On Jan 12, 2015, at 2:41 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Mon, Jan 12, 2015 at 2:14 PM, Ryosuke Niwa rn...@apple.com wrote:
On Jan
On Jan 12, 2015, at 4:24 PM, Domenic Denicola d...@domenic.me wrote:
From: Ryosuke Niwa [mailto:rn...@apple.com]
In that case, we can either delay the instantiation of those unknown
elements with - in their names until pending module loads are finished
Could you explain this in a bit
On Jan 12, 2015, at 4:16 PM, Brian Kardell bkard...@gmail.com wrote:
Sure, here are some use cases I can think off the top of my head:
Styling a navigation bar which is implemented as a list of hyperlinks
Styling an article in a blog
Styling the comment section in a blog article
Styling
On Jan 12, 2015, at 6:11 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Mon, Jan 12, 2015 at 5:59 PM, Ryosuke Niwa rn...@apple.com wrote:
On Jan 12, 2015, at 5:41 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
[ryosuke, your mail client keeps producing flattened replies. maybe
send
Hi,
Have you settled the question of what happens to a custom element that's
adopted into another document?
As far as I tested, WebKit and Blink keep the old __proto__ while Gecko changes
it to the adopted document's prototype. There is a bug in DOM component about
this:
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
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
Hi Brian,
The WebKit team has given a lot of feedback over the years on the Shadow DOM
spec. We wouldn't have done that if we didn't care about it. :) We're excited
to hear that Mozilla is planning to give more feedback on Custom Elements and
Shadow DOM because we feel that much of their
On Dec 17, 2014, at 3:18 PM, Brian Kardell bkard...@gmail.com wrote:
On Wed, Dec 17, 2014 at 3:24 PM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
Hi Brian,
The WebKit team has given a lot of feedback over the years on the Shadow DOM
spec. We wouldn't have done
On Dec 17, 2014, at 6:16 PM, Brian Kardell bkard...@gmail.com wrote:
On Wed, Dec 17, 2014 at 4:59 PM, Ryosuke Niwa rn...@apple.com
mailto:rn...@apple.com wrote:
On Dec 17, 2014, at 3:18 PM, Brian Kardell bkard...@gmail.com
mailto:bkard...@gmail.com wrote:
On Wed, Dec 17, 2014 at 3
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 Paris -
and there is an offer to host such a meeting.
So the
On Oct 28, 2014, at 2:23 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Oct 28, 2014 at 8:04 PM, Travis Leithead
travis.leith...@microsoft.com wrote:
There was interest in the room at TPAC at making this a new unique spec
deliverable under webapps.
A single specifiation for
On Oct 6, 2014, at 10:21 AM, Jarek Foksa ja...@foksa.name wrote:
On 2014-10-06, at 18:24, James M. Greene james.m.gre...@gmail.com wrote:
This only thing about this approach that is slightly inconsistent with the
rest of the Web Platform is assuming that the `this` context within the
Hi,
Is either one of you working on innerText specification?
(http://lists.w3.org/Archives/Public/www-archive/2014Mar/0008.html)
I think we need it for the selection API specification because the concept of
being “visually equivalent” and selection.toString need to be defined in terms
of it.
On Sep 15, 2014, at 1:09 PM, Jonas Sicking jo...@sicking.cc wrote:
On Sun, Sep 14, 2014 at 5:54 AM, Dale Harvey d...@arandomurl.com wrote:
websites can already trivially build editors that use copy and paste within
the site itself, the entire problem is that leads to confusing behaviour
when
On Sep 9, 2014, at 6:31 AM, Johannes Wilm johan...@fiduswriter.org wrote:
Absolutely. if this division means we can get into a saner place faster (and
with a higher likelihood that it will actually happen) then I am all for it.
Of course the long-term future of the web should be taken into
On Sep 4, 2014, at 6:46 AM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Thu, Sep 4, 2014 at 5:43 AM, Arthur Barstow art.bars...@gmail.com wrote:
Hi Editors, All,
Speaking of ED boilerplate data ... do we want to try to get some
consistency regarding boilerplate data in our EDs?
We
...@microsoft.com wrote:
I don’t understand the difference. setBaseAndExtent would then set all 4 of
these properties of selection? Do you have a definition to use for this?
From: Ryosuke Niwa [mailto:rn...@apple.com]
Sent: Wednesday, August 6, 2014 12:43 PM
To: James M. Greene
Cc: Ben Peters
, extentOffset), and set the context object's range to the
newly-created range.
From: Ben Peters
Sent: Tuesday, May 20, 2014 11:37 AM
To: Ben Peters; Ryosuke Niwa; public-webapps@w3.org
Subject: RE: [selection] Selection.setBaseAndExtent
I have filed a bug to track this issue [1
101 - 200 of 522 matches
Mail list logo
