Re: [whatwg] [WA1] is semantic

te to use, for instance, # # (a) foo # (b) bar # (c) baz # ...where the name of the item is more important than the order? If so, that this satisfies my conserns. Thanks. [1] http://www.access-matters.com/2005/10/01/quiz-118-alt-text-or-title-text/ [2] http://www.simplebits.com/notebook/2004/08/13/sq_conclusion.html Regards, Simon Pieters

[whatwg] ' in text/html

ernet Explorer 5.2 * Netscape Navigator 4.78 Should "'" be a valid charater reference in text/html? If not, what would be correct error handling? [1] http://zcorpan.1go.dk/test/apos.html [2] http://www.browsercam.com/view.aspx?proj_id=201638 Regards, Simon Pieters

Re: [whatwg] WA 1.0 and WF 2

tiple documents. Regards, Simon Pieters

[whatwg] triggers standards mode

ct.dtd";> triggers standards mode, while triggers quirks mode. [1] http://xml.coverpages.org/sgmlsyn/sgmlsyn.htm#P110 [2] http://zcorpan.1go.dk/test/html/doctype/ Regards, Simon Pieters

[whatwg] [WF2] Example not well-formed

Hi, This example[1] should probably be something along the lines: http://search.example.com/";> [1] http://whatwg.org/specs/web-forms/current-work/#extensions2 Regards, Simon Pieters

[whatwg] [WF2] Example should have labels

Hi, This example[1] should probably have labels: Name: required="required"/> Comment: [1] http://whatwg.org/specs/web-forms/current-work/#the-required Regards, Simon Pieters

[whatwg] [WA1] INS/DEL and omitted tags

; rv:1.9a1) Gecko/20051120 Firefox/1.6a1 foobar Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) foobar innerHTML for the first P: foo innerHTML for INS: bar innerHTML for the second P: bar Regards, Simon Pieters

[whatwg] Test suite: Embedded content

; filename=pass.class" didn't work, neither did "Content-Location: pass.class". Suggestions?) Regards, Simon Pieters

Re: [whatwg] Test suite: Embedded content

d with the frame if they are not, but should only show for 200 and 301-200; other codes should cause the fallback content to show. Ok. I doubt HTML5 will have . Then I won't go though the hassle. :) BTW it is spelt "response". Thanks. Fixed. Regards, Simon Pieters

Re: [whatwg] Test suite: Embedded content

isable plugins, so they are treated as Opera's "plugins enabled" behaviour. IE: Same as Firefox. Regards, Simon Pieters

Re: [whatwg] Test suite: Embedded content

> I can't find a way to disable plugins, so they are treated as Opera's "plugins > enabled" behaviour. > > IE: > Same as Firefox. Wow, pretty reasonable interoperability. I guess Opera's behaviour is what we should head for, then, making disabling of plugins optional. Alright. Regards, Simon Pieters

Re: [whatwg] Test suite: Embedded content

sers do now. Perhaps CDATA is faster than #PCDATA. , and works the same. Regards, Simon Pieters

[whatwg] After attribute name state

ble is the same as contenteditable="true" (at least in IE, not in Opera). There are probably some other exceptions aswell. [1] http://whatwg.org/specs/web-apps/current-work/#after Regards, Simon Pieters

[whatwg] The HTML namespace

Hi, The Namespaces section[1] currently says: The HTML namespace is: http://www.w3.org/1999/html I guess that should probably be "http://www.w3.org/1999/xhtml";. [1] http://whatwg.org/specs/web-apps/current-work/#namespaces Regards Simon Pieters

Re: [whatwg] Menus, fallback, and backwards compatibility: ideas wanted

it offers, and WHOOSH, there it is ;) I believe the spec already covers this with the element type. The UA could simply hide the contents of all NAV elements, and then show them when you click your "nav" button. It doesn't really matter if that is implemented with CSS or in some other manner... Regards, Simon Pieters

[whatwg] DOCTYPE name state

