Ian Hickson ha scritto:
What terminology would you prefer rather than subtree? (We can't say
document, since we are also trying to define conformance rules for
disconnected subtrees handled from scripts.)
I was thinking again on that. Let me suggest something like the
following (and just
Otherwise, just let the id attribute be unique in the whole document, label
any duplicate one as illegal and treat it as the empty string, so that one
only method is enough and the DOM 3 undefined behaviour for 'getElementById'
is no more problematic, being fired by non-allowed DOM structures
Ian Hickson ha scritto:
On Wed, 3 Dec 2008, Calogero Alex Baldacchino wrote:
But, isn't it worth to spend a word everywhere in the spec to tell when
it's a quirck for backward compatibility, which might go away in the
future, and when it's not, because that's not needed?
None of the
Ian Hickson ha scritto:
It's intended as a replacement for DOM3 Core, I believe.
Then, I hope in a convergence with the W3C, as it's one of the goal of
the WHATWG. I believe neither organizations wish a heavy standard
fragmentation.
--
Caselle da 1GB, trasmetti allegati fino a 3GB e
Jonas Sicking ha scritto:
In firefox we now always return the first element with the requested
ID. I think IE does the same. This seems equally reliably and much
less likely to cause page breakage or interoperability issues.
That's reasonable, and I pointed out that should be
Ian Hickson ha scritto:
On Mon, 1 Dec 2008, Calogero Alex Baldacchino wrote:
Yes, a hash link (a href=#foo) will scroll to the element with an
id=foo. If coding properly, you'll virtually *never* use an a for
an actual *anchor*, but rather will target the most semantically
appropriate
Calogero Alex Baldacchino wrote:
However, now I have a question. The 3rd step of the algorithm to
determine the indicated part of the document says,
If there is an element in the DOM that has an ID exactly equal to
/fragid/, then the first such element in tree order is the indicated
part of
On Tue, 2 Dec 2008, Calogero Alex Baldacchino wrote:
Indeed it does, and I found such behaviour more consistent than letting
just the a element with a 'name' or an 'id' being an anchor for
navigating to a fragment :-)
However, now I have a question. The 3rd step of the algorithm to
Benjamin Hawkes-Lewis ha scritto:
Calogero Alex Baldacchino wrote:
[...]
I think you're confusing parsing rules that conforming user agents
must follow to associate identifiers with elements (even when ids are
duplicated) with the authoring rules that conforming documents must
follow (ids
Ian Hickson ha scritto:
Exactly how getElementById() works is out of scope for HTML5, but in the
Web DOM Core spec that Simon is working on I imagine he has specced that
it will pick the first element with a matching ID or some such behavior.
Cheers,
Is it thought as a somewhat break with
On Wed, 3 Dec 2008, Calogero Alex Baldacchino wrote:
When you read The value must not contain any space characters., is it
an authoring rule for conforming documents, for you? Ok.
Right, statements that place requirements on what the values must be are
authoring requirements.
When you
On Wed, 3 Dec 2008, Calogero Alex Baldacchino wrote:
Ian Hickson ha scritto:
Exactly how getElementById() works is out of scope for HTML5, but in the Web
DOM Core spec that Simon is working on I imagine he has specced that it will
pick the first element with a matching ID or some such
Tab Atkins Jr. ha scritto:
[[off list]]
Well, in fact, the above could be done as well by 'playing' with anchors
(but is it still possible to set an anchor somewhere in the document, such
as a id=foo /? I haven't found examples for that, perhaps I'm missing
something...).
Yes, a hash
On Mon, 1 Dec 2008, Calogero Alex Baldacchino wrote:
Yes, a hash link (a href=#foo) will scroll to the element with an
id=foo. If coding properly, you'll virtually *never* use an a for
an actual *anchor*, but rather will target the most semantically
appropriate element, such as a
On Wed, 10 Sep 2008, Sam Kuper wrote:
In the current HTML5 draft, section 4.4.6 The blockquote element states,
If a blockquote element is preceded or followed by a single paragraph
that contains a single cite element and that is itself not preceded or
followed by another blockquote element
Ian Hickson ha scritto:
I've removed the offending text.
I don't think we can say that quotes should always come before their
citations. For example, it's easy to imagine a blog that says:
pciteBook The First/cite says:/p
blockquote...from book 1.../blockquote
pBut citeBook The
On Nov 30, 2008, at 18:38, Calogero Alex Baldacchino wrote:
I'm not sure I'm understanding the whole function of the cite
element,
[...]
Q: What problem does it solve?
The cite element solves the problem that if one considers i evil
(I don't) and one wants to conform to the Chicago
On Sun, 30 Nov 2008, Calogero Alex Baldacchino wrote:
I'm not sure I'm understanding the whole function of the cite element,
and perhaps I'm bothering again with ids and references, but the
relationship between a cite and a quotation could be disambiguated by
coupling an id and a reference
Ian Hickson ha scritto:
On Sun, 30 Nov 2008, Calogero Alex Baldacchino wrote:
I'm not sure I'm understanding the whole function of the cite element,
and perhaps I'm bothering again with ids and references, but the
relationship between a cite and a quotation could be disambiguated by
On Mon, 1 Dec 2008, Calogero Alex Baldacchino wrote:
Ian Hickson ha scritto:
On Sun, 30 Nov 2008, Calogero Alex Baldacchino wrote:
I'm not sure I'm understanding the whole function of the cite
element, and perhaps I'm bothering again with ids and references,
but the relationship
Dear all,
In the current HTML5 draft, section 4.4.6 The blockquote
elementhttp://www.w3.org/html/wg/html5/#the-blockquote
states, If a blockquote element is preceded or followed by a single
paragraph that contains a single cite element and that is itself not
preceded or followed by another
Dear all,
For some reason, the email set-up I used to send my previous message
(Gmail via Chrome) inserted whitespace:pre values into each
paragraph's style attribute. Depending upon your email client, this
may have rendered my email difficult/unpleasant to read.
My apologies for this. Quoted
22 matches
Mail list logo
