Commit e8dc9a98 authored by julientaq's avatar julientaq
Browse files

fix print

parent a5b8c9bb
......@@ -34,6 +34,6 @@ To date, the specifications for print/paged media have been developed under the
So, during the final conversation, rather than make a wish list of new specifications, we focused on the process: how can we work more effectively with the CSS working group (CSS WG)?
As Liam Quin said in the conclusion of his presentation, "nothing will go forward until the stakeholders are proactive." During this workshop, we could see that there is a core of people very interested in what's going on today with CSS for print and paged media. At the end of the workshop, a new community group was established as a place of our own to raise issues before bringing items to the CSS working group. Dave Cramer, supported by some of the participants, proposed this new group be added to the W3C as the **CSS Print Community Group**.
As Liam Quin said in the conclusion of his presentation, "nothing will go forward until the stakeholders are proactive." During this workshop, we could see that there is a core of people very interested in what's going on today with CSS for print and paged media. At the end of the workshop, a new community group was established as a place of our own to raise issues before bringing items to the CSS working group. Dave Cramer, supported by some of the participants, proposed this new group be added to the W3C as the CSS Print Community Group.
The purpose of the group is to “work together to gather use cases, help with specifications, and advocate for more and better implementations”. At the end of the day, the community group was launched and accepted in the list of the current W3C community group: [https://www.w3.org/community/cssprint/](https://www.w3.org/community/cssprint/.). You don't need to be part of W3C to join it, so jump in!
---
title: "Our position paper for the W3C CSS print workshop"
title: "Our position paper for the W3C CSS print workshop"
date: 2020-02-14T11:19:56+01:00
draft: false
class:
......@@ -7,7 +7,7 @@ intro: "With the upcoming W3C workshop on CSS print in Prague, we put together t
author: "the Paged.js folks"
---
# Paged.js
# Paged.js
*Position paper for the W3C Workshop on CSS Print (February 13th, 2020)*
......
{"Target":"css/main.min.0dfa4643922d6dace8c65176d325fe3f.css","MediaType":"text/css","Data":{"Integrity":"md5-DfpGQ5ItbazoxlF20yX+Pw=="}}
\ No newline at end of file
{"Target":"css/main.min.220dca945c76dc985ceccc22c9c54660.css","MediaType":"text/css","Data":{"Integrity":"md5-Ig3KlFx23Jhc7MwiycVGYA=="}}
\ No newline at end of file
......@@ -152,12 +152,14 @@
@media print {
body {
display: block;
margin: 0;
padding: 0;
}
footer {
position: running(footer);
font-size: 0.8em;
......@@ -172,6 +174,7 @@
#title {
string-set: title content(text);
font-size: 3em !important;
}
body {
......@@ -180,14 +183,11 @@
orphans: 3;
}
header {
#title,
.intro {
text-shadow: none;
}
.intro {
page-break-after: always;
break-after: page;
}
}
#print {
display: none;
......@@ -219,9 +219,14 @@
margin: 0;
display: block;
font-size: 14px;
h2, h3 {
padding-top: 0;
margin-top: 2em;
}
}
.menu {
.menu.hide, .menu {
display: none;
}
......@@ -255,7 +260,7 @@
width: 14ch;
path {
fill: white;
fill: black;
}
}
}
......
......@@ -43,9 +43,11 @@ article {
max-width: 60ch;
}
strong {
font-family: var(--font-sans);
font-family: 0.95em;
/* font-family: var(--font-sans); */
/* font-size: 0.85em; */
text-decoration: underline;
font-weight: 500;
line-height: 0;
}
li {
max-width: calc(60ch - 10ch);
......@@ -162,7 +164,7 @@ article {
h3 {
font-size: 1.375em;
padding-top: 3em;
margin-top: 0;
}
h4 {
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment