Re: [whatwg] Footnotes, end notes, side notes

Le 2008-04-21 à 8:19, Ian Hickson a écrit : On Tue, 31 Oct 2006, Michel Fortin wrote: Interesting. If I understand well, this CSS proposal would allow a note inserted in the middle of a paragraph to become a footnote. For instance this: This paragraph has a footnoteThis is a footnote

Re: [whatwg] Feeedback on , , and other elements related to cross-references

define an abbreviation somewhere in the document and have it applied to each instance of this word through the document. Since abbreviations are defined on a per-document basis, presumably by the author, chances are they'll be all correct. [1]: http://michelf.com/projects/php-markdown/

Re: [whatwg] several messages about and related subjects

Le 2008-02-25 à 17:42, Ian Hickson a écrit : On Mon, 16 Jul 2007, Michel Fortin wrote: Since I'm not convinced that the current content model for is adequate [1], I decided to dig more examples where figures in HTML pages would be hard to fit with the current model. Here are the re

Re: [whatwg] several messages about , , , and related subjects

Le 2008-02-27 à 2:17, Ian Hickson a écrit : On Thu, 6 Apr 2006, Michel Fortin wrote: Le 6 avr. 2006 à 6:44, Alexey Feldgendler a écrit : This heading shouldn't be within the document's main tree of headings. It should be completely taken out, that's what "aside&quo

Re: [whatwg] My case for Ruby-elements

be better: Hello Salut ? I've included the "on" attribute assuming would be able to define alternatives based on something other than the "lang" attribute, although it's not really necessary considering only the current use case. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] My case for Ruby-elements

because a table seems capable of handling that case fine (fine visually, not necessarily semantically). Do you have any example? (Preferably real-world examples.) Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

[whatwg] All (new) sorts of figures

m/modules.php? name=Content&pa=showpage&pid=2&page=4> There is nothing in HTML allowing the illustrative content to be separated from the main content when it is made of HTML markup itself. Using or is not a very good as it relies on the visual rendering of these elements to be understood. A solution for that could be to allow caption-less figures with block- level HTML content, as in: Here is the result: This is a sample paragraph. Followed by another paragraph. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Entity parsing

onsume and the name of the entity. And not everyone can remember all those entity names. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Still more comments and questions on Web Apps 1.0

Le 2007-06-10 à 7:05, Anne van Kesteren a écrit : On Sat, 09 Jun 2007 23:03:54 +0200, Michel Fortin <[EMAIL PROTECTED]> wrote: I don't think XML does that, actually. See the first paragraph of http://www.w3.org/TR/xml/#syntax for the reason why this is so. White space outside t

Re: [whatwg] Still more comments and questions on Web Apps 1.0

Le 2007-06-09 à 5:26, Anne van Kesteren a écrit : On Sat, 09 Jun 2007 04:49:56 +0200, Michel Fortin <[EMAIL PROTECTED]> wrote: I'd agree they're mostly useless in a browser context, but when reading HTML with the intent of reserializing it later, preserving the white

Re: [whatwg] Still more comments and questions on Web Apps 1.0

ments and the root element can be beneficial for the readability of the final output. I'd keep them there, just like XML does. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

[whatwg] HTML5Lib Test Suite vs. PHP 5 HTML Parser

its HTML parser. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] CR "entities" and LFCR

se CR; but I'm not aware of any system using LF+CR (and there is none on Wikipedia) and I don't think it's useful to give a meaning to it. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Web Forms attributes: minlength / autocomplete

hose characters as you type? If that's not what you want (and I'm pretty sure it's not) I don't think such an attribute, if added, should be called minlength. Perhaps requiredlength or something like that would fit better. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] No-DOM HTML

Le 2007-06-02 à 4:39, Anne van Kesteren a écrit : On Wed, 30 May 2007 15:22:39 +0200, Michel Fortin <[EMAIL PROTECTED]> wrote: 3) Emit events until you reach a point where it may be possible that some events should be reordered, in which case you build a local DOM-like tree and wait

[whatwg] No-DOM HTML (was: should be allowed in )

t go past the head with this technique, unless you consider yourself in the innerHTML case and append them to the current node, as the spec requires. I guess this could be fine for parsing HTML snippets belonging to the body for instance. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Predefined classes are gone

"."{name} with NAME being {nmchar}+ and NMCHAR including the dash.) -- CSS 1 grammar: http://www.w3.org/TR/REC-CSS1#appendix-b Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Predefined classes are gone

syntax. I don't think in any way that this is incompatible with the predefined class names that were just removed (which I liked), it's just a little addition so you're not limited to the few predefined ones. The XHTML Role Module also has a couple of predefined global roles it seems. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Predefined classes are gone

