Re: [webcomponents] HTML Parsing and the element

On Thu, Feb 9, 2012 at 12:00 AM, Dimitri Glazkov wrote: > == IDEA 1: Keep template contents parsing in the tokenizer == Not this! Here's why: Making something look like markup but then not tokenizing it as markup is confusing. The confusion leads to authors not having a clear mental model of wha

Re: [webcomponents] HTML Parsing and the element

On Thu, Feb 9, 2012 at 13:45, Dimitri Glazkov wrote: > On Wed, Feb 8, 2012 at 8:16 PM, Ryosuke Niwa wrote: > > On Wed, Feb 8, 2012 at 7:31 PM, Brian Kardell > wrote: > >> > >> Then why not something like > >> > >> world > >> hello > > > > Right. If we were to disallow nested templates, that's

Re: [webcomponents] HTML Parsing and the element

On Wed, Feb 8, 2012 at 8:16 PM, Ryosuke Niwa wrote: > On Wed, Feb 8, 2012 at 7:31 PM, Brian Kardell wrote: >> >> Then why not something like >> >> world >> hello > > Right. If we were to disallow nested templates, that's the way to go. The > question is whether we should disallow nested template

Re: April face-to-face meetings for HTML and WebApps

Regarding the checklist: perhaps these things are only relevant if there are Christian/Jewish/Muslim people in the group. And if there are people that prefer not to meet on Saturday. It seems to me more reasonable to expect people with prior commitments, that plan to attend, to speak up, and expect

Re: [webcomponents] HTML Parsing and the element

On Wed, Feb 8, 2012 at 7:31 PM, Brian Kardell wrote: > Then why not something like > > world > hello > Right. If we were to disallow nested templates, that's the way to go. The question is whether we should disallow nested templates or not. - Ryosuke

Re: [webcomponents] HTML Parsing and the element

Then why not something like world hello On Feb 8, 2012 10:22 PM, "Ryosuke Niwa" wrote: > On Wed, Feb 8, 2012 at 5:20 PM, Brian Kardell wrote: > >> Are you essentially suggesting partials? Basically, one template can >> contain another only by reference? Then you have something like a >> corr

Re: [webcomponents] HTML Parsing and the element

On Wed, Feb 8, 2012 at 5:20 PM, Brian Kardell wrote: > Are you essentially suggesting partials? Basically, one template can > contain another only by reference? Then you have something like a > corresponding tag or macro-ish thing whereby you can reference > (functionally include) on themplate

Re: [webcomponents] HTML Parsing and the element

Are you essentially suggesting partials? Basically, one template can contain another only by reference? Then you have something like a corresponding tag or macro-ish thing whereby you can reference (functionally include) on themplate from another? That sidesteps the whole nested template parsing

Re: [webcomponents] HTML Parsing and the element

On Wed, Feb 8, 2012 at 3:16 PM, Adam Barth wrote: > On Wed, Feb 8, 2012 at 2:47 PM, Rafael Weinstein wrote: >> Here's a real-world example, that's probably relatively simple >> compared to "high traffic" web pages (i.e. amazon or facebook) >> >> http://src.chromium.org/viewvc/chrome/trunk/src/chr

Re: [webcomponents] HTML Parsing and the element

On Wed, Feb 8, 2012 at 2:47 PM, Rafael Weinstein wrote: > Here's a real-world example, that's probably relatively simple > compared to "high traffic" web pages (i.e. amazon or facebook) > > http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/template/api_template.html?rev

Re: [webcomponents] HTML Parsing and the element

On Wed, Feb 8, 2012 at 2:54 PM, Dimitri Glazkov wrote: > On Wed, Feb 8, 2012 at 2:41 PM, Ryosuke Niwa wrote: > > On Wed, Feb 8, 2012 at 2:00 PM, Dimitri Glazkov > > wrote: > >> > >> == IDEA 1: Keep template contents parsing in the tokenizer == > >> > >> PRO: if we could come up with a way to per

Re: Installing web apps

Hi Adrienne, On Feb 8, 2012, at 22:56 , Adrienne Porter Felt wrote: > I agree that the current UI is not great. However, I disagree about > "everyone" clicking through permission grants. I've done two user studies > and found that about ~18% of people look at permissions for a given > install

Re: [webcomponents] HTML Parsing and the element

