Out of curiosity, what is the point of a "light box"? I tend to open lots of images into new tabs while I'm reading articles, and it's really annoying to have the rest of the article go black when I do.
Full CSS3 Lightbox - Absolutely no JavaScript
71–80 of 114 posts
Re: Full CSS3 Lightbox - Absolutely no JavaScript
#72Looks great. Does this work cross-browser? (besides the transition effect) Also, is there any documentation/github repos?
- Works well in Chrome / Safari. - Works without transactions in Firefox - Does not work in Internet Explorer 6, 7, or 8.
Re: Full CSS3 Lightbox - Absolutely no JavaScript
#73Earlier quoted context omitted.
Not true. A back button is meant to "go back to previous state". When you click a link, then back, you will go back to the previous page or position on the same page depending on the link you clicked. Similarly, if you enable a lightbox and your page goes behind a modal image, hitting back will behave exactly the way it should, i.e. take you back to your previous state. I'll go one step further and say that a lightbo…
Steps to reproduce broken button: 1) Open the demo page 2) Click image 3) Click 'X' in top left of image 4) Click different image 5) Click the 'X' in the top left of image 6) Click browser's 'back' button 7) Observe how you're staring at the image, not the hacker news page you came from. The problem is that clicking the 'X' should pop the image off the stack, not just add another page ("#home") to the stack. Opening…
1. Go to http://en.wikipedia.org/wiki/Hacker
2. Click the "Innovation" link in the ToC on the right
3. Click the "Entertainment" link (you can just see it) under the "Innovation" one.
4. Click the back button.
5. Observe how you're not taken back to Hacker News.
Now imagine this is a really long page of FAQs, with a "Return to top" after each question, and the same ToC at the top (something a clueless user probably sees everyday [I know I do on O2's site all the time]). You can see how it begins to look like a browser implementation problem.Maybe the browser should automatically pop all "#"s associated with a URL from its history stack if a user reaches the original URL again (via backs or clicking some in-page link, doesn't matter); I don't know. But I honestly consider this a browser implementation problem, not a web developer problem. I think anything we've been doing till now has been to mitigate this and we shouldn't have to.
Re: Full CSS3 Lightbox - Absolutely no JavaScript
#74I assume this isnt some bug or some flaw, and that it can probably be coded to behave differently, but as things stand that would prevent me from using this particular lightbox.
Re: Full CSS3 Lightbox - Absolutely no JavaScript
#75Earlier quoted context omitted.
Steps to reproduce broken button: 1) Open the demo page 2) Click image 3) Click 'X' in top left of image 4) Click different image 5) Click the 'X' in the top left of image 6) Click browser's 'back' button 7) Observe how you're staring at the image, not the hacker news page you came from. The problem is that clicking the 'X' should pop the image off the stack, not just add another page ("#home") to the stack. Opening…
Does that make it "broken" or just incompatible with your expectations? Would other non-technical users have the same expectations? It's possible other users will want to go "back" to the image they last visited. Consider if this was done just HTML 4 and no CSS or Javascript. You would click a thumbnail and a new page would be loaded with a full size version of the image. You would then click a "close" button that wo…
The user clicks the image in order to see it full-size. The lightbox overlays the page that the user is on. The user is not conscious that they are navigating to a new page, or even just a part of the page that they weren't at before (to the #image). Though the workflow is in actuality following a link, the user is not aware that they are following a link, so the back button functionality doesn't work as expected.
Links are well understood by everybody that uses the Web. They change the page that you're on to a new page, or a new part of the page. Lightboxes were invented so that the user doesn't need to leave the page, or the part of the page, that they are on.
So in my mind, lightboxes that don't behave like lightboxes and instead behave like links are broken.
Re: Full CSS3 Lightbox - Absolutely no JavaScript
#76Nice! It breaks the back button however...
[We can argue the pureness of the demo after that till the end of time though.]
Re: Full CSS3 Lightbox - Absolutely no JavaScript
#77Is it just me or is the Lighbox effect really annoying? What's wrong with middle-clicking an image and having it open in a new tab?
Re: Full CSS3 Lightbox - Absolutely no JavaScript
#78Re: Full CSS3 Lightbox - Absolutely no JavaScript
#79Re: Full CSS3 Lightbox - Absolutely no JavaScript
#80Out of curiosity, what is the point of a "light box"? I tend to open lots of images into new tabs while I'm reading articles, and it's really annoying to have the rest of the article go black when I do.