On 13/06/2015 16:33, Bruce Lawson wrote:
On 13 June 2015 at 15:30, Léonie Watson lwat...@paciellogroup.com wrote:
why not use the extends= syntax you mentioned?
my-button extends=button attributesPush/my-button
because browsers that don't know about web components wouldn't pay any
attention
From: Bruce Lawson [mailto:bru...@opera.com]
Sent: 13 June 2015 16:34
On 13 June 2015 at 15:30, Léonie Watson lwat...@paciellogroup.com wrote:
why not use the extends= syntax you mentioned?
my-button extends=button attributesPush/my-button
because browsers that don't know about web
From: Tobie Langel [mailto:to...@codespeaks.com]
Sent: 12 June 2015 21:26
On Fri, Jun 12, 2015, at 19:41, Léonie Watson wrote:
Is there a succinct explanation of why the is= syntax is disliked? The
info on the WHATWG wiki explains where is= breaks, but doesn’t offer
much on the syntax issue
From: Bruce Lawson [mailto:bru...@opera.com]
Sent: 13 June 2015 14:57
Subject: Re: Custom Elements: is=
On 12 June 2015 at 21:26, Tobie Langel to...@codespeaks.com wrote:
I'm also concerned developers will mistakenly write:
my-button is=button
As it is much closer in form to what they
On 12 June 2015 at 21:26, Tobie Langel to...@codespeaks.com wrote:
I'm also concerned developers will mistakenly write:
my-button is=button
As it is much closer in form to what they want to achieve (see the
extend=parent syntax I wrote earlier).
That's true (and I've done exactly this
Hello all,
I think a good solution would then be that UAs do a transcoding, or?
(so the spec should recommend doing it)
I understand that the right-menu copy image function has the same
problem except if that one does transcoding (and it probably does, to
offer more native flavours).
That would
On Fri, Jun 12, 2015 at 7:41 PM, Léonie Watson
lwat...@paciellogroup.com wrote:
Is there a succinct explanation of why the is= syntax is disliked?
Rather than
button is=my-button/button
you want
my-button/my-button
that just gets all the button goodness through composition/inheritance.
Folks,
I agree with Anne that we've been having a somewhat circular re-discovery
of the pros/cons here. I believe that the best way to address this is to
capture all of these points in one doc -- this would be a just a little
extra work for the current participants, but super awesome for the
On 13 June 2015 at 15:30, Léonie Watson lwat...@paciellogroup.com wrote:
why not use the extends= syntax you mentioned?
my-button extends=button attributesPush/my-button
because browsers that don't know about web components wouldn't pay any
attention to my-button, and render Push as plain
Doc in progress at
https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Type-Extensions.md
On Sat, Jun 13, 2015 at 8:50 AM, Dimitri Glazkov dglaz...@google.com
wrote:
Folks,
I agree with Anne that we've been having a somewhat circular re-discovery
of the pros/cons here. I believe
On Thu, Jun 11, 2015 at 8:57 PM, Elliott Sprehn espr...@chromium.org
wrote:
I don't think the clipboard should forbid inserting image data, there's so
many ways to compromise desktop software. ex. pasting text/html into
Mail.app might even do it. This API shouldn't be trying to prevent that.
On Fri, Jun 12, 2015, at 19:41, Léonie Watson wrote:
Is there a succinct explanation of why the is= syntax is disliked? The
info on the WHATWG wiki explains where is= breaks, but doesn’t offer much
on the syntax issue [1].
Esthetics aside, the main issue it is takes the concept of inheritance
On Thu, Jun 11, 2015 at 7:51 PM, Wez w...@google.com wrote:
Hallvord,
The proposal isn't to remove support for copying/pasting images, but to
restrict web content from placing compressed image data in one of these
formats on the clipboard directly - there's no issue with content pasting
raw
13 matches
Mail list logo