On Wed, Feb 8, 2012 at 2:41 PM, Ryosuke Niwa wrote: > On Wed, Feb 8, 2012 at 2:00 PM, Dimitri Glazkov > wrote: >> >> == IDEA 1: Keep template contents parsing in the tokenizer == >> >> PRO: if we could come up with a way to perceive the stuff between >> and as a character stream, we enable a se

Re: [webcomponents] HTML Parsing and the element

Here's a real-world example, that's probably relatively simple compared to "high traffic" web pages (i.e. amazon or facebook) http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/template/api_template.html?revision=120962&content-type=text%2Fplain that produces each page

Re: [webcomponents] HTML Parsing and the element

[This time from the right email] On Wed, Feb 8, 2012 at 2:10 PM, Adam Barth wrote: > Re-using the generic raw text element parsing algorithm would be the > simplest change to the parser.  Do you have a concrete example of > where nested declarations are required?  For example, > rather than incl

Re: [webcomponents] Considering declarative event handlers

On Tue, Feb 7, 2012 at 12:41 PM, Dimitri Glazkov wrote: > To make Web Components more usable, I would like to consider providing > a way to declare event handlers in markup. As I look over the use > cases and try to implement them using the proposed syntax > (http://dvcs.w3.org/hg/webcomponents/ra

Re: [webcomponents] HTML Parsing and the element

On Wed, Feb 8, 2012 at 2:00 PM, Dimitri Glazkov wrote: > == IDEA 1: Keep template contents parsing in the tokenizer == > > PRO: if we could come up with a way to perceive the stuff between > and as a character stream, we enable a set of > use cases where the template contents does not need to be

Re: [webcomponents] HTML Parsing and the element

On Wed, Feb 8, 2012 at 2:20 PM, Erik Arvidsson wrote: > On Wed, Feb 8, 2012 at 14:10, Adam Barth wrote: >> ... Do you have a concrete example of >> where nested declarations are required? > > When working with tree like structures it is comment to use recursive > templates. > > http://code.goog

Re: Installing web apps

> > > I agree that the current UI is not great. However, I disagree about > "everyone" clicking through permission grants. I've done two user studies > and found that about ~18% of people look at permissions for a given > installation, and about ~60% look occasionally. We found that most have no >

Re: Installing web apps

Hi Adrienne, On Wednesday, 8 February 2012 at 21:56, Adrienne Porter Felt wrote: > > > On Feb 1, 2012, at 21:20 , Paul Libbrecht wrote: > > > Le 1 févr. 2012 à 21:03, Boris Zbarsky a écrit : > > > > > Android goes somewhat in this direction with its app-security model... > > > > > > > >

Re: [webcomponents] HTML Parsing and the element

On Wed, Feb 8, 2012 at 14:10, Adam Barth wrote: > ... Do you have a concrete example of > where nested declarations are required? When working with tree like structures it is comment to use recursive templates. http://code.google.com/p/mdv/source/browse/use_cases/tree.html -- erik

Re: Installing web apps

On Feb 8, 2012, at 01:06 , Jean-Claude Dufourd wrote: > On 7/2/12 05:31 , Robin Berjon wrote: >> The first problem is that of the security model. A lot of smart people have >> tried to come up with a lot of different solutions here, often involving >> signatures, policies, intricate user interfac

Re: [webcomponents] Considering declarative event handlers

On Tue Feb 07 11:41:24 GMT-800 2012, Dimitri Glazkov wrote: > The pros are: > * It's declarative and intuitively logical I think this is a cons. Now you need both markup and code where you only had code before. This also does not scale very well and it brings us down the XBL/HTC path:

Re: [webcomponents] HTML Parsing and the element

Re-using the generic raw text element parsing algorithm would be the simplest change to the parser. Do you have a concrete example of where nested declarations are required? For example, rather than including nested templates, you might instead consider referencing other template elements by id.

[webcomponents] HTML Parsing and the element

Hello folks! You may be familiar with the work around the element, or a way to declare document fragments in HTML (see http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-November/033868.html for some background). In trying to understand how this newfangled beast would work, I started resea

Re: Installing web apps

> On Feb 1, 2012, at 21:20 , Paul Libbrecht wrote: > > Le 1 févr. 2012 à 21:03, Boris Zbarsky a écrit : > >>> Android goes somewhat in this direction with its app-security model... > >> > >> With all due respect, the app-security model on Android is a joke. > Everyone just clicks through the permis

Re: Installing web apps

On Feb 2, 2012, at 09:51 , Jean-Claude Dufourd wrote: > JCD: I do not see why the granting of privileges should be implicit when some > webapp is "installed". It all boils down to what "installation" means. For instance, if you take a super lightweight approach to it similar to Firefox's app tab

Re: Installing web apps

On Feb 1, 2012, at 21:20 , Paul Libbrecht wrote: > Le 1 févr. 2012 à 21:03, Boris Zbarsky a écrit : >>> Android goes somewhat in this direction with its app-security model... >> >> With all due respect, the app-security model on Android is a joke. Everyone >> just clicks through the permissions g

Re: CfC by 02-14: Add IME API to the charter

On Feb 8, 2012, at 13:29 , Charles McCathieNevile wrote: > thanks to Mike and the Google guys, we have > http://dvcs.w3.org/hg/ime-api/raw-file/default/use-cases/Overview.html which > explains what an IME API would do and why it would be useful. I believe we > have editors but it doesn't name a

Re: CfC by 02-14: Add IME API to the charter

thanks, i was just checking; i'll defer to Addison and the editor of the proposed work to handle the details On Wed, Feb 8, 2012 at 9:02 AM, Michael[tm] Smith wrote: > Hi Glenn, > > > @2012-02-08 08:33 -0700: > > will there be liaison/participation with I18N Core WG on this work? > > I've alread

Re: CfC by 02-14: Add IME API to the charter

Hi Glenn, > @2012-02-08 08:33 -0700: > will there be liaison/participation with I18N Core WG on this work? I've already given Richard Ishida and Felix Sasaki a heads-up about it. I believe Richard is planning to propose an agenda item for it on the i18n WG call today. But anyway certainly there s

Re: CfC by 02-14: Add IME API to the charter

will there be liaison/participation with I18N Core WG on this work? On Wed, Feb 8, 2012 at 5:29 AM, Charles McCathieNevile wrote: > Hi, > > thanks to Mike and the Google guys, we have http://dvcs.w3.org/hg/ime-api/ > **raw-file/default/use-cases/**Overview.html

Re: Installing web apps

On 8.2.2012 14:25, Scott Wilson wrote: Hi just let me quote from this thread - Tim Berners-Lee: There of course places where XHR is used and there is no cross-sitescripting security needed 1) in a browser extension 2) in node.js code

