Re: [whatwg] Tag Soup: Blocks-in-inlines

2006-01-26 Thread Alexey Feldgendler
On Thu, 26 Jan 2006 08:57:55 +0600, Lachlan Hunt [EMAIL PROTECTED] wrote: Semantically, it makes no sense at all to put a block level element within an inline element. Because CSS lets you redefine what's inline and what's block by means of the display property, there sometimes is sense

Re: [whatwg] Tag Soup: Blocks-in-inlines

2006-01-26 Thread Anne van Kesteren
Quoting Alexey Feldgendler [EMAIL PROTECTED]: The simplest, and actually the one being discussed: em pParagraph 1/p pParagraph 2/p /em Why not? These two paragraphs are highlighted with emphasis. What's wrong here, in the semantical sense? em has never been defined in a way that it

Re: [whatwg] Tag Soup: Blocks-in-inlines

2006-01-26 Thread Mikko Rantalainen
Lachlan Hunt wrote: !DOCTYPE html empspanh1X/emY/spanZ/h1/p Mozilla: BODY + EM + P + SPAN + H1 + EM + #text: X + #text: YZ That look reasonably like what the author would want with that rubbish, except that the Z is within the span, but it's not

Re: [whatwg] Tag Soup: Blocks-in-inlines

2006-01-26 Thread Alexey Feldgendler
On Thu, 26 Jan 2006 21:09:44 +0600, Anne van Kesteren [EMAIL PROTECTED] wrote: The simplest, and actually the one being discussed: em pParagraph 1/p pParagraph 2/p /em Why not? These two paragraphs are highlighted with emphasis. What's wrong here, in the semantical sense? em has

Re: [whatwg] Tag Soup: Blocks-in-inlines

2006-01-26 Thread James Graham
Alexey Feldgendler wrote: On Thu, 26 Jan 2006 21:09:44 +0600, Anne van Kesteren em has never been defined in a way that it could give entire paragraphs emphasis. I'm not really saying anything is wrong about it, just that has never been defined. Also, em was defined to be inline-level

Re: [whatwg] validate attribute in A

2006-01-26 Thread Mike Hoye
On Thu, Jan 26, 2006 at 06:15:06AM +0600, Alexey Feldgendler wrote: On Thu, 26 Jan 2006 03:14:07 +0600, Mike Hoye [EMAIL PROTECTED] wrote: The validate attribute would describe an algorithm to employ and a result to compare it to; for example, somebody downloading the en-US version of FF

Re: [whatwg] Tag Soup: Blocks-in-inlines

2006-01-26 Thread Ian Hickson
On Thu, 26 Jan 2006, Mikko Rantalainen wrote: I think a simple way to parse what the author meant is to use just the following rules: 1) An opening tag always starts a new element 2) A matching closing tag closes the element 3) A non-matching closing tag (top of the element stack

Re: [whatwg] Tag Soup: Blocks-in-inlines

2006-01-26 Thread Ian Hickson
On Thu, 26 Jan 2006, Lachlan Hunt wrote: Also, it may need some more improvement, I found an incredibly insane condition that fails in Safari and another that fails a little in Mozilla. !DOCTYPE html empspanh1X/emY/spanZ/h1/p Mozilla: BODY + EM + P + SPAN + H1

Re: [whatwg] Tag Soup: Blocks-in-inlines

2006-01-26 Thread Lachlan Hunt
Alexey Feldgendler wrote: On Thu, 26 Jan 2006 21:09:44 +0600, Anne van Kesteren [EMAIL PROTECTED] wrote: em has never been defined in a way that it could give entire paragraphs emphasis. I'm not really saying anything is wrong about it, just that has never been defined. Also, em was defined to

Re: [whatwg] Adoption Agency Algorithm

2006-01-26 Thread Alexey Feldgendler
On Fri, 27 Jan 2006 08:08:49 +0600, Ian Hickson [EMAIL PROTECTED] wrote: Ok, I specced out what I think is a workable algorithm that works a lot better than what we had before. It still only supports p and em elements inside body for now, but at least it does so in a way compatible with

Re: [whatwg] Adoption Agency Algorithm

2006-01-26 Thread Ian Hickson
On Fri, 27 Jan 2006, Alexey Feldgendler wrote: 1. What happens with the following: script src=1.jsscript src=2.js (without closing tags)? Nothing yet, I haven't specced out the script start tag. I plan to say that it would be treated as script src=1.js, with the element containing the