- From: Lea Verou <lea@w3.org>
- Date: Wed, 31 Jul 2013 20:20:53 +0300
- To: Brad Kemper <brad.kemper@gmail.com>
- Cc: Alan Stearns <stearns@adobe.com>, Håkon Wium Lie <howcome@opera.com>, www-style list <www-style@w3.org>
I think this is very intuitive too, it's what I first tried when I realized it didn't work and did some research on whether CSS rules are allowed within @page rules.
Lea Verou
W3C developer relations
http://w3.org/people/all#lea ✿ http://lea.verou.me ✿ @leaverou
On Jul 31, 2013, at 20:15, Brad Kemper <brad.kemper@gmail.com> wrote:
>
>
> On Jul 30, 2013, at 6:14 AM, Alan Stearns <stearns@adobe.com> wrote:
>
>> That's what Lea was originally asking for. I think it would be a good
>> thing to add. I think float:outside/inside are fine as well. But a general
>> mechanism for styling content on left/right pages would be better than
>> adding special-case values to each property you might want to change
>> depending on the spread location.
>
> Let us also not forget :first pages and named pages, which @page can select as easily as :left and :right. Thus, if the mechanism is an @content{} block with rulesets within, itself inside the @page{} block, then it would be a good general way of styling content based on if it appears in right/left/first/or other special pages.
Received on Wednesday, 31 July 2013 17:21:16 UTC