Re: [whatwg] href on any element

2006-08-28 Thread Andrew Fedoniouk
- Original Message - From: "Lachlan Hunt" <[EMAIL PROTECTED]> To: "Andrew Fedoniouk" <[EMAIL PROTECTED]> Cc: "Ian Hickson" <[EMAIL PROTECTED]>; "Anne van Kesteren" <[EMAIL PROTECTED]>; "WHATWG" <[EMAIL PROTECTED]> Sent: Monday, August 28, 2006 11:05 PM Subject: Re: [whatwg] href on an

Re: [whatwg] href on any element

2006-08-28 Thread Lachlan Hunt
Andrew Fedoniouk wrote: Ian Hickson wrote: ... ... If we will change model of A from to something else then it will create implications for parser. What implications? Changing the formal content model of an element doesn't change the way a parser needs to work. Ian's example

Re: [whatwg] href on any element

2006-08-28 Thread Andrew Fedoniouk
- Original Message - From: "Ian Hickson" <[EMAIL PROTECTED]> To: "Anne van Kesteren" <[EMAIL PROTECTED]> Cc: "WHATWG" <[EMAIL PROTECTED]> Sent: Monday, August 28, 2006 5:30 PM Subject: Re: [whatwg] href on any element On Mon, 28 Aug 2006, Anne van Kesteren wrote: On Mon, 28 Aug 200

Re: [whatwg] href on any element

2006-08-28 Thread Ian Hickson
On Mon, 28 Aug 2006, Anne van Kesteren wrote: > > On Mon, 28 Aug 2006 11:33:43 +0200, Lachlan Hunt <[EMAIL PROTECTED]> > wrote: > > > It's arguably a very minor improvement, > > > > The only benefit I'm aware of is the convenience it provides to authors for > > hand coding, but that benefit is neg

Re: [whatwg] Persistent storage is critically flawed.

2006-08-28 Thread Ian Hickson
On Mon, 28 Aug 2006, Shannon Baker wrote: > > > > This is mentioned in the "Security and privacy" section; the third > > bullet point here for example suggests blocking access to "public" > > storage areas: > > > > http://whatwg.org/specs/web-apps/current-work/#user-tracking > > I did read t

Re: [whatwg] Persistent storage is critically flawed.

2006-08-28 Thread Martijn
On 8/28/06, Jim Ley <[EMAIL PROTECTED]> wrote: On 28/08/06, Shannon Baker <[EMAIL PROTECTED]> wrote: > I accept tracking is inevitable but we > shouldn't be making it easier either. You have to remember that the WHAT-WG individual is a Google employee, a company that now relies on accurate track

Re: [whatwg] href on any element

2006-08-28 Thread Anne van Kesteren
On Mon, 28 Aug 2006 11:33:43 +0200, Lachlan Hunt <[EMAIL PROTECTED]> wrote: It's arguably a very minor improvement, The only benefit I'm aware of is the convenience it provides to authors for hand coding, but that benefit is negligible when you consider the abilities of many authoring tool

Re: [whatwg] href on any element

2006-08-28 Thread Lachlan Hunt
Ian Hickson wrote: It isn't always clear what it would mean, either (consider , or ). If the feature were to be added to Web Apps 2.0 (or other future spec) I think it would be sensible to limit it to inline, non-interactive, non-empty elements (e.g. abbr, em, strong, etc.) and a few other s

Re: [whatwg] Persistent storage is critically flawed.

2006-08-28 Thread Jim Ley
On 28/08/06, Shannon Baker <[EMAIL PROTECTED]> wrote: I accept tracking is inevitable but we shouldn't be making it easier either. You have to remember that the WHAT-WG individual is a Google employee, a company that now relies on accurate tracking of details, so don't be surprised that any pro

Re: [whatwg] href on any element

2006-08-28 Thread Lachlan Hunt
Keryx webb wrote: Shut me up and give me a link if this has been discussed before, but I can't find it on Google. Has there been any discussion of allowing the href-attribute in (almost) any element, as in XHTML 2.0? Personally I think this is the one killer feature of XHTML 2 and I would soo