Re: Concerns regarding cross-origin copy/paste security

Adam Barth skreiv Wed, 08 Feb 2012 00:05:54 +0100 FWIW, my main concern was the hidden data aspect because it can be abused for cross-site request forgery if a malicious site by getting the user to copy and paste gets access to form anti-CSRF tokens and such. That's certainly possible, bu

Re: Installing web apps

On 8 Feb 2012, at 10:31, Bronislav Klučka wrote: > > > On 8.2.2012 1:06, Jean-Claude Dufourd wrote: >> On 7/2/12 05:31 , Robin Berjon wrote: >>> The first problem is that of the security model. A lot of smart people have >>> tried to come up with a lot of different solutions here, often involvi

CfC by 02-14: Add IME API to the charter

Hi, thanks to Mike and the Google guys, we have http://dvcs.w3.org/hg/ime-api/raw-file/default/use-cases/Overview.html which explains what an IME API would do and why it would be useful. I believe we have editors but it doesn't name a test facilitator (don't blame me, Art chose that as th

Re: April face-to-face meetings for HTML and WebApps

It's Passover [1]. Passover begins in the evening of Friday, April 6, 2012, and ends in the evening of Saturday, April 14, 2012. As it happens, your calendar hits the *end* of Passover which is just as major of a holiday as the beginning (the middle is somewhat minor). At the risk of being seen as

Re: Installing web apps

On 8.2.2012 1:06, Jean-Claude Dufourd wrote: On 7/2/12 05:31 , Robin Berjon wrote: The first problem is that of the security model. A lot of smart people have tried to come up with a lot of different solutions here, often involving signatures, policies, intricate user interfaces, etc. I thin

Re: Enabling a Web app to override auto rotation?

The general use case is any UI that's been designed exclusively for portrait or landscape mode because displaying it in the other mode either doesn't make any sense (e.g. most platform games), requires some artifice that the designer wanted to avoid (e.g. to function in landscape mode, e-readers re

Re: Enabling a Web app to override auto rotation?

On Wednesday, 8 February 2012 at 07:39, Charles Pritchard wrote: > In case it's needed; use case: > > User is drawing a sketch on their mobile phone and their rotation is > intentional as if they are working with a physical piece of paper. or a car game where the driving is controlled by how