Ian Hickson wrote:
On Tue, 19 Jul 2005, Christoph Päper wrote:
h2Your todo list:/h2
ol
/ol
...makes sense to me.
Traditionally empty items have been filled with N/A, ./., -,
(empty), none etc. or in this case maybe nothing to do. It's not
like HTML was the first system to reuire
Ian Hickson wrote:
On Tue, 19 Jul 2005, Olav Junker Kjær wrote:
But the notion of conformance is still quite useful to authors and
authoring tools. E.g. if a META-element without any attributes appears
in a document, its clearly due to an oversight or a bug in some tool, so
it would be
Would it be possible to add a print stylesheet to the specifications? Or perhaps
a global one although that is not stricly necessary. (PDF would be even cooler,
but I'm not sure if there are any good scripts for that you could add to the
publishing mechanism.)
--
Anne van Kesteren
On Wed, 20 Jul 2005, fantasai wrote:
One way of drawing the line might be, does dropping this requirement
result in a semantically-meaningful representation? An empty list
represents an empty list. But a meta without a 'name', or a link
without a 'href': these, per spec, represent
Dean Edwards wrote:
Matthew Raymond wrote:
1) The feature can be abused.
All features can be abused.
Yes, but some more than others.
2) It alters the standard behavior of the browser.
No it doesn't.
Uh, yes it does. Perhaps the problem is that CSS clouds the issue.
Since CSS is not
Any chance Web Forms 2 is going to say something about:
!DOCTYPE html
titleDefault value for size DOM attribute from the SELECT element/title
pselectoptionTest/select
script
alert(document.getElementsByTagName('select')[0].size);
/script
Firefox 1.8b3: -1.
Opera 8 and IE 6: 0.
Haven't been
Quoting Anne van Kesteren [EMAIL PROTECTED]:
Would it be possible to add a print stylesheet to the specifications?
Or perhaps
a global one although that is not stricly necessary. (PDF would be
even cooler,
but I'm not sure if there are any good scripts for that you could add to the
publishing
Matthew Raymond wrote:
| if (documentchanged) {
| printClone = document.clone();
| prepareForPrinting(printClone);
| }
|
| printClone.print();
This seems less practical than print events. It is also very difficult
to detect changes to the document. What do you mean by changes? Style
James Graham wrote:
The problem is if I state one thing explicitly, then people will want
something else stated (does it allow IDNs? does it allow UTF-8
characters? does it allow fragment identifiers?). Why should one
aspect of something be redundantly stated?
Because it's identified by
Dean Edwards wrote:
Matthew Raymond wrote:
Dean Edwards wrote:
Matthew Raymond wrote:
| if (documentchanged) {
| printClone = document.clone();
| prepareForPrinting(printClone);
| }
|
| printClone.print();
This seems less practical than print events.
I don't see how:
|
On Wed, 20 Jul 2005, Anne van Kesteren wrote:
Say I load this file through a DATA attribute of a SELECT element:
xh:select xmlns:xh=http://www.w3.org/1999/xhtml;
xh:optionFAIL/xh:option
foo xmlns=tag:example.org,2005:/test
xh:option selected=selectedPASS/xh:option
/foo
/xh:select
11 matches
Mail list logo
