On Thu, 2008-12-18 at 14:41 +1300, Robert O'Callahan wrote:
Currently HTML5 does not require media elements to delay the load
event in any way. We certainly don't want to delay the load event
until the entire resource has finished loading (as we do for images),
but I think it would make sense
On Thu, Dec 18, 2008 at 9:57 PM, Philip Jägenstedt phil...@opera.comwrote:
On Thu, 2008-12-18 at 14:41 +1300, Robert O'Callahan wrote:
Currently HTML5 does not require media elements to delay the load
event in any way. We certainly don't want to delay the load event
until the entire
Quotations in the context of an article usually consist of three
elements:
* the actual quote
* the author of the quote
* the citation source
For two of these parts, there is markup; however, for the author, there
is none. I have no reason to believe that the author is of
Nils Dagsson Moskopp wrote:
Quotations in the context of an article usually consist of three
elements:
* the actual quote
* the author of the quote
* the citation source
For two of these parts, there is markup; however, for the author, there
is none. I have no reason to
Ian Hickson schrieb:
On Wed, 17 Dec 2008, João Eiras wrote:
While I myself don't find any decent use case for positioning the
window, I think sizing the popup is a common and useful use case,besides
controlling other aspected already covered by window.open(). Because the
behavior for the
Ian Hickson schrieb:
On Thu, 27 Nov 2008, Anne van Kesteren wrote:
On Mon, 24 Nov 2008 18:46:51 +0100, Philipp Serafin phil...@gmail.com wrote:
I guess this is more a cosmetic remark, but I thought I'd bring this up
anyway.
I've noticed that the paragraph on the MetaExtensions wiki
Ian Hickson wrote:
This is an area that has had some research done:
http://24ways.org/2006/marking-up-a-tag-cloud
http://microformats.org/wiki/tagcloud-brainstorming
I don't really see a compelling answer yet, and frankly tag clouds as a
whole aren't really so important that we need
2008/12/17 Ian Hickson i...@hixie.ch
This doesn't cost any time in HTML either, since the tokeniser doesn't
need to worry about what tags have end tags, the tree construction side
just drops unexpected end tags on the floor.
I don't think authors expect tags to disappear.
don't check for
Giovanni Campagna wrote:
2008/12/17 Ian Hickson i...@hixie.ch
This doesn't cost any time in HTML either, since the tokeniser doesn't
need to worry about what tags have end tags, the tree construction side
just drops unexpected end tags on the floor.
I don't think authors expect
I managed to miss this one when it went around the first time, but I
really have to speak up now. The second half of 8.1.1 is unnecessary
noise and complexity:
For the purposes of XSLT generators that cannot output HTML markup
without a DOCTYPE, a DOCTYPE legacy string may be inserted into
However, if the element is found within an XSLT transformation sheet
(assuming the UA also supports XSLT), then the processor would instead
treat the script element as an opaque element that forms part of the
transform.
transformation sheet is not a term in common use, and I don't think it
The nodes representing HTML elements in the DOM must implement, and
expose to scripts, the interfaces listed for them in the relevant
sections of this specification. This includes HTML elements in XML
documents, even when those documents are in another context (e.g. inside
an XSLT transform).
2008/12/18 Benjamin Hawkes-Lewis bhawkesle...@googlemail.com
Perhaps (got any actual evidence about author expectations in this case?),
but that's not a problem for tokenizer performance. You're shifting the
goalposts.
My comment about tokenizer performance was later. By the way, author
On Thu, 18 Dec 2008, Philipp Serafin wrote:
There is no reasoneable default size the page could adjust to. If the
author can't specify the size of a popup/dialog, what algorithm should
the UA use to find out the correct optimal size?
Lay out the page at infinite height and width, then
Ian Hickson schrieb:
On Thu, 18 Dec 2008, Philipp Serafin wrote:
There is no reasoneable default size the page could adjust to. If the
author can't specify the size of a popup/dialog, what algorithm should
the UA use to find out the correct optimal size?
Lay out the page at infinite
Elliotte Harold wrote:
...
Since XSLT 1.0 can generate well-formed XHTML without any problems,
there really is no need for this at all. Documents generated by XSLT
that need to be conforming should simply be XHTML.
...
Now if you can persuade Microsoft to implement XHTML, that might fly.
This should work in any scenario in which the XSLT processor itself is
serializing the output. If it's merely generating some sort of DOM or tree
to pass to another process, then all bets are off. However in that scenario,
other means of producing DOCTYPES are also not guaranteed since the
17 matches
Mail list logo