;T"|"t","M"|"m","L"|"l"] should be correct. I browsers I'm aware of that do doctype switching will use their standards mode for all case combinations. [1] http://www.whatwg.org/specs/web-apps/current-work/#doctype0 Regards Simon Pieters

Re: [whatwg] Should ID be required for ?

, this issue is covered by XPointer. http://www.w3.org/TR/xptr-xpointer/#stringrange Regards, Simon Pieters

[whatwg] Use instead of

f we use , Google is already (partially) compliant. ;-) [1] http://whatwg.org/specs/web-apps/current-work/#the-m Regards, Simon Pieters

[whatwg] Bogus comment treated as a real comment in Mozilla

ASS I think that Opera is correct and that Mozilla is wrong, but I wanted to send this to the list before I file a bug. Regards, Simon Pieters

Re: [whatwg] , , ,

ing CSS: head { display:block; text-align:center; } title { display:inline; } If you use (or , or ) you are still duplicating the , no? Regards, Simon Pieters

[whatwg] Allow as a child of

ot; attribute is not needed in this example. This also happens to be backwards compatible with legacy UA's. Is there a reason to disallow this sort of nesting? [1] http://whatwg.org/specs/web-forms/current-work/#formAttribute Regards, Simon Pieters

Re: [whatwg] Allow as a child of

x27;m considering dropping form="" altogether, as part of a WF2 simplification effort, in response to feedback from Mozilla and Apple about WF2 being too much too soon.) I don't think we should drop the form="" attribute, it has it's uses aswell. Regards, Simon Pieters

Re: [whatwg] Allow as a child of

; is already implemented in Opera 9 build 8031, if I'm not mistaken.) [1] http://zcorpan.1go.dk/test/html/table-form/ Regards, Simon Pieters

[whatwg] [WF2] Label with empty for attribute

Hi, It is not defined what should happen when a label has an empty for="" attribute. Consider the following example: foo Is the label element part of the .labels DOM attribute for the input? What should the label's .control DOM attribute return? Regards, Simon Pieters

Re: [whatwg] Definition of alt= attribute

e in some cases, such as: ...but not in others, such as: Regards, Simon Pieters

Re: [whatwg] Comment Syntax and Parsing

uirks comment parsing code for standards mode aswell. Regards, Simon Pieters

[whatwg] Attributes, namespaces and language determination

t-work/#terminology Regards, Simon Pieters

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

here's much advantage of differentiating between "well-formed" and "malformed" markup. They should be parsed the same to keep things simple and predictable. Thus, XY should be parsed as: BODY + EM + P + EM + #text: XY ...IMHO. Regards, Simon Pieters

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

ry, so it really doesn't matter. When do you insert the EM element node to the DOM? Should the parser wait with inserting it until it knows what comes next? I think it makes more sense to just insert the element when you have parsed the start tag, regardless of what comes next. Regards, Simon Pieters

Re: [whatwg] Google research into web authoring techniques

use a tag and then not put any cells in it, please let us know. Perhaps to simulate 'min-width', something like this: Text... [1] http://code.google.com/webstats/2005-12/tables.html Regards, Simon Pieters

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

Hi, From: Ian Hickson <[EMAIL PROTECTED]> This breaks in the face of , sadly (see my earlier mail). Otherwise I'd agree. Ok. Then what Safari does makes most sense to me. What Mozilla does seems too complicated and unpredictable. Regards, Simon Pieters

Re: [whatwg] Parsing: Tokenisation - DOCTYPE State

It doesn't seem to be necessary because of the last step in the DOCTYPE name state that says: [...] You might not get to the doctype name state. (Consider .) Regards, Simon Pieters

[whatwg] Serialize comments that contain "-->"

izer insert a space in between ("- ->")? [1] http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-1728279322 Regards, Simon Pieters

Re: [whatwg] Update to the Adoption Agency Algorithm

u can select a piece of text and view selection source, which will bring up the serialized DOM. Browsers could also log all HTML parse errors in a console, just like Firefox currently logs CSS parse errors and XML parse errors in the JavaScript Console. Regards, Simon Pieters

Re: [whatwg] getElementsByClassName()