ppropriate and others where it'd be better to start with a clean new attribute (role), but that's just a general feeling based on everything I've seen to date. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Feedback affected by the predefined classes being gone

Le 2007-05-17 à 1:17, Ian Hickson a écrit : On Tue, 20 Feb 2007, Michel Fortin wrote: I think it'd be useful to have that on rel values (link types) as well. On Wed, 21 Feb 2007, Michel Fortin wrote: The rel attribute is about links. What I meant by that is that I think it wou

Re: [whatwg] Sandboxing ideas

Le 2007-05-14 à 17:11, Alexey Feldgendler a écrit : On Mon, 14 May 2007 22:29:57 +0200, Michel Fortin <[EMAIL PROTECTED]> wrote: If you want the sandbox to degrade securely in older browsers, then this is not a solution. But I don't think there's a nice solution to tha

Re: [whatwg] Sandboxing ideas

around the inflated size of Base64, but otherwise it certainly is ugly and not human readable. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Sandboxing ideas

Le 2007-05-14 à 16:02, Jon Barnett a écrit : On 5/14/07, Michel Fortin <[EMAIL PROTECTED]> wrote: Le 2007-05-14 à 11:35, Alexey Feldgendler a écrit : > I'd treat these two problems as equally important. A separate HTTP > request per forum comment on the page is completely un

Re: [whatwg] Sandboxing ideas

Le 2007-05-14 à 11:35, Alexey Feldgendler a écrit : I'd treat these two problems as equally important. A separate HTTP request per forum comment on the page is completely unacceptable. What about encoding the content of each comment iframe in a "data:" URI? Michel Fortin [

Re: [whatwg] style='' on every element

hings for which you have something better to propose. Of course, nothing of this belongs in the spec. A conformance checker is free to warn about anything it wants. But systematically warning about style="" is not something I would find useful. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] style='' on every element

Le 2007-05-04 à 5:53, Henri Sivonen a écrit : Considering all the above, here's my concrete proposal for a solution: 1) Make style='' a global attribute. For the purposes of document conformance, make it conforming on all documents regardless how they came to being. 2) Include an informati

Re: [whatwg] Sequential List Proposal

a solution make the exercice pretty useless? Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Sequential List Proposal

ever needs to be inserted in the middle of the dialog. As an example: Me: ... and that was all I had to say. Someone else enter the room. Someone else: (thinking aloud) Wow! Otherwise, the spec tries to draw the line between what is and what is not a valid dialog... th

Re: [whatwg] List captions

I believe the markup should depend on what your list stands for. A list is not much unlike a paragraph: it's an enumeration formatted in a special way. So why can't we reuse the already existing structures? Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Sequential List Proposal

Le 2007-04-05 à 10:36, Simon Pieters a écrit : I get a 404 for this URI. Oops... sorry. <http://www.michelf.com/documents/whatwg/sequential-list/> Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

[whatwg] Sequential List Proposal

than one following a . is used for listing events other than speech and is used to insert time marks where appropriate. And you don't need to have any spoken part, meaning you can use it for system logs, or historical timelines too by using only and . Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Tendious use cases for

markup should accomodate this, but I think the rules ought to be flexible enough. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] on codecs in a 'video' tag.

pple can stay spec-compliant without having to fear submarine patents. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

[whatwg] Tendious use cases for

#x27;t say this is the ideal markup, but I think it's still better than opening and closing a dialog element each time you need a element. Any better way to markup these? Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

[whatwg] Figure without caption (was: Embedding Elements Should be Structured Inline-Level)

n illustration of the surrounding subject. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Embedding Elements Should be Structured Inline-Level

Ok, this is not conformant with the current spec since it's missing a legend, but in my opinion it should be allowed. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] One label: multiple fields

with , provides enough information to make the labels unnecessary. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] several messages about HTML5

ea. I can't say I dislike the idea though. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

[whatwg] Private class names (was: "several messages about HTML5")

Le 2007-02-21 à 16:58, Elliotte Harold a écrit : Michel Fortin wrote: t that, I would like to suggest that the current text be changed to reserve class names starting with a dash "-" for private use. That way that we would have a pool of class names which are guarantied to no

Re: [whatwg] Definition list and tables: what's the difference ?

e are many cases where both could be used as effectively, but there are many others where one makes much more sense than the other. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

[whatwg] Private class names (was "several messages about HTML5")

open for debate). It could certainly be scrapped altogether in the future, but in the meanwhile I want to improve it little by little. Maybe with enough incremental improvements like this one it'll become good enough for a majority of people. Michel Fortin [EMAIL PROTE

