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 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', 'track', 'title', 'canvas', 'source', 'video',
'iframe', 'audio', 'font']
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 2015/03/14 9:41, Karl Dubost wrote:
Tab,
The only conflicts in the namespaces are font
(deprecated in SVG2), script and style (harmonizing with HTML so
there's no difference), and a (attempting to harmonize API surface).
*If* I didn't make any mistakes
(I quickly did and didn't check
Could you post the specific regression you ran into?
Specifically this was around platform development. Let's say I have my
developers (those that use my platform) all define their templates in
template/ tags. This is used for all components, including components
that are partials or are
[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', 'script', 'track', 'title', 'canvas', 'source', 'video',
'iframe', 'audio',
On Thu, Mar 12, 2015 at 4:20 PM, Benjamin Lesh bl...@netflix.com wrote:
For my part, I disagree slightly with this statement. If you just drop a
circle tag in a div, you're going to get an HTMLUnknownElement. This is
by design and to spec, of course. But it unfortunately means you can't
On Fri, Mar 13, 2015 at 2:09 PM, Jonas Sicking jo...@sicking.cc wrote:
Unless the SVG WG is willing to drop support for
script![CDATA[...]]/script. But that seems like it'd break a lot
of content.
Like, on the same line? Because I recall that sort of thing showing up
in old HTML tutorials,
On Thu, Mar 12, 2015 at 3:07 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Mar 12, 2015 at 4:32 AM, Benjamin Lesh bl...@netflix.com wrote:
What are your thoughts on this idea?
I think it would be more natural (HTML-parser-wise) if we
special-cased SVG elements, similar to how e.g.
On Fri, Mar 13, 2015 at 1:27 PM, Benjamin Lesh bl...@netflix.com wrote:
I agree completely, Tab, but it's actually too late to stop forcing authors
to think about namespaces, the fact I currently have to think about it is
the source of this suggestion.
You have to think about it today *because
On Fri, Mar 13, 2015 at 1:57 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Fri, Mar 13, 2015 at 1:48 PM, Jonas Sicking jo...@sicking.cc wrote:
On Fri, Mar 13, 2015 at 1:16 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Thu, Mar 12, 2015 at 3:07 AM, Anne van Kesteren ann...@annevk.nl
On Fri, Mar 13, 2015 at 1:16 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Thu, Mar 12, 2015 at 3:07 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Mar 12, 2015 at 4:32 AM, Benjamin Lesh bl...@netflix.com wrote:
What are your thoughts on this idea?
I think it would be more natural
I agree completely, Tab, but it's actually too late to stop forcing authors
to think about namespaces, the fact I currently have to think about it is
the source of this suggestion.
The merging of namespaces is the ideal solution, no doubt, but it's
probably not a realistic solution in the short
On Fri, Mar 13, 2015 at 1:48 PM, Jonas Sicking jo...@sicking.cc wrote:
On Fri, Mar 13, 2015 at 1:16 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Thu, Mar 12, 2015 at 3:07 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Mar 12, 2015 at 4:32 AM, Benjamin Lesh bl...@netflix.com wrote:
Tab,
The only conflicts in the namespaces are font
(deprecated in SVG2), script and style (harmonizing with HTML so
there's no difference), and a (attempting to harmonize API surface).
*If* I didn't make any mistakes
(I quickly did and didn't check everything.)
The intersection seems to be:
On 12/03/2015 11:07 , Anne van Kesteren wrote:
On Thu, Mar 12, 2015 at 4:32 AM, Benjamin Lesh bl...@netflix.com wrote:
What are your thoughts on this idea?
I think it would be more natural (HTML-parser-wise) if we
special-cased SVG elements, similar to how e.g. table elements are
On Thu, Mar 12, 2015 at 4:13 AM, Robin Berjon ro...@w3.org wrote:
On 12/03/2015 11:07 , Anne van Kesteren wrote:
On Thu, Mar 12, 2015 at 4:32 AM, Benjamin Lesh bl...@netflix.com wrote:
What are your thoughts on this idea?
I think it would be more natural (HTML-parser-wise) if we
FWIW: Currently, template tags nested in svg are SVGElement, and not
HTMLTemplate Element. You also need to hide the SVG container or it will be
rendered.
On Mar 12, 2015 8:18 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Mar 12, 2015 at 3:57 PM, Ryosuke Niwa rn...@apple.com wrote:
By
On Thu, Mar 12, 2015 at 3:57 PM, Ryosuke Niwa rn...@apple.com wrote:
By special casing, do you mean to recognize SVG element names?
Yeah, not really sure there's another way of doing it. (You can of
course put things within svg, but then you could also put tbody in
table...)
I'd prefer
On Thu, Mar 12, 2015 at 7:16 PM, Adam Klein ad...@chromium.org wrote:
For clarity, is this significantly different from the below (which works
today)?
template id=tmpl
svg
circle .../
/svg
/template
Clearly there's an extra step here, in that accessing the SVG elements
requires
On Thu, Mar 12, 2015 at 11:22 AM, Anne van Kesteren ann...@annevk.nl
wrote:
On Thu, Mar 12, 2015 at 7:16 PM, Adam Klein ad...@chromium.org wrote:
For clarity, is this significantly different from the below (which works
today)?
template id=tmpl
svg
circle .../
/svg
On Thu, Mar 12, 2015 at 8:24 PM, Adam Klein ad...@chromium.org wrote:
Is your thinking that adding special-casing for SVG-looking (as in, tag
names appearing in the list of SVG tags but not in the list of HTML tags)
inside template has fewer compat risks than a wholesale change of the HTML
On Wed, Mar 11, 2015 at 8:32 PM, Benjamin Lesh bl...@netflix.com wrote:
I'd like to propose that the template tag have a namespace= attribute
that allows the user to specify namespaces such as
http://www.w3.org/2000/svg;, so that the document fragment that comes
from `.content` is created
WG
Subject: Re: template namespace attribute proposal
On Wed, Mar 11, 2015 at 8:32 PM, Benjamin Lesh
bl...@netflix.commailto:bl...@netflix.com wrote:
I'd like to propose that the template tag have a namespace= attribute that
allows the user to specify namespaces such as http://www.w3.org/2000
On Thu, Mar 12, 2015 at 4:32 AM, Benjamin Lesh bl...@netflix.com wrote:
What are your thoughts on this idea?
I think it would be more natural (HTML-parser-wise) if we
special-cased SVG elements, similar to how e.g. table elements are
special-cased today. A lot of template-parsing logic is set up
So much of the rest of how SVG/MathML are handled in HTML is seamless by
design. For my part, I disagree slightly with this statement. If you just
drop a circle tag in a div, you're going to get an HTMLUnknownElement.
This is by design and to spec, of course. But it unfortunately means you
can't
26 matches
Mail list logo
