Re: [whatwg] [html5] Semantic elements and spec complexity
On Tue, Feb 10, 2009 at 10:02 AM, Ian Hickson i...@hixie.ch wrote: On Thu, 11 Nov 2004, Matthew Thomas wrote: On Wed, 10 Nov 2004, James Graham wrote: Brilliant. I'm opting out of replies to my 2004 mails though ;) -- Jens Meiert http://meiert.com/en/
Re: [whatwg] [html5] Semantic elements and spec complexity
2009/2/11 David Gerard dger...@gmail.com: So the tricky one is to write a language definition that does something meaningful with tag soup. Because tag soup is what human languages are too, and they're learned in a similar fashion (try stuff and see if it works). Oh - and the way MediaWiki (the engine Wikipedia uses) deals with this is: there *is* no language definition - it's a series of PHP regular expressions. The parser is the actual definition of wikitext. This is horrifying in both big and small detail, of course. Also, the language is provably impossible to put into EBNF form. Argh. - d.
Re: [whatwg] [html5] Semantic elements and spec complexity
On Tue, 10 Feb 2009 10:02:36 +0100, Ian Hickson i...@hixie.ch wrote: , default header, footer, and navigation to having a slightly darker background than their parent element It seems like there should be something more obvious that could be done for these elements. For header and footer a border below and above, respectivly, would seem obvious. That would be simple enough, I guess; what do other people think? I think many authors hate default styles so much that they either prefer to just use div or they start their style sheet with resetting the defaults. Since header is intended to be useful to make subheaders not appear in the ToC, the move from h1Foo/h1 h2Bar/h2 to header h1Foo/h1 h2Bar/h2 /header shouldn't, IMHO, result in ugly borders that everyone has to nuke (compare with img border=0). -- Simon Pieters Opera Software
Re: [whatwg] [html5] Semantic elements and spec complexity
On Tue, 10 Feb 2009, Simon Pieters wrote: On Tue, 10 Feb 2009 10:02:36 +0100, Ian Hickson i...@hixie.ch wrote: , default header, footer, and navigation to having a slightly darker background than their parent element It seems like there should be something more obvious that could be done for these elements. For header and footer a border below and above, respectivly, would seem obvious. That would be simple enough, I guess; what do other people think? I think many authors hate default styles so much that they either prefer to just use div or they start their style sheet with resetting the defaults. Since header is intended to be useful to make subheaders not appear in the ToC, the move from h1Foo/h1 h2Bar/h2 to header h1Foo/h1 h2Bar/h2 /header shouldn't, IMHO, result in ugly borders that everyone has to nuke (compare with img border=0). Yeah, that's a good point. I've left it at just display:block. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] [html5] Semantic elements and spec complexity
Since header is intended to be useful to make subheaders not appear in the ToC, the move from h1Foo/h1 h2Bar/h2 to header h1Foo/h1 h2Bar/h2 /header shouldn't, IMHO, result in ugly borders that everyone has to nuke (compare with img border=0). Yeah, that's a good point. I've left it at just display:block. Four-and-a-bit years on I tend to agree :)
