mediawiki-skins-Vector/resources/skins.vector.styles/print.less

226 lines
4 KiB
Plaintext
Raw Normal View History

@import '../../variables.less';
@wmui-color-base0: #000;
@color-base: @wmui-color-base0;
@border-color-base: @wmui-color-base0;
@border-color-footer: #eee;
@media print {
/* These styles retain the existing typography in screen.less
In future (when deploying these styles) we may want to refactor skins.vector.styles
to apply certain styles in print as well as screen mode. */
.toc,
body {
padding: 10px;
font-family: @font-family-serif;
}
// Tables, thumbs and lists are sans-serif in print mode (unlike screen mode) because these will render
// more legibly on print media in a smaller font sizes
.printfooter,
#footer,
.thumb,
table,
ol,
dl,
ul,
h3,
h4,
h5,
h6 {
font-family: @font-family-sans;
}
// Images, such as formulas, render best in serif. Math fallback images, for example, have an
// inline style attribute setting their dimensions in ex (x-height) units, which is relative the
// font size:
// <img
// src="https://wikimedia.org/api/rest_v1/media/math/render/svg/d03b01348b751e6f4eaff085b3effa9542e2935d"
// class="mwe-math-fallback-image-inline"
// aria-hidden="true"
// style="vertical-align: -2.171ex; width: 11.418ex; height: 5.676ex;"
// alt="r_{s}={\frac {2GM}{c^{2}}}">
img {
font-family: @font-family-serif;
}
// Normalize Blue links in the article
a:not( .image ) {
border-bottom: 1px solid #aaa;
}
.firstHeading {
font-size: 25pt;
line-height: 28pt;
margin-bottom: 20px;
padding-bottom: 5px;
}
// Headings
.firstHeading,
h2 {
// To avoid the bottom border of section headings with floated elements
overflow: hidden;
border-bottom: 2px solid @border-color-base;
}
h3,
h4,
h5,
h6 {
margin: 30px 0 0;
}
h2,
h3,
h4,
h5,
h6 {
padding: 0;
position: relative;
}
h2 {
font-size: 18pt;
line-height: 24pt;
margin-bottom: 0.25em;
}
h3 {
font-size: 14pt;
line-height: 20pt;
}
h4,
h5,
h6 {
font-size: 12pt;
line-height: 16pt;
}
p {
font-size: 12pt;
line-height: 16pt;
margin-top: 5px;
text-align: justify;
// T175008
// When a paragraph is surrounded by floating elements from both
// sides, we want to make sure that there is at least some space
// before showing the text. Otherwise, small lengths of text may show
// between the surrounding elements, making the reading experience less
// enjoyable. If there is not enough space the following code will push
// the paragraph contents until after the floating element(s).
&:before {
content: '';
display: block;
width: 120pt;
overflow: hidden;
}
}
blockquote {
border-left: 2px solid @border-color-base;
padding-left: 20px;
}
ol,
ul {
margin: 10px 0 0 1.6em;
padding: 0;
li {
padding: 2px 0;
font-size: 12pt;
// T178667: Inline lists in new print styles should not
// have a smaller font size than surrounding content
table & {
font-size: inherit;
}
}
}
.toc {
page-break-before: avoid;
page-break-after: avoid;
background: none;
border: 0;
display: table;
a {
border: 0;
font-weight: normal;
}
> ul {
> li {
margin-bottom: 4px;
font-weight: bold;
}
}
ul {
margin: 0;
list-style: none;
ul {
padding-left: 30px;
}
}
li.toclevel-1 {
> a {
font-size: 12pt;
font-weight: bold;
}
}
Re-implement and improve mw-jump links with pure CSS * Improve their accessibility by giving both links a full label "Jump to x" and "Jump to y" instead of "Jump to: ", "x", "y". This also makes things much better for localisation, for which we generally discourage use of concatenation. * Use pure CSS for the toggling of the visibility on focus, instead of relying on JavaScript. Especially given the JS comes form core's 'jquery.mw-jump' module, which is considered technical debt per T195256. Alternatively, that could be copied to vector.js, but pure CSS is possible, so why not. * Use plain <a> links in the HTML instead of wrapped in a <div>. This solves the long-standing problem whereby the margin between #contentSub and #mw-content-text had to be awkwardly negated and overridden in core and on various to make sure that the wrapper itself would become visible as needed, in a way that has margin around this. This whole problem doesn't apply when simply using inline links that aren't part of the regular flow with .mixin-screen-reader-text. On focus, the individually focussed link appears in regular flow, without the need for any custom styles. * This uses :not(:focus) to naturally make it render in the default way on focus, and visibibly hidden/clipped otherwise. This is supported in IE9+ and Android 2+. There is a way to make it work with CSS2 for IE7-8, by applying the mixin to '.mw-jump-link' only and then undoing all of 'position', 'width', 'height', 'clip', and 'margin' on :focus. But I'm not sure that's worth it here. The fallback in IE7-8 for not supporting ":not(:focus)" is that the accessibility link is simply visible always, which seems like a good fallback for accessibility, and doesn't hurt anything. Bug: T195256 Change-Id: Icaadb290f692b3617688d32cbb66dfb007f1c82c
2018-05-21 16:28:07 +00:00
}
Re-implement and improve mw-jump links with pure CSS * Improve their accessibility by giving both links a full label "Jump to x" and "Jump to y" instead of "Jump to: ", "x", "y". This also makes things much better for localisation, for which we generally discourage use of concatenation. * Use pure CSS for the toggling of the visibility on focus, instead of relying on JavaScript. Especially given the JS comes form core's 'jquery.mw-jump' module, which is considered technical debt per T195256. Alternatively, that could be copied to vector.js, but pure CSS is possible, so why not. * Use plain <a> links in the HTML instead of wrapped in a <div>. This solves the long-standing problem whereby the margin between #contentSub and #mw-content-text had to be awkwardly negated and overridden in core and on various to make sure that the wrapper itself would become visible as needed, in a way that has margin around this. This whole problem doesn't apply when simply using inline links that aren't part of the regular flow with .mixin-screen-reader-text. On focus, the individually focussed link appears in regular flow, without the need for any custom styles. * This uses :not(:focus) to naturally make it render in the default way on focus, and visibibly hidden/clipped otherwise. This is supported in IE9+ and Android 2+. There is a way to make it work with CSS2 for IE7-8, by applying the mixin to '.mw-jump-link' only and then undoing all of 'position', 'width', 'height', 'clip', and 'margin' on :focus. But I'm not sure that's worth it here. The fallback in IE7-8 for not supporting ":not(:focus)" is that the accessibility link is simply visible always, which seems like a good fallback for accessibility, and doesn't hurt anything. Bug: T195256 Change-Id: Icaadb290f692b3617688d32cbb66dfb007f1c82c
2018-05-21 16:28:07 +00:00
.mw-jump-link,
.toc .tocnumber {
display: none;
}
.printfooter {
margin-top: 10px;
border-top: 3px solid @border-color-base;
padding-top: 10px;
font-size: 10pt;
clear: both;
}
#footer {
margin-top: 12px;
border-top: 1px solid @border-color-footer;
padding-top: 5px;
}
#footer-info {
margin: 0;
padding: 0;
li {
color: #999;
list-style: none;
display: block;
padding-bottom: 10px;
font-size: 10pt;
a {
// override default black print style.
color: #999 !important; /* stylelint-disable-line declaration-no-important */
}
}
}
// Last updated as primary info.
#footer-info-lastmod {
color: @color-base;
font-size: 12pt;
font-weight: bold;
}
}