Re: [whatwg] What exactly is contentEditable for?

rea though, since it seems a bit strange to toggle the content model of an element based on an attribute) regards Olav Junker Kjær

Re: [whatwg] What exactly is contentEditable for?

content rather than just plaintext as . In any case, this is a different use case than the case for contentEditable. Regards Olav Junker Kjær

Re: [whatwg] What exactly is contentEditable for?

eful, despite its shortcomings. regards Olav Junker Kjær

[whatwg] removing attributes

Is it possible to remove a constraint like maxLength (on input elements) through script, eg. by setting it to null? By default a field does not have any maxlength constraint, so it would seem natural that if you set a constraint through script, it could be removed again. regards Olav Junker

Re: [whatwg] WA1: attribute requirements

handle it somewhat gracefully (by ignoring it). regards Olav Junker Kjær

Re: [whatwg] [html5] window.print() undefined

Dean Edwards wrote: Fair enough. But in all the browsers I've tried when "Print Preview" is selected the normal browser window disappears and is replaced with a new window to show the preview. This is not instantaneous. The WHATWG takes notice of real-world browsers does it not? FWIW, in IE t

Re: [whatwg] [html5] window.print() undefined

Dean Edwards wrote: IE has some nice onbeforeprint/onafterprint events. Can we add these too? Arent these event mostly used to transform the view before printing it? I think this is better handled by a print-specific style-sheet today. regards Olav Junker Kjær

Re: [whatwg] [html5] window.print() undefined

Btw, in HTML5 class name handling is easier through the DOMTokenString interface, you just write: element.classNames.add("somethingThatIsOnlyVisibleOnScreen") /olav

Re: [whatwg] [html5] window.print() undefined

Dean Edwards wrote: That's not really the point. It could be any style setting that is assigned using script. The real problem is that styles assigned directly using element.style.something (or using the style html attribute) cannot be different for different medias. Print-events are not real

Re: [whatwg] [html5] window.print() undefined

Dean Edwards wrote: If I set element.style.display = "block" how do I hide it using a style sheet when it is printed? I dont think you should set element.style.display to "block", if the element should be visible only on screen and not in print. It would be better to dynamically assign it a c

Re: [whatwg] Input type=date UI discussion

Jim Ley wrote: Cool, any chance of it saying that ie defining the terms - specifically including automated submission tools, e.g. Opera with a script extension which submitted the form must also cause a click event to fire on the first form element for that Opera to remain conformant. I think t

Re: [whatwg] Input type=date UI discussion

f the spec is that a form must always be submitted by a specific button. So if your UI allows you to submit a form e.g. by clapping your hands once, the onclick event is still fired on the default button and the name=value of the button is still submitted. Olav Junker Kjær

Re: [whatwg] Input type=date UI discussion

Dean Edwards wrote: - Date widget appearance: Once the date chooser popup widget has been dismissed, the date in its correct localized format will be displayed I agree but localisation is hard for us. I'm not sure how we are doing that yet. Olav? Thats the easy part. Using the built-in toL

Re: [whatwg] Web Forms as data schema language

a HTML-described interface. regards Olav Junker Kjær

Re: [whatwg] [WA1] - The Selection List element

ected or :checked psuedo-classes), but thats a different issue. regards Olav Junker Kjær

[whatwg] Submit buttons

e button. It could be solved by requiring that submit buttons (and input type=image) may only be associated with a single form at a time. regards Olav Junker Kjær

Re: [whatwg] A thought:

thing or subscribe to a mailinglist or whatever. I think this coupling between protocol and UI is one of the great ideas of the web. So a link which performs a unsafe action is not just wrong according to HTTP, its also bad UI. regards Olav Junker Kjær

Re: [whatwg] Drag and drop in HTML5

and press space, shouting the label on the element) is media dependent. regards Olav Junker Kjær

Re: [whatwg] charset attribute of HTMLScriptElement

Wouldn't it be safer to declare the encoding in the js file itself? It could be in a magic comment at the start of the document: //@charset("utf8") Not very elegant, but less error prone than to specify the encoding everywhere the file is included. regards Olav Junker Kjær Tos

Re: [whatwg] text/html flavor conformance checkers and

is always either HTML or XHTML dependent on the mime type. regards Olav Junker Kjær Henri Sivonen wrote: What should text/html flavor conformance checkers say about ? Silently treat as > as per SGML? Silently treat as as per real world? Report a warning? Report an error? What about ? I am lean

Re: [whatwg] Canvas element - Keep It Simple

