[Bug 16833] New: consider always exposing a length property for objects with indexed properties

2012-04-24 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16833 Summary: consider always exposing a length property for objects with indexed properties Product: WebAppsWG Version: unspecified Platform: PC OS/Version: All

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

2012-04-24 Thread Rafael Weinstein
No, I hadn't. Let me digest this thread. Much of what I'm implicitly asking has already been discussed. I'll repost if I have anything to add here. Apologies for the noise. On Mon, Apr 23, 2012 at 10:32 PM, Ryosuke Niwa rn...@webkit.org wrote: Have you looked at 

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread Brian Kardell
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

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread Erik Arvidsson
On Tue, Apr 24, 2012 at 06:46, Brian Kardell bkard...@gmail.com wrote: I know of many, many templating systems and I have simply never (aside from MDV) seen it in exactly this light (that is templates actually embedded in others), regardless of whether those are for within the browser for

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread Yuval Sadan
Placing contents as CDATA is an option. I personally think the template/ tag as proposed is adhoc to somebody's notion of how templates should work. To avoid this I think they should be simpler. I am not seeing the added advantage of having the client parse the contents upon encountering it: there

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread James Graham
On 04/24/2012 05:57 PM, Yuval Sadan wrote: Placing contents as CDATA is an option. I personally think the template/ tag as proposed is adhoc to somebody's notion of how templates should work. To avoid this I think they should be simpler. I am not seeing the added advantage of having the

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread Clint Hill
Hmm. I have to say that I disagree that your example below shows a template within a template. That is IMO 1 template wherein there is iteration syntax. But to further my point: Where does the demarcation of template stop and template syntax begin in your example? Or are you saying that the

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread Brian Kardell
On Tue, Apr 24, 2012 at 11:48 AM, Erik Arvidsson a...@chromium.org wrote: On Tue, Apr 24, 2012 at 06:46, Brian Kardell bkard...@gmail.com wrote: I know of many, many templating systems and I have simply never (aside from MDV) seen it in exactly this light (that is templates actually embedded

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread Clint Hill
I agree with these statements: there is no use for the contents before it is used programmatically it's never considered to be part of the document's semantic content I'd like to add that the only use-case for a template/ tag (IMO) is to deliver content to the UA safely preventing the DOM from

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread Tab Atkins Jr.
On Tue, Apr 24, 2012 at 9:12 AM, Clint Hill clint.h...@gmail.com wrote: Hmm. I have to say that I disagree that your example below shows a template within a template. That is IMO 1 template wherein there is iteration syntax. The iteration syntax is basically an element - the example that Arv

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread Tab Atkins Jr.
On Tue, Apr 24, 2012 at 9:11 AM, James Graham jgra...@opera.com wrote: On 04/24/2012 05:57 PM, Yuval Sadan wrote: Placing contents as CDATA is an option. I personally think the template/ tag as proposed is adhoc to somebody's notion of how templates should work. To avoid this I think they

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread Clint Hill
Any way you slice it, common templating scenarios will create problems if you don't hook it up to a proper parser at some point. This is a great point: What parser? If you're implying the HTML Parser, then I think we're talking about a Templating syntax and not just a template/ tag. To which I

[Bug 16840] New: i vear shiad but lagbar mypassword

2012-04-24 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16840 Summary: i vear shiad but lagbar mypassword Product: WebAppsWG Version: unspecified Platform: Other URL: http://www.whatwg.org/specs/web-apps/current-work/#top OS/Version: other

[Bug 16840] i vear shiad but lagbar mypassword

2012-04-24 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16840 Olli Pettay olli.pet...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread Tab Atkins Jr.
On Tue, Apr 24, 2012 at 10:14 AM, Brian Kardell bkard...@gmail.com wrote: On Tue, Apr 24, 2012 at 12:45 PM, Tab Atkins Jr. jackalm...@gmail.com wrote: On Tue, Apr 24, 2012 at 9:12 AM, Clint Hill clint.h...@gmail.com wrote: Hmm. I have to say that I disagree that your example below shows a

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread Brian Kardell
On Tue, Apr 24, 2012 at 1:50 PM, Tab Atkins Jr. jackalm...@gmail.com wrote: On Tue, Apr 24, 2012 at 10:14 AM, Brian Kardell bkard...@gmail.com wrote: On Tue, Apr 24, 2012 at 12:45 PM, Tab Atkins Jr. jackalm...@gmail.com wrote: On Tue, Apr 24, 2012 at 9:12 AM, Clint Hill clint.h...@gmail.com

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread Scott González
On Tue, Apr 24, 2012 at 2:40 PM, Brian Kardell bkard...@gmail.com wrote: All that said, maybe with some time and experience I could learn to love it as DOM too... I'm really not trying to be the only one arguing endlessly about it, so unless someone backs me up on at least some point here I

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Olli Pettay
On 04/24/2012 09:43 PM, Travis Leithead wrote: Based on my reading of DOM4, initEvent makes it possible to transform a trusted event into a non-trusted event and dispatch it. Is that intentional? AFAIK, yes It is only currently supported in Firefox and Opera. In IE, Chrome and Safari, the

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Glenn Maynard
On Tue, Apr 24, 2012 at 2:23 PM, Olli Pettay olli.pet...@helsinki.fiwrote: Yes. It should be possible to re-dispatch events. But if a script running on a web page dispatches event, the event must become untrusted. What's the point of isTrusted, anyway? You have to trust other scripts

RE: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Travis Leithead
Glenn, isTrusted is the indicator that helps the web developer distinguish between an event fired by the UA, or one fired by JavaScript (e.g., dispatchEvent). From: Glenn Maynard [mailto:gl...@zewt.org] Sent: Tuesday, April 24, 2012 12:38 PM To: o...@pettay.fi Cc: Travis Leithead;

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Glenn Maynard
On Tue, Apr 24, 2012 at 2:54 PM, Travis Leithead travis.leith...@microsoft.com wrote: Glenn, isTrusted is the indicator that helps the web developer distinguish between an event fired by the UA, or one fired by JavaScript (e.g., dispatchEvent). I know what it does; I'm asking what its

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Tobie Langel
On 4/24/12 9:54 PM, Travis Leithead travis.leith...@microsoft.com wrote: Glenn, isTrusted is the indicator that helps the web developer distinguish between an event fired by the UA, or one fired by JavaScript (e.g., dispatchEvent). From: Glenn Maynard [mailto:gl...@zewt.org] What's the

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Tobie Langel
On 4/24/12 10:00 PM, Glenn Maynard gl...@zewt.org wrote: On Tue, Apr 24, 2012 at 2:54 PM, Travis Leithead travis.leith...@microsoft.com wrote: Glenn, isTrusted is the indicator that helps the web developer distinguish between an event fired by the UA, or one fired by JavaScript (e.g.,

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Glenn Maynard
On Tue, Apr 24, 2012 at 3:06 PM, Tobie Langel to...@fb.com wrote: Are you asking about the purpose of exposing the property or the purpose of trusted events? I'm asking about the property. The flag underneath it exists only to implement the property. The latter's obvious: prevent visited

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Glenn Maynard
(Sorry, forgot to merge drafts.) On Tue, Apr 24, 2012 at 3:02 PM, Tobie Langel to...@fb.com wrote: See http://www.w3.org/TR/DOM-Level-3-Events/#events-event-type-isTrusted Please don't link people to TR specs; that text is almost a year out of date, which invites pain and confusion. Always

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Anne van Kesteren
On Tue, 24 Apr 2012 22:00:24 +0200, Glenn Maynard gl...@zewt.org wrote: On Tue, Apr 24, 2012 at 2:54 PM, Travis Leithead travis.leith...@microsoft.com wrote: Glenn, isTrusted is the indicator that helps the web developer distinguish between an event fired by the UA, or one fired by JavaScript

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Boris Zbarsky
On 4/24/12 4:34 PM, Glenn Maynard wrote: This is a common misconception of how events work. If you're a browser, default events do not--except for one or two web-compat exceptions--look like this: browse_button.addEventListener(click, function(e) { if(e.isTrusted) openFilePicker(); }, false);

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Tobie Langel
On 4/24/12 11:04 PM, Boris Zbarsky bzbar...@mit.edu wrote: On 4/24/12 5:02 PM, Boris Zbarsky wrote: Oh, and that's before we get into default actions implemented by extensions. And one more thing: extensions _definitely_ want to know whether events are trusted or not. This doesn't necessitate

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Boris Zbarsky
On 4/24/12 5:08 PM, Tobie Langel wrote: On 4/24/12 11:04 PM, Boris Zbarskybzbar...@mit.edu wrote: On 4/24/12 5:02 PM, Boris Zbarsky wrote: Oh, and that's before we get into default actions implemented by extensions. And one more thing: extensions _definitely_ want to know whether events

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Anne van Kesteren
On Tue, 24 Apr 2012 23:02:22 +0200, Boris Zbarsky bzbar...@mit.edu wrote: (DOM3's language about default actions confuses this; I suggest reading DOM4's event section to get a good picture of how this actually works.) Or rather how the DOM4 editor is choosing to conceptualize it, which may

Re: [webcomponents] HTML Parsing and the template element

2012-04-24 Thread Erik Arvidsson
On Tue, Apr 24, 2012 at 12:00, Scott González scott.gonza...@gmail.com wrote: Are there other use cases that are trying to be solved with template? 3. Inert. You don't want to fetch resources at unresolved URLs. img src=/images/${user}.png 4. Selectors should not match content of the template

Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer

2012-04-24 Thread David Herman
On Apr 12, 2012, at 2:48 PM, Arun Ranganathan wrote: I intend to add ArrayBufferView as a parameter to the Blob constructor . Would it be possible also to allow passing an ArrayBuffer with an offset and length as an additional alternative? This would eliminate the need to create a view when

Re: BlobBuilder.append() should take ArrayBufferView in addition to ArrayBuffer

2012-04-24 Thread David Herman
On Apr 24, 2012, at 3:53 PM, David Herman wrote: On Apr 12, 2012, at 2:48 PM, Arun Ranganathan wrote: I intend to add ArrayBufferView as a parameter to the Blob constructor . Would it be possible also to allow passing an ArrayBuffer with an offset and length as an additional alternative?

[Bug 16846] New: cześc to ja rodzyn i wydaje mi się ze jestem na dość dobrej pozycji i w ogóle jestem super i jestem zajebisty ale nie czaje o co chodzi ty wszystklim ludzą skoro to ma tak wyglądać n

2012-04-24 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16846 Summary: cześc to ja rodzyn i wydaje mi się ze jestem na dość dobrej pozycji i w ogóle jestem super i jestem zajebisty ale nie czaje o co chodzi ty wszystklim ludzą skoro to

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Boris Zbarsky
On 4/24/12 5:16 PM, Anne van Kesteren wrote: On Tue, 24 Apr 2012 23:02:22 +0200, Boris Zbarsky bzbar...@mit.edu wrote: (DOM3's language about default actions confuses this; I suggest reading DOM4's event section to get a good picture of how this actually works.) Or rather how the DOM4 editor

RE: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Travis Leithead
I filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=16847 to track getting DOM3 updated on this point. Thanks for the info. BTW: Olli, your email isn't recognized in the Bug DB's CC list. Is there one that will work? -Original Message- From: Olli Pettay

[Bug 16846] cześc to ja rodzyn i wydaje mi się ze jestem na dość dobrej pozycji i w ogóle jestem super i jestem zajebisty ale nie czaje o co chodzi ty wszystklim ludzą skoro to ma tak wyglądać no to

2012-04-24 Thread bugzilla
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16846 Art Barstow art.bars...@nokia.com changed: What|Removed |Added Status|NEW |RESOLVED

Re: [DOM3 Events/DOM4] re-dispatching trusted events with initEvent

2012-04-24 Thread Olli Pettay
On 04/25/2012 12:16 AM, Anne van Kesteren wrote: On Tue, 24 Apr 2012 23:02:22 +0200, Boris Zbarsky bzbar...@mit.edu wrote: (DOM3's language about default actions confuses this; I suggest reading DOM4's event section to get a good picture of how this actually works.) Or rather how the DOM4