Re: [whatwg] Allow trailing slash in always-empty HTML5 elements?

On Dec 4, 2006, at 6:56 AM, Shadow2531 wrote: ... Firefox could do the same with the yellow bar that pops up at the top of the page that says, "The document appears to be XHTML, but is not well formed. Firefox has reparsed it as HTML for you in an attempt to handle the errors.", or something like

Re: [whatwg] XML databases, XML syntax and HTML5

On 12/8/06, Elliotte Harold <[EMAIL PROTECTED]> wrote: Robert Sayre wrote: > I disagree. Wouldn't it be more profitable to build an HTML database? > No. XML databases are a lot more general purpose and support many more use cases. says who? -- Robert Sayre "I would have written a shorter l

Re: [whatwg] XML databases, XML syntax and HTML5

Robert Sayre wrote: I disagree. Wouldn't it be more profitable to build an HTML database? No. XML databases are a lot more general purpose and support many more use cases. -- Elliotte Rusty Harold [EMAIL PROTECTED] Java I/O 2nd Edition Just Published! http://www.cafeaulait.org/books/java

Re: [whatwg] XML databases, XML syntax and HTML5

On 12/8/06, Elliotte Harold <[EMAIL PROTECTED]> wrote: One consequence of building on top of native XML database rather than a relational database is that well-formedness is going to become more important, not less. I disagree. Wouldn't it be more profitable to build an HTML database? -- Rob

[whatwg] XML databases, XML syntax and HTML5

Alexey Feldgendler wrote: LiveJournal, a popular blogging service, inserts hand-authored content into hand-authored templates. While the templates are written by competent authors who (mostly) know how to write proper HTML, blog posts are most often written by people who barely learnt how to

[whatwg] @autosubmit on

Seeing how the element is mostly used in the wild, I think an 'autosubmit' attribute on the element will increase accessibility because the current deployed solutions all depend on JavaScript, usually without any kind of fallback to an ordinary submit button. Seeing that having an onchange even

Re: [whatwg] several messages about XML syntax and HTML5

Hi, From: Sander Tekelenburg <[EMAIL PROTECTED]> Right. That's a window of opportunity (for the sort of attack I mentioned) I'm voicing concern about. I agree that it will likely be much harder when all browsers are HTML5-compliant and most authors produce HTML5. But before that? Well... for t

Re: [whatwg] PaceEntryMediatype

On Fri, 8 Dec 2006, Martin Atkins wrote: > Ian Hickson wrote: > > > > Then the browser wouldn't take these links and make them available in a > > "list of feeds" interface, which is the problem we are trying to solve. > > Why is it useful for a browser to make a list of a bunch of random feeds >

Re: [whatwg] [WebApps] "html" start tag token in main phase

On Fri, 8 Dec 2006, J. King wrote: > > The root element phase dictates that any start tag (including "html") > produces an element in the document and is then re-processed in > the main phase. The main phase then states that if an "html" start tag > token is encountered it produces a parse erro

Re: [whatwg] innerHTML for HTML and

On Fri, 8 Dec 2006, Anne van Kesteren wrote: > > The section "If the child node is a Text or CDATASection node" should > include the element. in general isn't supported by the innerHTML spec -- for example, it would always introduce a new element. Is that a problem? -- Ian Hickson

Re: [whatwg] several messages about XML syntax and HTML5

On Fri, 8 Dec 2006, Sander Tekelenburg wrote: > > But it still leaves the question whether every browser will in fact be > HTML5 compliant. Apparently Apple, Mozilla and Opera have that ambition. > Smaller ones, like iCab and lynx, will just have to follow. But what > about Microsoft? I still ha

Re: [whatwg] PaceEntryMediatype

Ian Hickson wrote: Then the browser wouldn't take these links and make them available in a "list of feeds" interface, which is the problem we are trying to solve. Why is it useful for a browser to make a list of a bunch of random feeds that have no relation to one another or to the current

Re: [whatwg] several messages about XML syntax and HTML5

On Fri, 8 Dec 2006, Sam Ruby wrote: > > If one has a single non-presentational relationship that one wishes to > associate with a web page AND one has control over the HTTP headers that > are sent with said web page (e.g., because your blogging software is > written in PHP), then an HTTP header

Re: [whatwg] Common Subset

Replying to myself... Le 8 déc. 2006 à 8:48, Michel Fortin a écrit : and document.write() workaround: create nodes programatically and avoid the use of . Another noteworthy problem with the common subset about scripting is that it's really impractical to write some idioms. You can't have

Re: [whatwg] Inline SVG

Le 8 déc. 2006 à 15:20, Leons Petrazickis a écrit : Unlike Michel Fortin's proposal for , I suggest that SVG included like this be rendered as an image in that exact spot. We may want to define a default h

[whatwg] [WebApps] "html" start tag token in main phase

The root element phase dictates that any start tag (including "html") produces an element in the document and is then re-processed in the main phase. The main phase then states that if an "html" start tag token is encountered it produces a parse error -unless- it's the first start tag. Wo

Re: [whatwg] Inline SVG

On 12/8/06, Sam Ruby <[EMAIL PROTECTED]> wrote: Leons Petrazickis wrote: > > How about this for HTML5: > >http://www.w3.org/2000/svg";> > stroke-width="2" fill="red"/> > > > > And this for XHTML5: > > > > > If that's over-complicating the semantics of , we could > introduce a

Re: [whatwg] several messages about XML syntax and HTML5

