Re: Beacon API

2013-02-20 Thread James Graham
On 02/20/2013 08:24 AM, Reitbauer, Alois wrote: My personal experience is different. We found that using img tags is not that reliable. Especially in Firefox we recently saw some problems. Img tags in general have the disadvantage that the amount of data that can be set is rather limited. While

Re: [webcomponents]: Building HTML elements with custom elements

2013-02-20 Thread Anne van Kesteren
On Wed, Feb 20, 2013 at 3:01 AM, Scott Miles sjmi...@google.com wrote: Perhaps one other COST of the localName issue is the question of document.createElement. document.createElement('x-button') creates button is='x-button', people complain because the tag names do not match.

Re: [editing] defaultParagraphSeparator

2013-02-20 Thread Aryeh Gregor
Sorry for the delayed response -- I've been busy with other things and didn't have time to check my e-mail. Thanks a lot for the feedback and questions! On Mon, Feb 4, 2013 at 9:59 PM, Alex Mogilevsky alex...@microsoft.com wrote: There was a discussion here a while ago on desired default

Re: [webcomponents]: Building HTML elements with custom elements

2013-02-20 Thread Boris Zbarsky
On 2/20/13 7:26 AM, Anne van Kesteren wrote: These already cannot be just localName checks They often are in practice for extensions and web script. For browser code or better-written extensions and web script they're typically localName + namespaceURI checks. I also fail to see exactly

Re: [editing] Is this the right list to discuss editing?

2013-02-20 Thread Aryeh Gregor
On Tue, Feb 19, 2013 at 11:26 AM, Ms2ger ms2...@gmail.com wrote: FWIW, Aryeh is currently studying full time and doesn't follow web standards discussions regularly. I do check them from time to time, though, and will check any personal e-mail I receive for the time being. In particular, I'm

Re: Custom elements ES6/ES5 syntax compromise, was: document.register and ES6

2013-02-20 Thread Dimitri Glazkov
It seems that there's some additional reasoning that needs to go into whether an element could be constructed as custom tag. Like in this case, it should work both as a custom tag and as a type extension (the is attr). :DG On Tue, Feb 19, 2013 at 10:13 PM, Daniel Buchner dan...@mozilla.com

Re: Custom elements ES6/ES5 syntax compromise, was: document.register and ES6

2013-02-20 Thread Scott Miles
Since many of these cases are 'semantic' elements, whose only raison d'ĂȘtre (afaik) is having a particular localName, I'm not sure how we get around this without being able to specify an 'extends' option. document.register('fancy-header', { prototype: FancyHeaderPrototype, extends: 'header'

Re: Custom elements ES6/ES5 syntax compromise, was: document.register and ES6

2013-02-20 Thread Scott Miles
[I messed up and failed to reply-all a few messages back, see the quoted text to pick up context] semantic is only important in markup Hrm, ok. I'll have to think about that. At any rate, I'm concerned that developers will not be able to predict what kind of node they will get from a

Re: exposing CANVAS or something like it to Web Workers

2013-02-20 Thread Kenneth Russell
On Fri, Feb 8, 2013 at 9:14 AM, Travis Leithead travis.leith...@microsoft.com wrote: What would be the advantage? If you wanted to keep dom elements in sync with the canvas you'd still have to post something from the worker back to the main thread so the main thread would know to pop. Well,

Re: [webcomponents]: Building HTML elements with custom elements

2013-02-20 Thread Jonas Sicking
On Feb 19, 2013 3:54 PM, Dimitri Glazkov dglaz...@chromium.org wrote: 2) Custom element constructor runs at the time of parsing HTML, as the tree is constructed. PROBLEM: Several implementers let me know that allowing to run JS while parsing HTML is not something they can accommodate in a