109 Reader Comments

Good article. I love it when programmers’ eyes light up when I say “Nah, don’t do a print specific page, I’ll handle it with CSS.”

Outputting links’ URLs is a great idea, but limiting this to bodycopy elements, and going with a small font size works better. Print this article in Netscape 6.2 and the title image, which is wrapped in a <H1>, spits out a superhuge <H1> styled URL that doesn’t wrap. Yikes.

A browser-related note: currently, the Mac version of Opera doesn’t handle point-sizes in print stylesheets very well. Opera uses 96 dpi on screen, which is what Windows uses and close to what the W3C recommends (90 dpi, IIRC). However, in print, 72 points make an inch. This is why the original Mac’s use of 72 dpi made it perfect for desktop publishing. The Mac version of Opera uses its 96 dpi definition in print as well, making the output too large. I don’t believe there is any workaround at this time. I’ve reported the bug to Opera.

Also, a tip for people making print stylesheets for sites that use absolute positioning: you should declare your absolutely-positioned divs as position:static (and probably also use width:auto) in your print stylesheet to return them to the normal document flow, or you may get strange results.

over the past few months i have come to love CSS and i now do everything with it, or at least so i thought up till now. i thank you for writing this article. it will no doubt come in very handy to me :D

Amazing article, I was very impressed. Having used this method myself, I found it useful to have a full article going over the topic in greater depth.

Combining this with a style switcher should make for good usability - I’ve long wanted an easy way to make good pages, that work well on multiple devices, and for people with visual disabilities, and this sure is a good approach for printers.

Don’t waste paper testing the results of your new print-only stylesheets. The Print Preview function in both IE and Moz will let you see how your stylesheet is coming on - without the need to print it.

Great article, the absence of print style sheets from virtually every major site has been a pet peeve of mine for some time. Hopefully their sluggish in-house developers will get round to learning enough CSS sometime in the next few years.

One teeny weeny almost microscopic nitpicking point about ALA’s printer-friendliness: it’d be just that little bit more slick if the images used transparency (obviously there’d still be pixels around the edges matted onto the background colour to retain anti-aliasing, but it’d be an improvement).

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.

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.

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.

<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.

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/”.

Not to say, of course, that you shouldn’t use a print stylesheet, but that the benefits *users* will gain are likely to be more than offset by what we lose. I’ll remember the Print Preview trick mentioned above….

You can increase the user experience by including a style switcher. Plus, the whole point of CSS is that the user can control the experience and “escape wretched design” through an user style sheet. Basically, print pages always were a hack and still are. With proper CSS and actual standards-compliant Web browsers, we shouldn’t be indulging in kludges any more. Besides, the newer browsers are better for users anyhow.

Thanks for all the positive feedback, folks! I really appreciate knowing that articles like this are useful and interesting, and also what other questions people have about CSS. Here are my responses to a few.

“...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.”

A couple of people commented on this. We left them in on purpose, because the image link contains a URL like any other. However, we could have avoided the HUGE TEXT problem using something like this:

h1 a:after {font-size: 50% !important;}

That would make the generated content half the usual size of ‘h1’ text when printed. Of course you could use whatever value you like. When Big Z gets back from his trip I’ll talk with him about whether or not we want to do that for the site’s print styles.

“...how do you get the long URLs to wrap? They’re busting my table width apart in the print out at the moment.”

As it turns out, that’s browser-dependent. Some browsers will line-wrap after a hyphen or slash, while others won’t. If yours won’t then you may want to stop trying to size a table to a certain width in print, or making the generated URLs use a smaller font size in print. As a last resort, you could class any link you don’t want to generate a long URL and write styles to prevent it.

“Theoretical CSS-3 to complete relative URIs that start with slashes and URIs that don’t… “

I think you’re close, but there are some cases that your rules wouldn’t cover. I’d really like to explore a comprehensive solution, but it would almost be an article in itself—which is why it doesn’t appear in the article I wrote. Still, I’m impressed; I didn’t think anyone was messing around with those CSS3 selectors, and it looks to me like you have a pretty good handle on how they work. That’s more than I can say about myself most days…