At 16:13 + UTC, on 2006-12-08, Simon Pieters wrote: > From: Sander Tekelenburg <[EMAIL PROTECTED]> >>[...] But it still leaves the question whether >>every browser will in fact be HTML5 compliant. > > They probably won't, at least for the next few years. Right. That's a window of opportunity

Re: [whatwg] several messages about XML syntax and HTML5

Alexey Feldgendler wrote: LiveJournal, a popular blogging service, inserts hand-authored content into hand-authored templates. While the templates are written by competent authors who (mostly) know how to write proper HTML, blog posts are most often written by people who barely learnt how to

Re: [whatwg] several messages about XML syntax and HTML5

At 02:42 +1100 UTC, on 2006-12-09, Lachlan Hunt wrote: > Sander Tekelenburg wrote: >> [...] errors that result in 'good' looking pages in Explorer, and >> 'bad' in HTML5 browsers. Simply by producing code that they know will result >> in 'bad' pages when parsed in accordance with the HTML5 parsing

[whatwg] innerHTML for HTML and

The section "If the child node is a Text or CDATASection node" should include the element. -- Anne van Kesteren

Re: [whatwg] several messages about XML syntax and HTML5

At 17:05 +0200 UTC, on 2006-12-08, Rimantas Liubertas wrote: >> [...]undermine this entire effort by getting people to use authoring tools >>that on >> purpose contain errors that result in 'good' looking pages in Explorer, and >> 'bad' in HTML5 browsers. > > And how do you imagine Microsoft will

Re: [whatwg] Inline SVG

Le 8 déc. 2006 à 10:29, Leons Petrazickis a écrit : How about this for HTML5: http://www.w3.org/2000/svg";> Change for

Re: [whatwg] Inline SVG

Hi, From: "Leons Petrazickis" <[EMAIL PROTECTED]> How about this for HTML5: http://www.w3.org/2000/svg";> OBJECT has to be parsed as PCDATA for backwards compatibility, and introducing yet more features to an already overloaded element is probably not a good idea. However,

Re: [whatwg] Inline SVG

Leons Petrazickis wrote: On 12/7/06, Alexey Feldgendler <[EMAIL PROTECTED]> wrote: On Mon, 04 Dec 2006 13:55:32 +0600, Ian Hickson <[EMAIL PROTECTED]> wrote: >> http://intertwingly.net/stories/2006/12/02/whatwg.logo > Currently, there wouldn't be one. We could extend HTML5 to have some sort

[whatwg] Reserved class names

The spec says: A document must not use a class defined in the Wiki on an element other than the elements that the Wiki says that class name is allowed on. Does that mean that conformant documents can suddenly become non- conformant because a class it uses has been added to the Wiki with

Re: [whatwg] several messages about XML syntax and HTML5

Hi, From: Sander Tekelenburg <[EMAIL PROTECTED]> [...] But it still leaves the question whether every browser will in fact be HTML5 compliant. They probably won't, at least for the next few years. Historically all browsers have always had bugs in their implementations. But having a clear spe

Re: [whatwg] Inline SVG

On 12/7/06, Alexey Feldgendler <[EMAIL PROTECTED]> wrote: On Mon, 04 Dec 2006 13:55:32 +0600, Ian Hickson <[EMAIL PROTECTED]> wrote: >> http://intertwingly.net/stories/2006/12/02/whatwg.logo > Currently, there wouldn't be one. We could extend HTML5 to have some sort > of way of doing this, in

Re: [whatwg] several messages about XML syntax and HTML5

Sander Tekelenburg wrote: I still have the impression that they can undermine this entire effort by getting people to use authoring tools that on purpose contain errors that result in 'good' looking pages in Explorer, and 'bad' in HTML5 browsers. Simply by producing code that they know will resul

Re: [whatwg] several messages about XML syntax and HTML5

<...> Apparently Apple, Mozilla and Opera have that ambition. Smaller ones, like iCab and lynx, will just have to follow. But what about Microsoft? I still have the impression that they can undermine this entire effort by getting people to use authoring tools that on purpose contain errors that r

Re: [whatwg] several messages about XML syntax and HTML5

At 02:37 + UTC, on 2006-12-08, Ian Hickson wrote: > On Fri, 8 Dec 2006, Sander Tekelenburg wrote: [...] >> [...] >> >> "The error handling for parse errors is well-defined: user agents must >> either act as described below when enc

Re: [whatwg] several messages about XML syntax and HTML5

Ian Hickson wrote: On Thu, 7 Dec 2006, Sam Ruby wrote: They were made around the same time (Trackback was invented first). My point was just that Trackback is not a good example of why you need more attributes in HTML, since there are equivalent technologies that do it with existing markup and

[whatwg] Common Subset (was: several messages about XML syntax and HTML5)

Le 8 déc. 2006 à 0:08, Ian Hickson a écrit : On Fri, 8 Dec 2006, Alexey Feldgendler wrote: Recently, "" has been brought into the common subset of HTML5 and XHTML5. That's OK because browsers currently handle "" the same in HTML and XHTML, and will continue doing so. The same for xmlns a

Re: [whatwg] Psuedo classes based on DOM Events

On Tue, 05 Dec 2006 13:18:00 +0600, Rohan Prabhu <[EMAIL PROTECTED]> wrote: > i was just wondering, that in the Web Controls 1.0 specifications, in > the psuedo classes specifications, could it be that the psuedo classes > could also be the DOM Events which would modify the style information > at