Standardizing autocapitalize

(bcc: public-webapps@) Hi, I would like to standardize the Apple's proprietary autocapitalize attribute. This attribute is widely used and it would probably benefit the platform to have a broader support for it. The implementation cost should be fairly low while it can be very beneficial for the

template namespace attribute proposal

I'd like to propose that the 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 properly. e.g.: http://www.w3.org/2000/svg> Likewise, should work properly

Re: template namespace attribute proposal

On Thu, Mar 12, 2015 at 4:32 AM, Benjamin Lesh 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 -parsing logic is set up so that things work with

Re: template namespace attribute proposal

On 12/03/2015 11:07 , Anne van Kesteren wrote: On Thu, Mar 12, 2015 at 4:32 AM, Benjamin Lesh 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

Re: CfC: publish WG Note of UI Events; deadline November 14

Hi All, This CfC (original thread is [1]) is now moving forward and on March 17 there will be two publications: 1. /UI Events (Keyboard Extension)/; W3C Working Group Note; (draft is ). 2. /UI Events Specification (formerly DOM Level 3 Events)/

Re: template namespace attribute proposal

On Thu, Mar 12, 2015 at 4:13 AM, Robin Berjon wrote: > On 12/03/2015 11:07 , Anne van Kesteren wrote: > >> On Thu, Mar 12, 2015 at 4:32 AM, Benjamin Lesh wrote: >> >>> What are your thoughts on this idea? >>> >> >> I think it would be more natural (HTML-parser-wise) if we >> special-cased SVG el

Re: template namespace attribute proposal

> On Mar 12, 2015, at 4:13 AM, Robin Berjon wrote: > >> On 12/03/2015 11:07 , Anne van Kesteren wrote: >>> On Thu, Mar 12, 2015 at 4:32 AM, Benjamin Lesh wrote: >>> What are your thoughts on this idea? >> >> I think it would be more natural (HTML-parser-wise) if we >> special-cased SVG element

Re: template namespace attribute proposal

On Thu, Mar 12, 2015 at 3:57 PM, Ryosuke Niwa 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 , but then you could also put in ...) > I'd prefer allowing template elements inside

Re: template namespace attribute proposal

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" wrote: > On Thu, Mar 12, 2015 at 3:57 PM, Ryosuke Niwa wrote: > > By special casing, do you mean

Re: template namespace attribute proposal

On Wed, Mar 11, 2015 at 8:32 PM, Benjamin Lesh wrote: > I'd like to propose that the 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 properly. > > e.g.:

Re: template namespace attribute proposal

On Thu, Mar 12, 2015 at 7:16 PM, Adam Klein wrote: > For clarity, is this significantly different from the below (which works > today)? > > > > > > > > Clearly there's an extra step here, in that accessing the SVG elements > requires hopping into firstElementChild, but adding new name

RE: template namespace attribute proposal

I would also prefer to enable this to work without any extra annotation. So much of the rest of how SVG/MathML are handled in HTML is seamless by design. From: ad...@google.com [mailto:ad...@google.com] On Behalf Of Adam Klein Sent: Thursday, March 12, 2015 11:17 AM To: Benjamin Lesh Cc: WebApps

Re: template namespace attribute proposal

On Thu, Mar 12, 2015 at 11:22 AM, Anne van Kesteren wrote: > On Thu, Mar 12, 2015 at 7:16 PM, Adam Klein wrote: > > For clarity, is this significantly different from the below (which works > > today)? > > > > > > > > > > > > > > > > Clearly there's an extra step here, in that access

Re: template namespace attribute proposal

On Thu, Mar 12, 2015 at 8:24 PM, Adam Klein 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 has fewer compat risks than a wholesale change of the HTML > parser to recognize SVG-

Re: template namespace attribute proposal

> 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 tag in a , you're going to get an HTMLUnknownElement. This is by design and to spec, of course. But it unfortunately means you can't clone() t

[Shadow] URL-based shadows?

Dimitri et al., 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?) I'm curious to know if there's some obvious flaw that I'm missing. element.

Re: [Shadow] URL-based shadows?

Yep. Elliott (cc'd) had a proposal like this a while back. It was coolly received (can't remember the details). :DG< On Thu, Mar 12, 2015 at 5:46 PM, Travis Leithead < travis.leith...@microsoft.com> wrote: > Dimitri et al., > > > >Has the idea of loading/parsing a Shadow DOM directly from a