That was a great article - practical and helpful with some ideas that I had not considered before. I already had a print.css, but I have been back fiddling a bit more with it and it is now definitely better than it was. I particularly appreciated the tips about links - I didn’t even realise before that this was possible!

This is the section of CSS2 that describes generated content, which is how that URL insertion got done. Note that the section on counters and automatic numbering can be ignored, because no browser I know has implemented them correctly. Or at all.

I wouldn’t recommend the extra space on the end of the paranthesis after printing links out. If the link is at the end of the setence it means you’ll get something like ‘.../page.html .’ Which looks a bit silly. All the links that are inline will already have spaces after them anyway, so I don’t see any point in that extra space. Apart from that, nice article.

Re: the content request. You can find out more about it in the CSS2 spec. It’s not too hard to read, particulalr,y I don’t think. http://www.w3.org/TR/REC-CSS2/generate.html

This is a great thing - the one with CSS print version of the page ;) But nobody mentioned that not all users that are browsing the web, are webmasters that know about CSS.
They will be still looking for the “click here for printer-friendly version”? link. If there is none such link - they will propably not print the page. Or they will and they will be pleasantly surprised ;)

Maybe I’m being obtuse, but there’s nothing stopping us putting somewhere on our pages something like “This page will reformat correctly for your printer” with appropriate credit to the clever use of stylesheets. Or would that not accord with the design of your pages?

Great article! I’m now beefing up the print stylesheets for my sites :)

One problem thought… I’m having trouble getting URL completion to work… basically I can get the URL to display (in N6.2 at least) but I can’t get the relative URLs to complete. This is the code, very slightly modified:

quick version: I’m trying to add this to my print-version stylesheets but I can’t get the URL completion to work… how well (or otherwise) is the feature supported in the common browsers at the moment? Trying to figure out if the fault is mine or the UA :)

The selector above is CSS level 3. CSS-3 is still a W3C draft and not expected to be supported at all at the moment. But things go fast and it doesn’t harm knowing what will be possible within hopefully only months.

If you put a class on outgoing links (you may wish to style those differently as well, if they are about to open up a new window), you can escape those from the completion rule. Then for the internal links, if they are all relative:
div.item a:link:after, div.item a:visited:after {
content: " (http://www.domain.com" attr(href) ")";
}

