RE: publish LCWD of Server-sent Events; deadline April 23

2012-04-23 Thread SULLIVAN, BRYAN L
I support the LCWD publication. Thanks, Bryan Sullivan -Original Message- From: Arthur Barstow [mailto:art.bars...@nokia.com] Sent: Monday, April 16, 2012 4:44 AM To: public-webapps Subject: CfC: publish LCWD of Server-sent Events; deadline April 23 The Server-sent Events spec has

Custom Tags and Local Semantics

2012-04-23 Thread Dimitri Glazkov
Eric Meyer (cc'd) posted an intriguing article about custom tags and local semantics: http://meyerweb.com/eric/thoughts/2012/04/10/element-customization/ I must say, even though the current direction we take with Web Components does not involve custom tags, I still find the current, is

Re: Custom Tags and Local Semantics

2012-04-23 Thread Marat Tanalin | tanalin . com
FWIW: my proposal (already successfully rejected) for custom elements (real custom elements with really arbitrary tag names allowed) in W3 bug tracker from 2011-09-03: https://www.w3.org/Bugs/Public/show_bug.cgi?id=14011 BTW, it seems local semantics (what my proposal is about and what you are

Re: [webcomponents] HTML Parsing and the template element

2012-04-23 Thread Yuval Sadan
You musn't forget what we're not planning for. Templates can be great for so many applications - generating code (JSON, Javascript), generating plain-text or otherwise formatted (markdown, restructured text, etc.) content and much more. I don't think templates should be parsed by DOM unless

Re: [webcomponents] HTML Parsing and the template element

2012-04-23 Thread Ryosuke Niwa
Why don't we just use script elements for that then? On Mon, Apr 23, 2012 at 3:52 PM, Yuval Sadan sadan.yu...@gmail.com wrote: You musn't forget what we're not planning for. Templates can be great for so many applications - generating code (JSON, Javascript), generating plain-text or

Re: [webcomponents] HTML Parsing and the template element

2012-04-23 Thread Rafael Weinstein
Yes. I think this issue is a distraction. Using the script tag for encoding opaque text contents is a hack, but it works as well as it can. AFAIC, The main drawback is that the contents cannot contain the string /script. This will be the case for any new element we came up with for this purpose.

Re: [webcomponents] HTML Parsing and the template element

2012-04-23 Thread Clint Hill
I'd like to weigh in on this topic as it is something that I'm involved in at work as well. Could you maybe explain further parsing the template contents as HTML Š can contain sub templates? If you take this example: template div!-- A little markup //--/div template!-- subtemplate

Re: [webcomponents] Template element parser changes = Proposal for adding DocumentFragment.innerHTML

2012-04-23 Thread Ryosuke Niwa
Have you looked at http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0663.html ? On Mon, Apr 23, 2012 at 8:39 PM, Rafael Weinstein rafa...@google.comwrote: The main points of contention in the discussion about the template element are 1) By what mechanism are its content elements