is perceived as proprietary, and because Flash has an even wider penetration (and better tools). regards Olav Junker Kjær

Re: [whatwg] Updating Location Bar for RPC Type Apps

anging to a new bookmarkable state on the client side without reloading the page. regards Olav Junker Kjær

[whatwg] Canvas element

spec which is intended to cover *web* applications. SVG is at least usable in IE through a plug-in for IE, but realistically, anyone who needs interactive vector graphics on the web is going to use flash. regards Olav Junker Kjær

[whatwg] Editing

aps the execCommand-style interface should be replaced with something consistent with the WA1 Command interface. regards Olav Junker Kjær

[whatwg] Fear of scope creep

latform for web *applications*, as an open and (potentially) widely implemented alternative to XUL, XAML etc? regards Olav Junker Kjær

Re: [whatwg] Web Forms 2.0 submission to W3C

echnically cover the same ground but which are optimized for different use cases. A closer cooperation and sharing of ideas between XForms and WF2 communities will certainly be a boon for everyone. In the end, HTML extensions do belong in the W3C. So I'll be optimistic now! regards Olav Junker Kjær

Re: Call four comments 4 is out (Was: [whatwg] Web Forms 2.0 submission to W3C)

eatures, but also as documentation of the intention of the spec. Often I understand a feature better by reading the use case, rather than by reading the precise specification. regards Olav Junker Kjær

Re: [whatwg] Web Forms 2.0 submission to W3C

ing for it compared to XForms. Or am I to pessimistic? regards Olav Junker kjær

Re: [whatwg] Web Forms 2.0 submission to W3C

? Olav Junker Kjær

Re: [whatwg] multiple forms submit

et buttons must *reset* all the forms they are associated with." :-) Olav Junker Kjær

[whatwg] multiple forms submit

form at a time. (Along the same line, hitting enter when focus is in a text field should only submit one form.) regards Olav Junker Kjær

Re: [whatwg] [html5] tags, elements and generated DOM

xcept some specific doctypes which is defined as triggering quirks mode. More specificly, it seems that standards mode is triggered by the string If the regards Olav Junker Kjær

Re: [whatwg] [html5] tags, elements and generated DOM

missing might be annoying but wont usually have serious consequences in HTML (XHTML is different, of course). Still, this is the only type of error DTD validation will catch. regards Olav Junker Kjær

Re: [whatwg] [html5] tags, elements and generated DOM

ode in browsers, so we might as well put the doctype to some use. regards Olav Junker Kjær

Re: [whatwg] [html5] tags, elements and generated DOM

lly I think it would be beneficial for interoperability and perhaps discovery of weaknesses in the spec, if several schemas were developed by independent parties during the call for implementation. regards Olav Junker Kjær

Re: [whatwg] [html5] tags, elements and generated DOM

will cause more authors to check their pages. regards Olav Junker Kjær

Re: [whatwg] WhatWG spec addition? (fwd)

:nth-child pseudo-class. regards Olav Junker Kjær

Re: [whatwg] Repetition Model

Dean Edwards wrote: Yes you would have to iterate over each element to attach the repetition template interface. Olav Junker Kjær provided a solution to this speed this up a little: It should be said that the expression-based solution improves the initial rendering, but slows the page

Re: [whatwg] Repetition Model

Dean Edwards wrote: It was my understanding (from reading previous threads) that there were still some misgivings about the repetition model. There doesn't seem to be too much discussion about the repetition model. I think the reason some suggest dropping it from the spec, is that they would li

Re: [whatwg] WF2 changes: uri->url, ERROR_* constants dropped; status update

d it might make both specs clearer and more focused. regards Olav Junker Kjær

Re: [whatwg] [wf2] type="url"

RI), go for URL. regards Olav Junker Kjær

Re: [whatwg] [WF2] Objection to autocomplete Attribute

nput data is sensitive. (the recommended default UI in UA's that support autocompletion would still be as described in the spec). Of course the name will be slightly misleading now, but thats not a big deal. "checkbox" is also a name that suggest an UI representation, but the semantics is still defined as UI neutral. regards Olav Junker Kjær

Re: [whatwg] Introducing new elements is expensive

g deal, though, since we can just avoid giving the field a name attribute. Regards Olav Junker Kjær

[whatwg] WF2 section A

ould be "the *change* event..." The HTMLFormElement has the dispatchFormChange() method while the corresponding method on form controls is called dispatchFormChanged() (with a "d"). However in section 7.12 the method on HTMLFormElement is called dispatchFormChanged() (with a "d"). regards Olav Junker Kjær