I’m not joking, Kevin (http://www.alistapart.com/stories/goingtoprint/discuss/2/#ala-426). While Opera does support generated content, it had some serious bugs up through at least v5, many of which I personally reported to Opera’s CTO. Most of them were fixed, but not everything works as it should. See, for example, the test located at http://www.meyerweb.com/eric/css/tests/css2/sec12-02.htm , which shows some support for ‘content’. At least one text ont he page is failed by Opera 6/Win. Furthermore, when I print-preview the article in Opera 6, or try testing the generated content with a screen-media version of the print styles, none of the URLs appear. So it would seem to me that there are some flaws in Opera’s CSS2 support, probably in the generated-content area.

Remember that I said “Note that the section on counters and automatic numbering can be ignored, because no browser I know has implemented them correctly. Or at all.” There’s a difference implementing a thing and implementing it correctly, as the past five years have taught us all too painfully.

This is not meant to denigrate Opera: it has very good CSS support, especially in Opera 6. And it does seem to get counters mostly right (for example, see http://www.meyerweb.com/eric/css/tests/countertest.html), so I may have overstated my point a bit. I’d need to do far more extensive testing than I already have before I could say with certainty.

“Have I done something daft, or is this feature not supported in most of the currently-used browsers…? “

The selector in question will only “complete” ‘href’ values that begin with a ‘/’ character. For example, ‘/stories/goingtoprint’ would be “completed” by the rule I used, but ‘examples/ch1/figure07.jpg’ would not because it doesn’t start with a forward-slash. And so far as I know, it will only be handled by Mozilla and its variants, like Netscape 6.x, which have implemented the CSS3 selectors draft.

I’ve been using something similar on my resume page, where I have a link that switches the style of the page to a “printer friendly” version. I was using a JavaScript from the “Dreamweaver 4 Magic” book (which has some pretty good tricks in it, although I’ve been hand coding using HomeSite 5 now more and more lately). Maybe it’s the code, or the script, or just having 2 style declarations that screws it up. Either way, I’ve gotten rid of the script and now I’m only using the following in my head:

Great article, which seem to answer all my prayers, but I’m a bit new to developing and didn’t grasp everything.

I’ve got a DHTML menu bar, which is placed into DIV tags. This file is then use as an #include file within all my main pages. I don’t want the menu bar to be displayed when I print, can anybody help????

Since the include file is dropped in and actually becomes part of your page (the browser doesn’t know, only the server does), you could treat the navbar’s <div> the same way as any other HTML in your page.

Cheers Damien, I tried your method but still no joy, I think its down to the complexity of the DHTML nav bar, it use’s a couple of ‘JS’ include files and no matter what I try it still appears. Anyway i’ll solider on - much appreicated.

Leave it to ALA to put out another great article. I have become a CSS fanatic since I found this site and Have integrated all of what I have learned here in my web development in one way or another. This is a little off the subject, but does anyone know how to get the rotated 3-D text effect a la the logo for this printing article where it says “ala”?

Movement2.com is an ethical and ecological policy and lifestyle service.

We propose a life without the burden of property and the freedom of movement within Europe.

We enable our members to shape the ethical and ecological minds of in industry by using their collective buying as lobbying tool.

Our proposal is a housing system in which an individual buys into a network of homes instead of just one house. An individual can move freely within our EU wide system. All furnishing, utility billing and security is managed by us. It gives individuals the freedom of owning what they want not what they need.

I’m trying to get a banner which is set in the background to not repeat on the second and following pages. Is there an easy way to set the print style sheet so the banner displays only once. Here is a link, but it may not display correctly http://www.discoveringmontana.com:88/isd/css/about/bureaus_rb.asp

Eric, I was wondering if you’ve had a look at Printtopdf, a useful utility that acts as a desktop printer and lets you output PDFs from any application on a Mac.

It’s surpring how well your tips work with that program when you print from Netscape or IE. With only a little modification to your styles, you can output something really good.

I’d be interested in you taking a look at Printtopdf and maybe post your comments about how to modify your print styles to get flawless PDF prints. If you’d like some feedback from my meagre attempts, give me a yell.

I’m wondering if anyone has been experimenting with page-break-before or page-break-after. I’ve been working on a print style for a couple of MovableType sites and controlling page breaks in the monthly archives would be really helpful. So far I’ve not noticed any effect - are there any browsers that support this?

Not that long ago I was faced with the task of producing a lot of content for an intranet. The browser used was NN4.0 and I was told it “it has to print perfectly.” I kept trying to get my bosses to at least upgrade their browser but no. Nearly all the content ended up as .pdf (sob / scream in rage Delete where appropriate) How i wish my now former employers could see this article. Then again as they are still on NN4 I doubt they will.

The bits about links were great. Now to do a print version of my own site.

I’m using a print.css on the site I develop for as well. It is an elegant and simple solution that made the printed page look far better than it had before. This article was great for some new ideas (like the link options mentioned), but didn’t mention something I had noticed on our site. Opera (Version 6.01, Build 1041, Platform Win32, System Windows 2000, Sun Java Runtime Environment 1.3) seems to read the styles from both a print and screen style sheet when printing. In this case, the style sheets are called in the HTML with

The pages display just as expected on the screen, but when printing, both styles from insidepage.css and printss.css are used. This was easily fixed by using !important and styles in printss.css to overwrite where necessary. Unfortunately, we’ve run into a much harder problem to fix which I can detail in a separate post, but which would be fixed if Opera did not read insidepage.css when printing… Has nobody else experienced this? I would have expected to see it in the article if someone had.

Thanks for your great articles—there’s so much fantastic stuff to read, I’m having a hard time getting through them (especially when IE keeps crashing, argh).

Whenever I read stuff on style sheets, there’s the “make sure it works in old browsers that don’t support CSS” line. My question is, how do you make sure of this? I read that you can’t install older versions of IE because they stuff up the new ones. How do you get a hold of older browsers to check your sites for accessibility?

Excellent article. As always, EMeyer blosters the confidence of designers using CSS. However, I have encountered something of a bug in IE6/Win. Possibily some one out there can help…

Like the “Float Flub” mentioned for mozilla, this is appearing in IE/6 on long pages, but without the float anywhere to be found. I simply get the first page, followed by blank pages to the end of the print job.

The base CSS was taken from bluerobot’s layout reservoir for three column layouts. Anyone experiencing similar issues in IE6/Win?

Great article…I love using CSS…but I have run into a problemo.
I would like to use CSS for printer friendly pages, but I have text boxes that contain information my users would like to print. Is there any way using CSS to capture the content in the text boxes and print them?

I think I am resigned to using a combination of JavaScript (w/printer friendly button) and CSS.

OK. I know all the wonders you can do with CSS. ( I don’t fully know how to do them but I know they exist).
This is my question. What happens if I as a regular user want to actually print the side bars?? for example : there’s a coupon ( from one of these ad companies that give random ads) on the left bar that I want to print ? or a phone-number or address from a business on the right bar?
what if I WANT the whole page to be printed in the exact same way I see it on screen??
Should I mix some JavaScript and some buttons and <div’s> so I can give my user the options of
1. print the article (then use print.css)
2. print the whole page (use some other css suitable for print but that encloses every element on the page).
3. buttons to print the left, right side bar???

and then when they actually print the page get rid of the buttons using the <div> tag that encloses them??

As a developer I see the beneficial part of using CSS and not having to create a second version of the same page for printing purposes, but as a user I feel that somebody is TELLING me (not asking) what are the things I can and can’t print. Probably is just me. Don’t get me wrong I’m NOT against CSS, on the contrary I think is the best thing ever created for the web. Having a way to separate content from presentation is something that’s always welcome in my toolbox.
I’m just talking options here, not technical matters, options on what to print, that’s all.
fer

re: <a href=“http://www.alistapart.com/stories/goingtoprint/discuss/3/#ala-676”>Print Contents of a Text Box <a>—————————————————————————————————————————-
Just define your input elements in the print.css without the borders (or with borders dotted to make them easy to see and differentiate) and then adjust the font size and appereance of those elements to something you’d like to see on paper.
ie:
input{
border : thin dotted Black;
color : Red;
font : 12pt Arial, Helvetica, sans-serif;
background : transparent;
}

Got some problems solved!
I’m just experimenting with a redesign of my own page at http://www.xpw18.de - current efforts at http://www.xpw18.de/_demos/entwurf04/ - switching layout and markup to some style which is more simple and completely XHTML/CSS-based.
Had problems with Mozilla getting page breaks done when printing. I don’t have floating ‘divs’ there so I wondered where the problem was rising from. Found out that ‘position:absolute;’ in a ‘div’ for the main content caused the problem. IE5.5 doesn’t matter, it gets the page breaks while printing.
But there seems to be no possibility to get around the default printing margins the browser sets by itself. I know some people who set them to something about 2.5cm left and some 1.5cm top margin to get some comfortable space for older inkjet printers or for having the pages picked up in a folder.

Thanks for the great article. But I have a problem, u may help solving it. When a line comes at the end of a page, the text is clipped; meaning part of the text in one page and the remainin part in hte next page!
I am using IE6.
I would appreciate anyone tries to help (via email is recommended).

Hi Migs
Has your problem been sorted out? I have a similar problem and I tried wot Damien suggested but it aint working. Please let me know if its solved and if yes, how u did it. If anyone else knows about the how the problems with Div tag with #include is sorted out, ps. post it here. You could refer to a detailed problem at http://www.alistapart.com/stories/goingtoprint/discuss/2/#ala-448

Hi,
(this may not be the place to post this, and if it isn’t please forgive me ALA)

I’d already started using print specific css before I read this (and Eric’s) great articles.
I’ve got a situation which someone here might have come across and may be able to offer advice.
I’m having to print a table generated from a database via php, the table is an unknown number of rows and each row is an unknown size.
The current table prints over 15 pages (no problem getting to print multiple pages) but some of the page breaks cut in the middle of lines so the lines are illegible, and (this is really weird) the width of the table shrinks as you move through the pages!!

I have a feeling that you can’t have a clean page break within a continious table, but if anybody has any suggestions (especially about the width thing) I would be most grateful.

A post earlier by Peter Sheerin gave me the clue, I created another php output which formatted the document using tags instead of as a table.
Then in the table version I used a <link title=“Printer friendly version” type=“text/html” rel=“alternate” media=“print” href=“weeklyprint.php”>
which is called when someone presses print.

This must be so obvious that no-one mentions it ...cos I can’t find help on it anywhere, but how do I print from a browser without the infernal windows header and footers appearing? I just want them to go

We are experienced web developers. It seems, unless you are using HTML, you could check your server CGI variables, see if the browser is print friendly, include the css print style. (If not, let them use the browser print and blame the browser for non-compliance!) Not supporting any browser over another here, but the standards should be supported by any major browser.

Great article. Had experimented with this but now I can eliminate the print-friendly page.
Anyone know when page-break-inside will be supported? Can’t find anything on this, although it’s in CSS2 it’s is not supported anywhere. Page-break-before and after seem to work.

I am trying to use your example css on my company test site, but am having problems with the margin, the left margin in particular - it’s half-a-page wide, no matter which browser I print from, no matter what I set the margin percentage to, it just will not print to the left margin of the pager. Too weird. I ‘ve tested in IE6, Netscape7, Mozilla 1.1 and Opera 5 and 6. Then after that gets resolved there is the font size issue…

So I’ve got the whole print css thing working, I can’t believe I never thought of this. :) Now I know you can set the page to print landscape or portrait, but with the footer, is there a way to make sure that it is always a the bottom of a page that I print, even if there is a lot of blank whitespace?

Great article! I used it to create print and screen stylesheets - great results. Question: when updates are made to some pages, I change the BGCOLOR to “highlight” them. How can I preserve that effect in the print version? I have tried BODY {
font-size: 10pt;
background: inherit;
background-color: inherit;
}
but had no luck. Thanks!

Awesome article! I have definate need of being able to print web pages from our intranet. I’m fairly new to CSS, so what is happening when you included “!important” in your float definition for #wrapper or #content? It’s not a comment (\* , *\), right?

A colleague has the problem of putting headers and footers on pages when printed out. I referrred him to this article, but that particular feature doesn’t seem to have been mentioned. I intend to dig into my css reference books, since css isn’t my main specialty, I thought I ask for pointers. Anyone?

i use a xerox docuprint 4508. all the lights are flashing eg paper jammed. paper empty etc and it will not print. obviously the paper is not the problem yet this message flashes on screen also, printer out of paper, can some one advise… anne

I recently replaced ink cartridges (on my Canon S750 printer) and I can no longer print e-mail. It will print when I highlight, “Copy” and “Paste” the subject onto “Write”. I was able to always print out e-mail or whatever from it’s original display prior to the ink replacement. What did I do wrong?
Thanks for any help.

Someone asked about !important. I hadn’t remembered seeing that before either. It is explained here: http://www.w3.org/TR/REC-CSS1#important

Basically, if I understand it correctly, by adding !important to a style, that style is forced to take precedence even when another style may normally take precedence by default. So by adding !important to a style that is absolutely necessary (for printing in this case) we do not have to worry about it being overridden by, say, a style defined within the body of the doc. (Could this be a solution to a few problems some have mentioned here?)

Btw, the above reference is only part of a section which explains how one style gets preference over another. The entire section 3 may be helpful to anyone that is not sure how this works.

Some have taken issue with the lack of a printer friendly link when utilizing this solution. Some workarounds have been addressed by others. If you must you can still create such a page, although I like the suggestion to use some very simple javascript to simply print the current page.

However, in my experience, the average user often overlooks the printer friendly link and complains that pages do not print in such a way that they are readable, thereby negating the value of the option. This alleviates that problem by ensuring that all pages look as intended when printed, no matter the level of the user (which makes it the best solution in my view). And if you feel obligated to provide the link for the more knowledgable/ observant, then by all means do.

Thank you ala for providing another great article (to bad I didn’t read it sooner). Even the least intelligent of visitors to my sites can get the intended results whenever I follow your excellent advice.

This was a great article, as have been all the ones I’ve read here. But I still have a question about something that’s happening to a site I’m working on. If you go to this page http://www.sassllc.com/index.asp and do a Print Preview, it looks OK. But if you go to http://www.sassllc.com/FAQ.asp and do the same, the text gets squeezed to the left of the content box.

Am I missing something really obvious?

Thanks so much! (If there’s a more proper place for me to be asking this, please let me know and I will forthrightly comply!)

Hi, im new at css and i need this. I want a print this button on my page so im gonna have that link to a new page and i wanna put in this code to make it printer ready.. Now if anyone has any better ideas i would like to know :). But i dont really understand this code, well some of it. Could someone, very simply, tell me exactly where i need to put everything and what i need to change. Thanks!