s not needed for this use case. Regards, Simon Pieters

[whatwg] Doctype, "html" or "HTML"

DOCTYPE name state[2], won't the name always be "HTML"? [1] http://whatwg.org/specs/web-apps/current-work/#the-initial1 [2] http://whatwg.org/specs/web-apps/current-work/#doctype0 Regards, Simon Pieters

Re: [whatwg] Empty elements

Hi, From: David Hyatt <[EMAIL PROTECTED]> Also, is actually supported even in HTML by Firefox and Safari. I think they do a reparse when they hit EOF if they're in script parsing mode. That should probably be abadoned for the same reason as comments shouldn't be reparsed.

[whatwg] typo: opttion

Hi, There's a typo in the How to handle tokens in the main phase[1] section: An end tag token whose tag name is "option" If the current node is an opttion [...] [1] http://www.whatwg.org/specs/web-apps/current-work/#how-to Regards, Simon Pieters

Re: [whatwg] HTML5 Parsing spec first draft ready

t;;, </tt><tt>"lang", "x-pass"); </tt><tt>document.body.firstChild.firstChild.data = "This page should have a </tt><tt>green background."; </tt><pre style="margin: 0em;"> Why should the lang attribute (in the null namespace) take precedence in HTML? [1] http://whatwg.org/specs/web-apps/current-work/#terminology Regards, Simon Pieters

Re: [whatwg] several messages on alternative spellings for/

ot;Less" should be "higher". Regards, Simon Pieters

Re: [whatwg] draft

in allowing different formats in the value="". Regards, Simon Pieters

Re: [whatwg] draft

to have a value="" attribute, because you might want to have both plain text and an indicator, as can be seen in Hotmail: 12% of 250 MB Regards, Simon Pieters

[whatwg] Do we want reparsing of ?

ms to just drop everything after the , resulting in a blank page), so I doubt that many pages rely on this reparsing. [1] http://whatwg.org/specs/web-apps/current-work/#data-state [2] http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2006-January/005552.html Regards, Simon Pieters

Re: [whatwg] hello list

l [2] http://whatwg.org/specs/web-apps/current-work/#parsing Regards, Simon Pieters

Re: [whatwg] image captions

e this: caption [1] http://www.w3.org/MarkUp/HTMLPlus/htmlplus_35.html Regards, Simon Pieters

[whatwg] Doctype conformance requirements

owing DOCTYPE: . Such documents that are served over the wire (e.g. by HTTP) must be sent as text/html. [1] http://whatwg.org/specs/web-apps/current-work/#conformance Regards, Simon Pieters

Re: [whatwg] Test suite: Embedded content

Hi, From: Ian Hickson <[EMAIL PROTECTED]> On Mon, 28 Nov 2005, Simon Pieters wrote: > > I've created a test suite for , , / and > with the data types image/png, text/plain, text/html, > application/xml and application/x-shockwave-flash, with the HTTP > responces 200,

[whatwg] Authoring tools and presentational markup

there's no other suitable element type for the purpose and bold or italics is the typographical convension for the purpose. [1] http://accessifyforum.com/viewtopic.php?t=5096 Regards, Simon Pieters

[whatwg] Markup errors in example

Hi, The example for [1] seems to have a markup error: Progress: 0% Should the start tag be there? In the same example there's also this: < ...which probably should be "". [1] http://whatwg.org/specs/web-apps/current-work/#the-progress Regards, Simon Pieters

[whatwg] Parse error for "--" in comment end state?

Hi, Shouldn't the Anything else entry in Comment end state[1] be a parse error? As written, the following is allowed: I thought it shouldn't for compability with the "SGML comments" implementations. [1] http://whatwg.org/specs/web-apps/current-work/#comment1 Regards, Simon Pieters

Re: [whatwg] Parse error for "--" in comment end state?

ters and the input character to the comment token's data. Switch to the comment state. ...to say: Anything else Parse error. Append two U+002D HYPHEN-MINUS (-) characters and the input character to the comment token's data. Switch to the comment state. Regards, Simon Pieters

[whatwg] On accessibility

