before/after/replaceWith behave the same in this case is just a side effect of
DOM trying to be less surprising and more symmetrical for the curious ones. I
doubt most people would even aware they behave the same in this case. Whenever
the user cases come, I believe most people will just use
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27914
Bug ID: 27914
Summary: [Custom]: Typo instantation --- instantiation
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Minutes logged at: http://www.w3.org/2015/01/28-webapps-minutes.html
Previous minutes: https://www.w3.org/2008/webapps/wiki/Bi-weekly_meetings
masayuki Travis: Hi
masayuki garykac: Hi,
garykac masayuki: Hello
garykac Travis is having trouble with IRC. He's working on a fix right now.
masayuki
So...we discussed 31 e-mails, time to try to reach a consensus? Please
keep in mind, it's too obvious to everyone but you don't have to agree
to build a consensus. We can build a consensus if all can live with
single conclusion.
3 proposals so far:
Proposal A: Leave it undefined. If it's not
I thought a bit of the same thing as Tab when I saw the visual focus
discussion in CSS WG, but my current conclusion is not to think the
two the same thing. Focus may be possible, but selections is a
different thing.
It's true that you could use multi-range selections to select in
visual order.
On Thursday, January 15, 2015, Domenic Denicola d...@domenic.me wrote:
Just to clarify, this argument for symbols is not dependent on modules.
Restated, the comparison is between:
```js
class MyButton extends HTMLElement {
createdCallback() {}
}
```
vs.
```js
class MyButton extends
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27915
Bug ID: 27915
Summary: Clients of WebSockets are not NTP synced (and there is
no NTP-alike spec)
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS:
Agree with this completely.
Yehuda Katz
(ph) 718.877.1325
On Tue, Jan 27, 2015 at 9:32 PM, Domenic Denicola d...@domenic.me wrote:
From: Elliott Sprehn [mailto:espr...@google.com]
Perhaps, but that logically boils down to never use string properties
ever just in case some library conflicts
On Tuesday, January 27, 2015, Domenic Denicola d...@domenic.me wrote:
It does. If a framework says “use clonedCallback and we will implementing
cloning for you,” we cannot add a clonedCallback with our own semantics.
Whereas, if a framework says “use [Framework.cloned] and we will implement
From: Elliott Sprehn [mailto:espr...@google.com]
Perhaps, but that logically boils down to never use string properties ever
just in case some library conflicts with a different meaning. We'd have
$[jQuery.find](...) and so on for plugins.
Nah, it boils down to don't use string properties
On Jan 27, 2015 4:51 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Jan 22, 2015 at 11:43 AM, Jonas Sicking jo...@sicking.cc wrote:
In general I agree that it feels unintuitive that you can't replace a
node
with a collection which includes the node itself. So the extra line or
two
I'm also curios why DOM mutation is a problem.
I read arguments like using the nodes as a key in a Map but such code is
already broken as a node can also be replaced with some user code; so such
code should put into account the node replacement.
I also don't understand how the two-tier
12 matches
Mail list logo
