11 Nice but sadly enough still browser dependent

THis is really handy, but when you look at the sad truth all the big sites as mentioned in one of the posts above cannot take for granted that their users have the needed browsers.

On my site I solved this issue with a small PHP script that extracts the content only (indicated by comments in the HTML, coming from the CMS) and substituting all images and links in there. It’s also a rather fast and small solution and works on every browser.

Just my two cents, still awesome that some people write about the benefits newer browsers give us.

posted at 06:50 am on May 10, 2002 by Chris

12 A timely article

Thanks for the article. It has solved many problems I was facing and couldn’t find solutions to. Like previous posters, the article has given me encouragement.

Does anyone know where I can find out which other media selectors are supported by various browsers?

posted at 06:54 am on May 10, 2002 by Matthew Farrand

13 Very useful, cheers

Many thanks for the article. Useful as ever. ;-)

posted at 07:47 am on May 10, 2002 by Guy Carberry

14 Print Links on Most Major Sites

The best part about print links on most major sites isn’t the fact that it removes a lot of the display (which you wouldn’t want to waste paper on), but the fact that it places all of the content on one “page”. No more clicking a link to go to the 2nd (or 3rd or 4th, etc.) page.

While I agree that a print media style sheet would be wonderful on sites that have a “Print!” link, I don’t think it would alleviate the problem of multiple pages of content. That’s the biggest draw to a “Print!” link, IMHO.

In the case of a print CSS, you would have to print each page of the article, clicking next to load the next page, and printing that page, rather than loading the article in one large page (like the BigCo’s do it now with their “Print!” links) and printing directly from that.

posted at 08:05 am on May 10, 2002 by Jason Lempka

15 Story Image Link

Great article, but I noticed when print previewing the page in Moz RC1 that there is a big URL that comes right after the image at the top of the story. That might be something that you want to fix. Great article though, I’ve used some but definetly not all of these tips.

posted at 08:07 am on May 10, 2002 by Nate Baxley

16 Printing on Major Sites

<quote by=“Chris”> This is really handy, but when you look at the sad truth all the big sites as mentioned in one of the posts above cannot take for granted that their users have the needed browsers. </quote>

I don’t see a reason why major sites, including yours, coudn’t do both. That’s the part I like best about CSS print styles. A user can print from the print only page or from the normal page and the output is respectable both ways. And if you have a consistent naming convention, it doesn’t take a whole lot of effort either.

posted at 08:45 am on May 10, 2002 by Jeff Carr

17 Broken Link

Great – but the link to the article about images and tables is broken. There’s a space ( ) before the last slash in the address. Once removed, the url works fine.

posted at 09:38 am on May 10, 2002 by Chris Hester

18 How to wrap the links?

Great piece of work but how do you get the long URLs to wrap? They’re busting my table width apart in the print out at the moment.

posted at 09:48 am on May 10, 2002 by Chris

19 Transparency and printing

Jason—there is no need to print each page of a multi-page web document—if the author has coded it correctly and you’re using the right browser.

This code, placed on all of the individual pages, should cause a modern browser to print a different document instead:

<link title=“Print the whole damned thing!” type=“text/html” rel=“alternate” media=“print” href=“printversion.html”>

Or:

<link title=“Print the whole damned thing!” type=“text/html” rel=“alternate” media=“print” href=“printversion.pdf”>

Works with IE5+/Win, but still doesn’t work with MacIE last time I checked.

posted at 09:49 am on May 10, 2002 by Peter Sheerin

20 Completing relative URIs with and without slashes

Great article. I love it!!
Theoretical CSS-3 to complete relative URIs that start with slashes and URIs that don’t:

/* for all relative URIs (“foo…”) */ #content a:not([href^=“http://www.alistapart.com/”]):after { content: “ (http://www.alistapart.com/” attr(href) “) “; }
/* for all relative URIs (”/foo…”) */ #content a[href^=”/”]:after { content: “ (http://www.alistapart.com” attr(href) “) “; }

Now, I am not sure if the second rule overrides the first. It should, but in case it doesn’t, then replace the first rule’s selector by this: #content a:not([href^=“http://www.alistapart.com/”]):not([href^=”/”]):after

Relative URIs that start with something like “../foo”, I am not sure what to do about that, but I recently stopped using them. I define a BASE-URL and all paths are always from that location down. In the above-mentioned examples, that BASE-URL would be “http://www.alistapart.com/”.

O yeah, this is all pure speculation, but it made sense to me.

posted at 10:08 am on May 10, 2002 by Kris