Its me again, same guy as before. Ok say i already have a style sheet on my page, because i already do. This will still work with it right?? Another question is, does this only make the printed page come out different it doesnt make it on the net look different??? I need to know how to use this because im very new at css and this is complicated, ahhhhh. By the way, i want to also make a print this icon. How would i make that work so it automatically printed?

Great article and making me change how our new site is formatted. However…
Like someone else in this thread I have menus on the left and removing them with display: none just leaves a blank space with the content still shifted across the page.
How do I get the content back to use the empty space to the left?

I’ve used the similar
http://alistapart.com/stories/alternate/
alternate CSS to create a fixed point font size for printing. But both on that, and also your sample page, my IE6 continues to print as if the screen font is not changed. (NN6 is fine though). In other words, IE6 completely disregards the visible changes on the screen, although it DOES print out according to size if I use the mousewheel to resize the print.

Is this a known Win IE6 problem? Is it my setup? Is there any way round it?

But I found that when I validated the CSS by URI it did so but the validator gave me warnings saying that I had several redefinitions in my CSS. Obviously the W3C validator reads both style sheets and adds them together, I don’t know. So I searched for a hack and couldn’t find anything until I came across the @ media tag.

Within my style sheet (styles.css) I added the following:

@media print {

/* I then cut and pasted my print style sheet into this section */

}

It worked great and validated correctly, naturally that meant I could remove the line.

While I find the solution discussed in this article interesting, sometimes you want to offer visitors more than just the same page with different looks.

Is it possible to instruct the web browser to choose a specific document when the user wants to print a page? Something like
<link rel=“printable” href=“resume.pdf” />
that basicallt says: “if the user wants to print this page, use the document resume.pdf”.

This is a great article but I’m working with a site currently built with tables. Most of the code has worked (getting rid of graphics, changing fonts, etc.), but my text is being cut off by the right margin of the printed page. I’m not sure if this is b/c of tables or some other problem. The content is the center column of a three column table. Left and right columns are set to display:none. Any ideas?

I printed this article in Safari 1.0 (v85) and the main content wrapped to a column only about 25% the width of the page. From IE, it looked fine. Is there a something in the CSS that can fix this? Or perhaps it’s a browser-bug?