if I notice an accesskey on a site I visit often, I make use of it. I would disagree with [HTML5 dropping accesskeys] more than longdesc. accesskeys, are really useful, and again I tend to use them whenever I come across them. it's a shortcut to get to where you want to go, instead of having to search for it. Regards, Simon Pieters

[whatwg] About adopting quirks mode parsing

his if we want to be more compatible with IE. What do others think? Do we want to be more compatible with quirks mode parsing? [1] http://whatwg.org/specs/web-apps/current-work/#the-initial1 Regards, Simon Pieters

Re: [whatwg] Where did the "rev" attribute go?

r/ Regards, Simon Pieters

Re: [whatwg] About adopting quirks mode parsing

Hi, From: Ian Hickson <[EMAIL PROTECTED]> On Sun, 18 Jun 2006, Simon Pieters wrote: > > The spec asks whether quirks mode parsing should be adopted[1]. I think > it would be good if parsing worked more or less the same in quirks and > standards mode. If we want to adopt q

Re: [whatwg] About adopting quirks mode parsing

Hi, From: Ian Hickson <[EMAIL PROTECTED]> On Mon, 17 Jul 2006, Simon Pieters wrote: > As for an algorithm for how to do that, I think that an extra flag would > be sufficient. If the parser hits the flag sets to > false. Initially the flag is false. While the flag is true the

[whatwg] Parsing entities

you also have to reparse the "i;", right? Unless I'm mistaken the spec doesn't say anything about that. [1] http://www.google.com/search?q=R%26eacutesum%C3%A9 Regards, Simon Pieters

Re: [whatwg] Parsing entities

Hi, From: Ian Hickson <[EMAIL PROTECTED]> On Mon, 14 Aug 2006, Simon Pieters wrote: > > I guess that for compat with IE and the Web[1] we have to treat > "Résumé" as if it were "Résumé". So how do we > handle "¬i;"? When the parser has come as fa

Re: [whatwg] Parsing entities

quot;. Ok. So the "i" is not consumed, just peeked at. Only when you see "¬in" then you consume the "i" and "n" aswell. That was a bit unclear to me at first. Regards, Simon Pieters

Re: [whatwg] href on any element

-whatwg.org/2006-January/005410.html Regards, Simon Pieters

[whatwg] Scoped tabindex proposal

ibute is a scoping element, so that authors can use tabindex="-1" on the table instead. Here's a pointer of where this (or something similar) is called for: http://accessifyforum.com/viewtopic.php?t=6034 Regards, Simon Pieters

Re: [whatwg] Scoped tabindex proposal

1 3 2 I can agree with tabindex="scoped" - it's good enough too. But how do you deal with the .tabIndex DOM attribute? It can't be long and DOMString at the same time. Changing it to DOMString might break some sites. Currently, if you for instance do: documen

Re: [whatwg] Scoped tabindex proposal

tabindex="2" on #container1. I think this makes more sense than changing tabIndex to a DOMString, and it is more flexible. Regards, Simon Pieters

Re: [whatwg] Scoped tabindex proposal

tabindex 11, 21, 12, 22 and 30. Regards, Simon Pieters

Re: [whatwg] Scoped tabindex proposal

nested tabindex elements, and the ability to declare unfocusable scoping elements. Third, magic values are less readable. It's voodoo. Ok. Regards, Simon Pieters

[whatwg] [WF2]

ith radio buttons instead, but why can't the above be supported? That is, make required apply to s and if the value is empty then required is not satisfied. (Same for .) (I realise that radio buttons and checkboxes satisfy required even if the value is empty.) Regards, Simon Pieters

[whatwg] innerHTML and QNames

-html/demo.htm However, it seems IE does return the QName for elements and attributes...: http://simon.html5.org/test/html/dom/the-document/dynamic/in-html/ie-demo.htm I'd rather the spec followed Opera and Firefox here though (i.e., use the local name). Regards, Simon Pieters

Re: [whatwg] [WF2]