Re: [whatwg] several messages about HTML5

it-column-count. I think it'd be useful to have that on rel values (link types) as well. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Heading, binding, LH (was:XSLT: HTML 5 --> HTML)

some minor issues it seems to be evolving in the right direction. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] The m element

ing. And since the current specification has predefined class names, it could simply be added as one. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Fwd: Re: Heading, binding, LH (was:XSLT: HTML 5 --> HTML)

Le 2007-02-09 à 12:32, David Latapie a écrit : On Fri, 9 Feb 2007 11:40:32 -0500, Michel Fortin wrote: That was my idea of what you were doing. With this syntax there's no association between the description and the image, I'm not sure you caught that from my explanation though.

Re: [whatwg] The m element

no change in meaning) : reference marker (no change in meaning or importance) Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] De-emphasis

(or something similar)? I'm still not convinced that it is needed or that it can have a good default rendering, but it'd certainly be more to-the-point than the abstract concept of "de-emphasis" which can be stretched to dozens of unrelated use-cases. Michel Fortin [E

Re: [whatwg] De-emphasis

tract and harder to misuse than anything derived from "de-emphasis". Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Heading, binding, LH (was:XSLT: HTML 5 --> HTML)

finition group and no semantic association between the term and the definition. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] as a wrapper for inline content

he Text construct MUST be a single XHTML div element [XHTML] and SHOULD be suitable for handling as XHTML. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

[whatwg] in

graphs in for situational information and action descriptions? Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Semantic styling languages in the guise of HTML attributes.

ble manner. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Semantic styling languages in the guise of HTML attributes.

e HTML document if you have inline SVG. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] finding a number...

le dumb, but that's because it is, and I fully support making the attributes mandatory. At the very least, I think find-a-number should be limited to integer numbers. But even then it'll be limited to languages using our western digits and possibly not suitable for full inter

Re: [whatwg] microformats incompatible with WebApps 1.0 ?

Le 11 déc. 2006 à 21:25, Ian Hickson a écrit : On Mon, 11 Dec 2006, Michel Fortin wrote: http://microformats.org/wiki/hcard-profile"; class="vcard"> http://tantek.com/";>Tantek Çelik Technorati Given that nobody does the former, why would anyon

Re: [whatwg] microformats incompatible with WebApps 1.0 ?

efined as containing no colon, so that they can't be valid absolute URLs.) Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] microformats incompatible with WebApps 1.0 ?

Le 11 déc. 2006 à 20:37, Ian Hickson a écrit : On Mon, 11 Dec 2006, Michel Fortin wrote: I think we should keep both systems. Things worth registering in the global namespace because they're common and not very likely to be misused (like class names currently listed in the spec: ex

Re: [whatwg] microformats incompatible with WebApps 1.0 ?

t the Wiki idea is that it'll make conformance to HTML5 a moving target that would need to be reevaluated each time a new class is added on the Wiki. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

Re: [whatwg] Common Subset

Le 9 déc. 2006 à 7:50, Lachlan Hunt a écrit : Alexey Feldgendler wrote: The HTML5 spec could somehow officially bless CDATA only when used like this: // It would not harm because it is already interoperable. It's technically already allowed because script and style elemen

Re: [whatwg] Inline SVG

ses an interesting question about how you'd embed an XML application that itself features a element, since any </tt><tt> ends the parsing of the script element regardless of nesting. (The HTML parser just sees the XML as an opaque block of text.) You'd have to play with namespace prefixes: <my:script my:xmlns="..."> </my:script> Not the a very elegant solution however, and not very copy-paste friendly. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

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

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

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

[whatwg] Reserved class names

uot; is defined twice: as 3.5.1.2. and 3.5.1.3. Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

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

interesting part is the *additional* limitations it imposes, things with are supported by both but which cannot be expressed in a cross- compatible way. I've started a wiki page about the common subset: <http://wiki.whatwg.org/wiki/Common_Subset> Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

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

nd limited recommendation to keep backward compatibility. That's what I understand while reading the spec as a whole. If that's not what is intended, then maybe something should be done about that, like removing some of the incompatible features. Michel Fortin [E

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

ttered throughout many different files, which makes it difficult to update, the xmlns attribute occurs in one place, and that's usually in the same file as the DOCTYPE (in cases where templates are used). Michel Fortin [EMAIL PROTECTED] http://www.michelf.com/

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

Le 4 déc. 2006 à 14:33, Martin Atkins a écrit : Likewise, the content model of the element is "hardcoded" into the parser; there's no way to discover it from the syntax alone. (I'll admit that there's no similar construct to the content model of