Re: [whatwg] href on any element

2006-08-29 Thread Lachlan Hunt
Andrew Fedoniouk wrote: Ian Hickson wrote: a href= h2.../h2 p.../p /a If we will change model of A from !ELEMENT A - - (%inline;)* -(A) -- anchor -- to something else then it will create implications for parser. What implications? Changing the formal content model of an

Re: [whatwg] href on any element

2006-08-29 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 any element Andrew

Re: [whatwg] href on any element

2006-08-29 Thread Lachlan Hunt
Andrew Fedoniouk wrote: Lachlan Hunt wrote: Andrew Fedoniouk wrote: Ian Hickson wrote: a href= h2.../h2 p.../p /a If we will change model of A from !ELEMENT A - - (%inline;)* -(A) -- anchor -- to something else then it will create implications for parser. What

[whatwg] Table integrity and conformance

2006-08-29 Thread Henri Sivonen
Should one expect HTML table row/column integrity to become an HTML5 conformance requirement? That is, will these tables be non-conforming: table trtd rowspan=2/td/tr /table table trtd/td/tr trtd/tdtd/td/tr /table ? (This is something static document authors probably would prefer to have

Re: [whatwg] href on any element

2006-08-29 Thread Ric Hardacre
Ian Hickson wrote: 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

Re: [whatwg] Persistent storage is critically flawed.

2006-08-29 Thread Shannon Baker
Ian Hickson said (among other things): It seems that what you are suggesting is that foo.example.com cannot trust example.com, because example.com could then steal data from foo.example.com. But there's a much simpler attack scenario for example.com: it can just take over foo.example.com

Re: [whatwg] href on any element

2006-08-29 Thread dolphinling
Lachlan Hunt wrote: Andrew Fedoniouk wrote: If yes then let it be just : section href=... h2... p... /section But that isn't backwards compatible. data:text/html,tabletra hef=www.google.comtdlink to google/td/atdplain text/td/tr/table Neither is a around table cells or list items.

Re: [whatwg] href on any element

2006-08-29 Thread Francisco Monteiro
What practical use has this for Mr Joe Public? Give me a really useful example in very simple wording! Francisco -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of dolphinling Sent: 29 August 2006 16:46 To: WHAT WG List Subject: Re: [whatwg] href on any

Re: [whatwg] proposed canvas 2d API additions

2006-08-29 Thread Anne van Kesteren
On Fri, 19 May 2006 17:34:04 +0200, Ian Hickson [EMAIL PROTECTED] wrote: One other problem I had with it was that the colors are restricted to 8 bit. That may potentially lead to data loss but I guess it's not a major concern yet. This is already the case in other aspects of the API, I think.

Re: [whatwg] href on any element

2006-08-29 Thread Kornel Lesinski
On Tue, 29 Aug 2006 17:02:22 +0100, Francisco Monteiro [EMAIL PROTECTED] wrote: What practical use has this for Mr Joe Public? Give me a really useful example in very simple wording! Having data table representing list of items where large clickable area is useful - i.e. inbox in a

Re: [whatwg] proposed canvas 2d API additions

2006-08-29 Thread Ian Hickson
On Tue, 29 Aug 2006, Anne van Kesteren wrote: On Fri, 19 May 2006 17:34:04 +0200, Ian Hickson [EMAIL PROTECTED] wrote: One other problem I had with it was that the colors are restricted to 8 bit. That may potentially lead to data loss but I guess it's not a major concern yet. This

Re: [whatwg] Lists, ins/del, and a

2006-08-29 Thread James Graham
Michel Fortin wrote: (Note that everything applying to normal lists in this message could also apply to definition lists and tables.) The ongoing thread about a global href attribute versus a block-level a element made me think of a similar situation concerning ins and del. How can we markup

[whatwg] return lowercase hex values for fillStyle and strokeStyle

2006-08-29 Thread Anne van Kesteren
Instead of returning an uppercase six digit hex value I suggest returning a lowercase value for compatibility with what UAs (including IE) currently do for CSS already and what Mozilla already does for canvas. -- Anne van Kesteren http://annevankesteren.nl/ http://www.opera.com/

Re: [whatwg] href on any element

2006-08-29 Thread Matthew Raymond
Kornel Lesinski wrote: On Tue, 29 Aug 2006 17:02:22 +0100, Francisco Monteiro Having data table representing list of items where large clickable area is useful - i.e. inbox in a webmail, list of contacts, forum threads listing, etc. I've ran into this problem many times and seen many

Re: [whatwg] href on any element

2006-08-29 Thread Kornel Lesinski
On Tue, 29 Aug 2006 22:55:01 +0100, Matthew Raymond [EMAIL PROTECTED] wrote: Having data table representing list of items where large clickable area is useful - i.e. inbox in a webmail, list of contacts, forum threads listing, etc. I've ran into this problem many times and seen many

Re: [whatwg] Lists, ins/del, and a

2006-08-29 Thread Alexey Feldgendler
On Wed, 30 Aug 2006 01:09:26 +0700, Michel Fortin [EMAIL PROTECTED] wrote: ul insliSome list item/li/ins delliAnother list item/li/del /ul Changing this to allow the above markup has consequences on the DOM: for instance we could no longer iterate on the content of a

Re: [whatwg] Lists, ins/del, and a

2006-08-29 Thread Lachlan Hunt
Michel Fortin wrote: How can we markup removed or inserted list items? Here's a general idea: ul insliSome list item/li/ins delliAnother list item/li/del /ul This can be solved by putting the ins and del elements as the only child nodes of the li elements instead. ul

Re: [whatwg] Lists, ins/del, and a

2006-08-29 Thread Andrew Fedoniouk
- Original Message - From: Lachlan Hunt [EMAIL PROTECTED] To: Michel Fortin [EMAIL PROTECTED] Cc: whatwg List [EMAIL PROTECTED] Sent: Tuesday, August 29, 2006 8:00 PM Subject: Re: [whatwg] Lists, ins/del, and a Michel Fortin wrote: How can we markup removed or inserted list items?

Re: [whatwg] Lists, ins/del, and a

2006-08-29 Thread Michel Fortin
Le 29 août 2006 à 23:00, Lachlan Hunt a écrit : Michel Fortin wrote: How can we markup removed or inserted list items? Here's a general idea: ul insliSome list item/li/ins delliAnother list item/li/del /ul This can be solved by putting the ins and del elements as the only

[whatwg] Fw: Lists, ins/del, and a

2006-08-29 Thread Andrew Fedoniouk
- Original Message - From: Alexey Feldgendler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, August 29, 2006 7:47 PM Subject: Re: [whatwg] Lists, ins/del, and a On Wed, 30 Aug 2006 01:09:26 +0700, Michel Fortin [EMAIL PROTECTED] wrote: ul insliSome list

Re: [whatwg] Fw: Lists, ins/del, and a

2006-08-29 Thread Alexey Feldgendler
On Wed, 30 Aug 2006 10:57:51 +0700, Andrew Fedoniouk [EMAIL PROTECTED] wrote: Probably, lists should implement a special DOM interface which allows to iterate over the list items. Tables have such an interface. Why not to implement just one simple function: function foo(element) { ... }

[whatwg] Fw: Fw: Lists, ins/del, and a

2006-08-29 Thread Andrew Fedoniouk
- Original Message - From: Alexey Feldgendler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, August 29, 2006 9:18 PM Subject: Re: [whatwg] Fw: Lists, ins/del, and a On Wed, 30 Aug 2006 10:57:51 +0700, Andrew Fedoniouk [EMAIL PROTECTED] wrote: Probably, lists should