Hi, From: Robert <[EMAIL PROTECTED]> On Mon, 02 Oct 2006 16:35:32 +0200, Simon Pieters <[EMAIL PROTECTED]> wrote: Submitting an empty value may be wanted, Then don't mark the select as being required. Or do you mean that there are cases where the user has to change the

[whatwg] semantics (and dialogue)

uct/lists.html#h-10.1 [3] http://whatwg.org/specs/web-apps/current-work/#the-blockquote Regards, Simon Pieters

[whatwg] Parsing MathML in HTML5

is not MathML: x The following is MathML: http://www.w3.org/1998/Math/MathML";> x+2 This is still MathML and is not an empty element Please cc any other lists as appropriate. Regards, Simon Pieters

Re: [whatwg] Parsing MathML in HTML5

ng content and future MathML. If the latter, well, to ease authoring of MathML? Regards, Simon Pieters

[whatwg] scope

that when applies to the element also applies to the entire document? Regards, Simon Pieters

[whatwg] Map lang to xml:lang at the parser level

. This would make it simpler to set/get the language with script in XHTML (no need to use namespace-aware methods). I don't know if this is too expensive on the parser or if there are other flaws but it's just an idea. Regards, Simon Pieters

[whatwg] Parsing: Disallow slashes in unquoted attribute values?

to the HTML5 parsing algorithm (and goes without parse errors). But according to SGML (assuming the HTML4 doctype and the SGML declaration for HTML4) it's equivalent to: >test Regards, Simon Pieters _ Satsa på en romant

[whatwg] [wf2] Comments in textarea

(ignoring the weird "pseudo-comment" parsing). [1] http://whatwg.org/specs/web-forms/current-work/#handling Regards, Simon Pieters _ Eragon på vita duken 15/12! http://www.msn.se/noje/eragon/

Re: [whatwg] Table integrity and conformance

ta cells and header cells if they have scope="" or have headers="" pointing at them. Regards, Simon Pieters _ Sök bilder på glammiga kändisar! http://search.msn.se

[whatwg] Getting .innerHTML in XML well-formedness issues

http://whatwg.org/specs/web-apps/current-work/#dynamic1 Regards, Simon Pieters _ Dags att flytta till större? http://sokbostad.msn.se

[whatwg] Cross-reference elements

