W3C home > Mailing lists > Public > public-respimg@w3.org > December 2014

Re: Walking and Talking

From: Simon Miles-Taylor <smilestaylor@gmail.com>
Date: Wed, 17 Dec 2014 00:48:29 +0000
Message-ID: <CAGeVLLPe-DVyXgtgQiVAS8nnFwMTHia92HxRovxt6Zs6J-ip9g@mail.gmail.com>
To: Eric Portis <lists@ericportis.com>, public-respimg@w3.org
When it comes to images there are a number of strategies you can use.
Larger images I would always create for quality assurance purposes.
Rendering down images is fine but you do get to a point where the image
starts to disintegrate.

I have three sets of Images 750px images for large format devices.  Then

Std 500px (Mobile 200px) Text .875em (Mobile .6em)
Std 225px (Mobile   75px) Text .875em (Mobile .6em)

To get the images to render for the mobile devices all I have to do in
separate stylesheet is:

.cellimage3 { display: inline-block; height: 47%; width: 32%; margin: auto;
.cellimage3i { height: 86%; width: 99%; margin: auto; text-align: center; }
.cellimage3t { height: 13%; width: 99%; font-size: .6em; line-height:
.75em; text-align: center; }
.imageformat3 {display: inline-block; height: auto; width: auto;
max-height: 75px; max-width: 75px; vertical-align: middle;}
.imagespacer { width: 0px; vertical-align: middle; border-style: none; }

The Image container is always expressed as a percentage and using the
vertical-align attribute the image will center both horizontally and
vertically.  This does require another image:

<div class="cellimage3">
<div class="cellimage3i">
<img class="imagespacer" src=" include/fill.gif" height="100%" alt="" />
<img class="imageformat3" src="/Images/Originals/1.jpg" width="225"
height="200" alt=""/></a><br />
<div class="cellimage3t">Foo

The mobile device will render the image down proportionally to 75px x
67px.  For the standard rendering there is obviously no size restraints.
The only reason there are two sets of image is that going from 500px images
to 100px can get a little bit ugly.

Providing your image can be held within the image container you should be
able to port your image onto the mobile device with a media query directing
to a separate stylesheet with the downsized attributes.

A lot of the image management is about the size of the image and this was
implemented before the Picture Element. For the mobile environment I was
simply not enamoured to create 20,000 images at 75px constraints

Simon Miles-Taylor

On 15 December 2014 at 22:00, Eric Portis <lists@ericportis.com> wrote:
> IE walks the walk
> Internet Explorer is implementing srcset with x descriptors
> <http://blogs.msdn.com/b/ie/archive/2014/12/08/status-roadmap-update-srcset-lt-main-gt-element-and-date-inputs-in-development.aspx>
> .
> This is *huge* news; it means that x descriptors have or will soon come
> to every major browser <http://caniuse.com/#feat=srcset>.
> w descriptors, sizes, picture, and all of the rest are still officially
> “under consideration” (and not “in development”), but from the looks of it
> <https://twitter.com/gregwhitworth/status/542075784014204929> this
> represents a firmly planted first step on the path towards a full respimg
> implementation in IE.
> (And it certainly doesn’t hurt the RICG’s unofficial 1% in 2014 campaign
> <https://twitter.com/zcorpan/status/542048849641340931>.)
> RICG members talk at talks
> Here’s <http://www.ami.ca/AMI-tv/Pages/AMI-Inside.aspx> a video recap of Dave
> Newton’s September talk
> <https://speakerdeck.com/newtron/using-responsive-images-responsibly-performance-and-accessibility>
> at Accessibility Camp Toronto. Respimg discussions start at the eight
> minute mark; Newtron takes center stage from 9:22–16:50. The talk and the
> interview are great, and hey! Nice shirt!
> And apparently Yoav brought the house down at SmashingConf Whistler this
> past week <http://smashingconf.com/speakers/yoav-weiss>. “Responsive
> images are <del>coming</del> here!” Yoav’s slides are here
> <http://yoavweiss.github.io/smashingconf_whistler/#/>.
> Etcetera
> I was pleasantly surprised by the comments on my recent A List Apart
> respimg article
> <http://alistapart.com/article/responsive-images-in-practice>. I’d braced
> myself for a lot of criticism and complaint, but almost every comment
> concerned *implementing* and *automating* all of this new markup. Myriad
> dev environments and CMSes are going to require myriad tutorials and
> implementation recaps; Aaron Gustafson has written a great one about his
> recent experiences implementing respimg with ExpressionEngine
> <http://aaron-gustafson.com/notebook/2014/adaptive-images-in-expressionengine-with-ce-image/>
> on the Nichols College site <http://www.nichols.edu/>.
> Ian Devlin did some walking *and* talking this week, on the subject of providing
> multiple, alternate captions for art-directed images
> <http://www.iandevlin.com/blog/2014/12/html5/defining-multiple-captions-and-alt-text-for-responsive-images>.
> Personally I’m a bit ambivalent about this, but Ian’s article (and
> polyfill <https://github.com/iandevlin/picturecaption>!) make a strong
> case.
> Finally, element query talk is still rumbling along. Minutes from a
> recent RICG conference call
> <https://docs.google.com/document/d/1NlJslYLNkmm42EYAXSiA94PIq7t4Bo7EiUA6t2tj7ps/mobilebasic?pli=1>
> indicate that there is some consensus within the group on how to deal with
> the feature’s inherent circular dependency issues
> <http://www.xanthir.com/b4VG0>, and that Tab is getting ready to start a
> syntax discussion thread on www-style
> <http://lists.w3.org/Archives/Public/www-style/>. That should be fun.
> See you in a couple of weeks!
> —eric
Received on Wednesday, 17 December 2014 00:48:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:06:15 UTC