CreativeSheep

When you create a JSON file to manipulate Chrome, do you run it in the console log ?

<img src="http://demosthenes.info/assets/images/sossusvlei-namibia-thumb-1x.jpg" srcset="sossusvlei-namibia-thumb-1x.jpg 1x, http://i4.mirror.co.uk/incoming/article5803160.ece/ALTERNATES/s615/Lion-park.jpg w320 " The image in red is initially seen by the user, shouldn't the image in blue be seen when the viewport is a width of 320 ?

Ahh I see the error of my ways. In my version it is working but the lightbox is not clearly visible ? Chrome works, ok, except the close button is out of view, Firefox 43.0.3 has problems.

Why is it referencing the file to another link, when I removed all references to the link ? My reference to the script is, as you mentioned, strictly above the closing tag of the </body> tag ?

Odd the CodePen version works for me in FireFox, hrm.

Can someone tell me what I did wrong, why this works when you click on an image, but not on this page ? I simply copied and pasted the code as so it's identical but the CodePen version works, the other, well, not.

How do you process a JSON file to create something from it ? What I want to do is, export an image file from Chrome Device manager with details. I understand that JSON is an easier to read, how do you get Chrome to, if I'm right, execute a script that runs a function, console.log ?

486-SX25 Upgrade a year later 486DX4-100. I owned that computer an extremely long time before buying a new one. My videos cards today cost more then that computer, scary. Now my seven year old laptop is almost identical in power to some of the tablet PC sold today, the tech of yesterday is new today.

I have three <li>. When positioning the left most <li> the middle <li> will always auto center between the left most inline <li> and the right most inline <li> as there are no styles for the center inline <li>. Let the <li> between to do the centering for the middle <li> ?

Suppose you have three list items <li> and the middle one you want to align automatically, can this be done ? <li><a></a></li> <li><a></a></li> // Regardless how you position the other two, this one will be automatically aligned ? <li><a></a></li>

I asked this question elsewhere, maybe more input a conclusion can come quicker. In Chrome you can view your media queries based on devices; I want to be able to export a screen capture of the current div with the div size put within each div via console log ?

I don't understand what you meant as in your example ?

So, you say there isn't any benefit; then you say srcset can save on bandwidth, doesn't that sound like a benefit to you ?

I know. Why can't I use a lightbox to serve different images based on screen width ?

A browser downloads all the image in a Srcset, it doesn't request the image to which it matches, for example a 320w image and download only that specific image ?

I understood you perfectly. What did you think I meant by high pixel density, a large image ? No need for responsive images, but I want responsive images, regardless if the user is on a retina or not; for example, I don't want to display the same image for all screens. <img src="acme.jpg"> == This is the image a person will originally see regardless of screen size. <srcset = "acme2.jpg" w320 == If the screen width is 320 this image will show when the user clicks or touches the acme.jpg image. And that is where the lightbox would come into effect, understood ?

Are you saying, if they have a high pixel density screen they will load a 1024 image ? Even if they do, they will have to scroll & pan, not that efficient. If you are not lazy loading then look into that, you will see far better performance gains there. ? How would you tie in a Lightbox into a polyfill, if a polyfill is the only answer ?

The polyfill for srcset doesn't require the srcset to be nested within the <picture> element, correct ? A mobile users, or for that matter, a tablet user, won't want to load a 1024 image, with srcset you can feed the user an image appropriate for their screen size, it may be different, atleast they can view it. From my understanding, the suggestion is to use whatever lightbox I want to use, regardless if it doesn't support srcset, and simply polyfill ? That raises a question, most lightboxs are JS or jQuery can the polyfill mention in this thread, communicate with any lightbox and tell it, the screen size is 320px width, don't feed the user the image in the <img src> which is the first in the markup; feed the user the 320px width image in the srcset that follows ?

I've been searching for a Lightbox that supports Srcset, the free ones I've come across were, presentation wise, exactly what I was after but support from the author to add Srcset support always broke down. I prefer free, but at this point I will pay for one if required. If anyone has any suggestion ?

I did post an issue on Github, the author fails to care. I can only hope the next lightbox I find fills in the requirements I want <sigh>

I'm setting up a lightbox, there is one of two problems, the main problem is. The lightbox works with a <picture> element; how does one get it to work without a <picture> element and strictly a <a href> & srcset ? I tried srcset and it doesn't work ? The first image by default would be, in this case, paperpile image then depending on the screen width the other images would load. The lightbox, I assume expects the markup below to be nested within <picture></picture> I don't want to nest it within <picture>. <a href="/wdp/wip/paperpile.png" class="firstimg"> <img src="/wdp/wip/images/paperpile.png" srcset="/wdp/wip/images/brick.jpg 320w, /wdp/wip/images/bulding.jpg 560w, /wdp/wip/images/rock.jpg 900w" sizes="(min-width: 320px)" alt="" title="">

Ah syntax error !

Daisy chaining doesn't appear to work; the class=firstimg works, in general, the second class=secondimg returns a 404 ? $("a.firstimg","a.secondimg").fluidbox();

Fluidbox requires I load two CDN & set the following as a script. Since the anchor is an image and fluidbox requires an anchor, except I assigned a class to the anchor ? <script> $(function () { $(a.firstimg).fluidbox(); }); </script>

oh shorthand.