should it apply to any rel values? (like rel="import" that Steve mentioned)
Jeremy
--
Jeremy Keith
a d a c t i o
https://adactio.com/
er and smaller images in
srcset.
If you want specific examples 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/
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
from the examples above? Or, if we're going to use this CSS-like syntax
> anyway, allow other units of measurement (e.g. ems).
And Tab replied:
> No, if we're aping the CSS syntax more closely, we should just use CSS units.
I agree. Seems like the sensible approach. It also allows autho
do we still want to keep this unit-less i.e. ditch the "px"
from the examples above? Or, if we're going to use this CSS-like syntax anyway,
allow other units of measurement (e.g. ems).
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
t; approach.
Jeremy
P.S. I'm using air-quotes 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/
t it's a different syntax to media 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/
n use-case could look almost
exactly like media 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/
http://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/
ons.html#the-footer-element
...and the element is a sectioning root. The semantics of those
two elements match up perfectly.
> Interactive user agents should additionally make the cited resource available
> in manner similar to how they present other hyperlinked resources
Can yo
it
shows us 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 "v
olution would match up
nicely with the design principle "Support existing content."
http://www.w3.org/TR/html-design-principles/#support-existing-content
"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/
7;s suggestion (or, at least, I like it as much as any of the
semantic redefinitions being applied to formerly-presentational elements).
The element is currently defined as "a paragraph-level thematic break." I
think could be defined as "a text-level thematic break."
Jeremy
--
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
r than opening in the
browser:
* images[x]
* movies [ ]
...etc."
--
Jeremy Keith
a d a c t i o
http://adactio.com/
" ;-)
But to the point at hand
Would the @pattern 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/
those two optimisation patterns, the n is inferred from fn.
HTH,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
re examples
elsewhere in the spec that contradict this definition highlights the
problem, but the issue isn't with those examples; it's with the
definition of .
HTH,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
x27;s still not ideal but it's much better than the
conditional comment 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://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.
14:22 egof I'm not that nerdy, I've only
seen 30% of the star trek episodes"
What's the point of having the time seman
seen
30% of the star trek episodes"
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 K
n headings,
you 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/
w element like , and the refusal at all
costs to add new elements where they would be genuinely useful (such
as a labelling element for and ).
--
Jeremy Keith
a d a c t i o
http://adactio.com/
f a particular type (e.g.
article) without necessarily creating a new element for it. Otherwise
we'd have to create , , elements, etc.
instead of using .
So an answer of "yes" to your question doesn't mean that every current
ARIA role needs a corresponding distinct elemen
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/
;t more or less important than
the other; they have an equivalence in importance.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
est large unit of
content
that is repeatable and my understanding is that would be a
good
replacement of that.
Only if the content is independent. Otherwise use (or
if the content is related).
--
Jeremy Keith
a d a c t i o
http://adactio.com/
this:
...
--
Jeremy Keith
a d a c t i o
http://adactio.com/
lve
anything, as far as I can tell. All the discussion around suggested
name changes have revolved around blog posts ...the one use case that
is unambiguous.
[1] http://krijnhoetmer.nl/irc-logs/whatwg/20090916
--
Jeremy Keith
a d a c t i o
http://adactio.com/
/adactio.com/journal/1605/
--
Jeremy Keith
a d a c t i o
http://adactio.com/
twg.org/specs/web-apps/current-work/multipage/embedded-content-0.html#fallback-content
Just a thought.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
anks, 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/
something along 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/
ick
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/
e
element to make it clear that it is only intended for certain
instances but not others?
Alternatively, does anyone else think the element should be
capable of wrapping inline and block elements? (raises hand)
--
Jeremy Keith
a d a c t i o
http://adactio.com/
t measurement in general (and recipes in particular) 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/
element.
I choose to mark up names with the element. Other authors
choose not to. We 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/
nal static analysis for both style and correctness.
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
with the microformats community. While I don't the
microformats 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
ip to
the URI as well to the DOM. Currently the documentation only mentions
the DOM.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
a good idea. There are perfectly good values listed
(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/
. No META value will *ever* become a microformat;
the very concept of invisible metadata is anathema to microformats—
it's impossible for a META keyword 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/
f it's a proper noun, then
it could potentially be marked up using CITE, IMHO.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
43 matches
Mail list logo
