Unfortunately there is not a good answer to your question – but maybe if you understand the why’s then you can choose a way forward.
Why?
It’s true that Bootstrap uses the @media print { * { color: $fff; background: transparent; }} — but there is a very solid reason. This bit of code is actually derived from the normalizer.css project (by a then college of @mdo ‘s, @necolas) – it’s intent is to make all browsers behave the same. These guys chose to “normalise” the css for a very good reason:
With most browsers one can choose to include or exclude background color, so the behaviour is not standard across even the same browser. Imagine for a sec a website with very dark background with white text – when printing with backgrounds off, it will look like you’re printing nothing – when actually you’re printing white text on no (white) background.
There was no way to account for all the different uses of color, so they choose to go black (font) and white (background, actually ‘transparent’). Even the choice of black was well thought of — its a better print solution, as most color printers have more black “ink/toner” (more economical) and they don’t need to mix color to make black (so faster).
Remember that Bootstrap is also a “framework” – so a starting point if you will – and kudos to @mdo and @necolas for having the foresight to think of this in terms of establishing a predictable baseline. (No, I don’t know them.)
Nope…
So the thinking here is: “what if we could ‘go back’ and unset this. Unfortunately CSS does not work like that – yes browsers load the CSS declarations in a “queue” where the last declaration wins (LIFO, or last-in-first-out), but I’m not aware of a way to remove this stack. So CSS developers just add more to the end…
So one would assume that we can go back that way — add a * { background-color: inherit }. Problem is that inherit reverts to the parent property, but * is the root, so it has nothing to revert to. Same goes for initial!
Maybe!
So we’re left with 4 options, none of them is what you where hoping for, but it is what it is. In order of difficulty:
- Download the BS (less or sass) source, edit the offending code, and then compile it. (You need to use a local copy, CDN’s will not work.)
- Download the CSS variant of your choice, search and delete the offending code. (No CDN’s again.)
- Use getbootstrap.com/customize to create a new variant – exclude “Print media styles” under “Common CSS”. (Again, no CDN’s)
- Override the specific items who’s color you want to print: e.g.
@media print {
.alert-danger {
color: yellow !important;
background-color: red !important;
}
}
CDN’s copies of BS will now work, but then you have the problem of the user possibly not printing backgrounds and having the output white (yellow in the e.g.) on white!
Finally
Well I hope learning the why’s was at the very least a way of you thinking of a workaround. General rule of thumb I follow is that when printing, the background is (should be) always white. When constrained that way you start thinking of novel ideas, like exclamation icons around the text that only “print” (@media only screen { .hidden-screen { display: none; }})