nce, and not be used for e.g. phrases in foreign languages in general. (I'd use for that.) [1] http://whatwg.org/specs/web-apps/current-work/#the-x Regards, Simon Pieters _ Sök bilder på glammiga kändisar! http://search.msn.se

Re: [whatwg] Allow as a child of

ld make form="" redudant for that use-case. Obviously form="" has other use-cases, but if implementors don't want it yet it can perhaps wait to WF3... I don't have strong opinions about form="", I only know that "works" in all browsers while form=

Re: [whatwg] Allow as a child of

ning is a giant hack, not something that IMHO we should condone. Indeed. Again, I'd love to do this. I just don't see _how_ to do it within the constraints of a sane DOM, without a huge amount of work both in updating specs (like CSS

Re: [whatwg] How not to fix HTML

omething, and use that as the "legend" for the radio group. (I'm not saying this algorithm is fool-proof, just saying that we don't necessarily need to change the markup to solve this issue.) Regards, Simon Pieters _ Eragon på vita duken 15/12! http://www.msn.se/noje/eragon/

Re: [whatwg] Form Control Group Labels

new stuff to do the same thing. (Also make s more CSS-friendly in graphical browsers so authors cal use it more.) [...] Regards, Simon Pieters _ Ladda ner höstens sköna låtar! http://www.msn.se/music

[whatwg] s/A tfoot element/Zero or one tfoot elements/

be a tfoot element. [1] http://whatwg.org/specs/web-apps/current-work/#the-table Regards, Simon Pieters _ Windows Live Messenger 8.1 Beta är här! http://get.live.com/messenger/overview

[whatwg] Why does allow block-level elements?

lock-level elements in that doesn't apply to or as well? [1] http://whatwg.org/specs/web-apps/current-work/#the-th Regards, Simon Pieters _ Sök bilder på glammiga kändisar! http://search.msn.se

[whatwg] Questions about headings and sections

;t such documents be non-conforming or at least such usage be considered discouraged? [1] http://whatwg.org/specs/web-apps/current-work/#outlines Simon Pieters _ Beyoncé live-konsert på MSN 15/11 2006 http://msnpresents.msn.com/Beyonce/?mkt=sv-se

[whatwg] Shouldn't empty s be allowed?

D&remove=%5Bplayer%5D [1] http://whatwg.org/specs/web-apps/current-work/#the-tbody Regards, Simon Pieters _ Hitta formen http://www.msn.se/halsa/

[whatwg] Allow omitting ="" for attributes?

y alt text (). Pros: * Three characters less to type. Cons: * Less obvious which attributes are boolean attributes and which are not by looking at the source. Regards, Simon Pieters _ Sök bilder på glammiga kändisar! http://search.msn.se

Re: [whatwg] Allow omitting ="" for attributes?

http://syntax.whattf.org/ Regards, Simon Pieters _ Dela med dig av foton på Windows Live Spaces http://spaces.live.com/

Re: [whatwg] Allow omitting ="" for attributes?

Hi, From: "Charles Iliya Krempeaux" <[EMAIL PROTECTED]> What's the "whattf"? Web Hypertext Application Technology Task Force. Regards, Simon Pieters _ Beyoncé live-konsert på MSN 15/11 2006 htt

[whatwg] Only allow s as children of

e.ch/specs/html/usemap-alt Regards, Simon Pieters _ Sök snyggingar där du bor http://match.se.msn.com

[whatwg] rel="" on and dosn't create a hyperlink

ot;it creates a hyperlink" above should be removed. [1] http://whatwg.org/specs/web-apps/current-work/#other Regards, Simon Pieters _ Allt om Tom Cruise och Katie Holmes http://starlounge.msn.se/

[whatwg] HTML syntax: space characters between attributes

x27;d suggest either making it a parse error or change the syntax to make it optional. (But obviously it can't be optional when the preceding attribute is minimized or unquoted.) Regards, Simon Pieters _ Prenumerera på senaste mu

[whatwg] Parsing (and syntax): < in unquoted attribute values

If not, should it still be a parse error (and be disallowed in the syntax section)? Regards, Simon Pieters _ Eragon - äventyret börjar 15 december! http://www.msn.se/noje/eragon/

[whatwg] HTML syntax: Missing "#" for numeric entities

Hi, Decimal numeric entities and hexadecimal numeric entities start with "&#", but according to the syntax section they only start with "&". http://whatwg.org/specs/web-apps/current-work/#chara

[whatwg] HTML syntax: , and omission

xists with different combinations of thead, tbody and tfoot, and they don't have the same name. I think this is better fixed by talking about start tags instead of elements (except for parent elements). Regards, Simon Pieters _ A

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

rsion. So now I'm starting to think that trailing slashes for void elements should be allowed in HTML5. Regards, Simon Pieters _ Facklor och eldar i trädgården http://alltombostad.msn.se/

Re: [whatwg] Inferring rel="feed" from the media type

k to an alternate representation of the current document in application/atom+xml format that is not a syndication feed. IMHO introducing new rel keywords is an uglier hack than just omitting the type="" attribute. Regards, Simon Pieters __

[whatwg] Editorial: Move and to Paragraphs

Hi, Shouldn't The address element and The figure element sections be moved to the Paragraphs section? Regards, Simon Pieters _ Martin Stenmarck som ringsignal http://msn.cellus.se/

[whatwg] HTML syntax: Tag omission and attributes

Hi, It is obvious, but should still be specified that start tags with attributes can't be omitted. Regards, Simon Pieters _ Leta bloggar om dina intressen http://spaces.live.com/default.aspx?page=Interests&ss=False

[whatwg] Editorial: Tag omission

start tags mention "the head element", should be replaced with the relevant entry's element instead. The entry has a markup error (s///). Regards, Simon Pieters _ Hitta bloggar om dina intressen http://spaces.live.c

  1   2   3   4   5   6   7   8   >