that Steve mentioned)
Jeremy
--
Jeremy Keith
a d a c t i o
https://adactio.com/
of responsive sites currently using one or other
of these techniques, I'll be able to find them for you.
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
of measurement (e.g. ems).
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
are using
ems for their media queries in CSS to also use ems for their srcset
declarations.
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
Kornel wrote:
Note that the scale multiplier can be omitted already when only the size is
specified
I'm confused by what you mean by scale multiplier. The x value describes the
pixel density of the device/screen, not the image, right?
Jeremy
--
Jeremy Keith
a d a c t i o
http
queries but on the plus side, if it
maps directly to imgset in CSS, that's good.
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
around Mobile First and Desktop First because
it's not really about mobile or desktop; it's about small viewports and large
viewports but the terms are fairly common.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
queries (because the use-case is so similar to common
use-cases for media queries).
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
://adactio.com/journal/4272/
I'm trying (and failing) to understand why Jonas wants this feature removed.
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
.
Interactive user agents should additionally make the cited resource available
in manner similar to how they present other hyperlinked resources
Can you please give an example of user agents presenting *invisible*
hyperlinked resources? @longdesc, perhaps?
Jeremy
--
Jeremy Keith
a d a c t i o
http
The benefit of the proposed change should be weighed against the likely cost
of breaking content
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
how *not* to do it.
But is it really possible to mark such citations up without presentational
elements?
I'm not sure I understand the question. Do you mean presentational as in not
conveying semantics or presentational as in visible?
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
to formerly-presentational elements).
The hr element is currently defined as a paragraph-level thematic break. I
think br could be defined as a text-level thematic break.
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
in the
browser:
* images[x]
* movies[ ]
...etc.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
Dennis wrote:
Yes, but that wouldn't help since I want to force downloads regardless
of the browser settings.
Ah, I see. In that case, I fundamentally disagree with what you are asking for.
Final control should be in the hands of the user, not the author.
--
Jeremy Keith
a d a c t i o
http
attribute cover the use case of lat/long inputs? (albeit
without a nice UI)
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
fn.
HTH,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
that contradict this definition highlights the
problem, but the issue isn't with those examples; it's with the
definition of time.
HTH,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
Henri wrote:
On Nov 26, 2009, at 18:50, Jeremy Keith wrote:
The following extract shows how an IM conversation log could be
marked up.
p time14:22/time begof/b I'm not that nerdy, I've only
seen 30% of the star trek episodes
What's the point of having the time semantically marked up
parsing. It's still not ideal but it's much better than the
conditional comment object hackery.
(and again, this only relates to versions of IE before IE8)
So, on balance, #3 is looking more reasonable than #2 (which fails in
a lot more browsers).
Jeremy
--
Jeremy Keith
a d a c t i o
http
://www.whatwg.org/specs/web-apps/current-work/multipage/commands.html#conversations
I think that's a perfectly reasonable use of the time element* but I
find it hard to imagine how a user could add a chat message to their
calendar.
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com
probably wouldn't want those headings to contribute to the overall
outline of the document.
What do you think?
--
Jeremy Keith
a d a c t i o
http://adactio.com/
by the cognitive dissonance between the refusal to
drop a redundant new element like article, and the refusal at all
costs to add new elements where they would be genuinely useful (such
as a labelling element for figure and details).
--
Jeremy Keith
a d a c t i o
http://adactio.com/
.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
an outline point of view, this is identical:
section
h1 /
section
h1 /
...
section
h1 /
/section
/section
/section
As is this:
article
h1 /
article
h1 /
...
article
h1 /
/article
/article
/article
--
Jeremy Keith
a d a c t i o
http://adactio.com/
understanding is that article would be a
good
replacement of that.
Only if the content is independent. Otherwise use div (or section
if the content is related).
--
Jeremy Keith
a d a c t i o
http://adactio.com/
the other; they have an equivalence in importance.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
I wrote:
An h1 nested within two sectioning elements has exactly the same
importance as an h3
Whoops. I was looking at a different example. Ignore what I said and
listen to Tab Atkins Jr.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
.
Thoughts?
[1] Details of the exercise: http://adactio.com/journal/1605/
--
Jeremy Keith
a d a c t i o
http://adactio.com/
/multipage/embedded-content-0.html#fallback-content
Just a thought.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
.
Thanks, much appreciated.
I figured that the genesis of that note was the comment thread on
Bruce's post but it only makes sense in the context of H1+H2.
Ah well.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
the
lines of:
This content is fallback content. It is not content intended to
address accessibility concerns.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
and Love the Bomb/h2
h3By Stanley Kubrick/h3
/hgroup
The note would make sense if it were moved down to the examples and
prefaced with In this case...
--
Jeremy Keith
a d a c t i o
http://adactio.com/
of the
small element to make it clear that it is only intended for certain
instances but not others?
Alternatively, does anyone else think the small element should be
capable of wrapping inline and block elements? (raises hand)
--
Jeremy Keith
a d a c t i o
http://adactio.com/
) are best
solved by microformats and/or microdata.
By the way, there is a draft recipe microformat in the works and, once
again, your input would be very welcome:
http://microformats.org/wiki/hRecipe
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
will all continue to exercise our personal choices
even if the HTML5 spec tries to restrict the meaning of the element.
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
analysis for both style and correctness.
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
as well to the DOM. Currently the documentation only mentions
the DOM.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
community itself is the right group for this job, I think
that many of the people in the community would be well-suited (and
have experience).
I'll be sure to make the longevity of committing to a new community
process clear.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
(e.g. rel=accessibility) that would/should probably never become a
microformat but are still good semantic values. Will they really be
rejected outright?
Thanks in advance,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
, then
it could potentially be marked up using CITE, IMHO.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
value to pass the microformats
process.
Should everything on the wiki page be marked as unendorsed or, more
realistically, should the conditions for acceptance be altered?
--
Jeremy Keith
a d a c t i o
http://adactio.com/
42 matches
Mail list logo
