Dave writes:
To an indexing service, the caption is the single most important thing
about
an image. By separating the caption from the IMG element, you force the
search engine to apply a heuristic of some variety to infer the
connection
... The indexing service user agent has to make
Hi,
The current specification of the createRadialGradient( x0, y0, r0, x1,
y1, r1 ) [1] is a bit ambiguous about the colour to use in the disc
defined by x0, y0, r0 when a colorStop is set for the offset 0. Should
the disc be transparent black or should it be filled with the color
defined
On Sun, 26 Nov 2006, fantasai wrote:
Ran across this comment:
http://www.whatwg.org/specs/web-apps/current-work/#features
# Should textContent be defined differently for dir= and bdo?
What would it mean to define textContent differently for dir= and bdo?
The question is really
Hi,
Other link types[1]:
Effect on... a and area
[...]
Hyperlink
The keyword may be specified on a and area elements; it creates a
hyperlink.
According to the sections of a and area, they are only hyperlinks if they
have an href= attribute, so it creates a hyperlink
Based on a lot of the feedback, I wrote up a first draft of how to do
image captions in HTML5:
figure
img ...
legend ... /legend
/figure
It's a block-level element, same level as p. The image and the legend
can come in any order, but there must be exactly one of each. The
Le 27 nov. 2006 à 20:49, Ian Hickson a écrit :
On Wed, 1 Nov 2006, Michel Fortin wrote:
I see no reason to be restrictive on the kind of content that can be
captioned.
Well, we want the semantics to be well-defined. It's not clear to
me what
the semantics will be in all cases if we allow
On Thu, 6 Apr 2006, mozer wrote:
Proposition 1 :
-
And what about just giving to img a content ?
This, sadly, wouldn't be very backwards compatible.
So why not to provide brand new element, say, x-img / that
have closed model? The same apply to x-input / and few others
On Tuesday 2006-11-28 01:49 +, Ian Hickson wrote:
figure
img ...
legend ... /legend
/figure
There are special rules for what to do with
fallback that basically make the caption disappear (though of course this
won't happen in legacy UAs).
I'm assuming the rules
I've chosen an inline-level content model because it allows not only
img, but also structured inline-level elements like pre. I'm not so
sure about that choice however.
Hm, pre seems like an interesting thing to put in a figure[...] I
certainly could see us also allowing figure to label
Michel Fortin wrote:
To me, a figure contains illustrative content attached to a document. It
may be an image, a code sample, or a snippet of another document used as
an example. I think it's important we do not try to narrow too much what
can and what cannot be contained in a figure; that's
On Tue, 2006-11-28 at 01:15 -0500, fantasai wrote:
I'd suggest using address, e.g.
figure
img
addressPhoto by Mariel/address
/figure
figure
img
captionCarcassonne/caption
addressPhoto by Mariel/address
/figure
Mere attribution is not contact
11 matches
Mail list logo
