W3C home > Mailing lists > Public > www-style@w3.org > April 2015

Re: [css-page-floats] First cleanup

From: Håkon Wium Lie <howcome@opera.com>
Date: Tue, 7 Apr 2015 23:01:25 +0200
Message-ID: <21796.17829.545952.594410@opera.com>
To: Johannes Wilm <johanneswilm@vivliostyle.com>
Cc: www-style list <www-style@w3.org>, public-ppl@w3.org
Also sprach Johannes Wilm:

 > >  > I can also see that Inside/outside can be helpful, but this is for page
 > >  > based media in general, not specific for floats. And from what I can tell,
 > >  > the same effect can be achieved by setting separate styles for @page :right
 > >  > and @page :left, right?
 > >
 > > That's different. Floting inside/outside lets you do things like:
 > >
 > >   aside {
 > >     float: outside;
 > >     float-offset: -80mm;
 > >     width: 75mm;
 > >   }
 > 
 > And that would be different from
 > 
 > aside {
 >   float-offset: -80mm;
 >   width: 75mm
 > }
 > 
 > @page:right {
 >   aside {
 >    float: right;
 >   }
 >  }
 > 
 > @page:left {
 >   aside {
 >    float: left;
 >   }
 >  }
 > 
 > in the cases when the aside ends up being floated to a different page than
 > where the float reference is?

Ok, I see what you mean. Yes, if you were able to select elements
based on which page they end up on, we could achieve the same (and
more(. However, that's quite far ahead -- there are no known
implementations of this and the spec is highly experimental:

  https://books.spec.whatwg.org/#selecting-elements-within-pages

OTOH, "float: outside/inside" has been interoperably implemented for years.

 > > Can't we just say that "inside" and "outside" are alises for "left"
 > > and "right", depending on which page the float ends up on?
 > 
 > 
 > Ok, so inside/outside would be mapped to left/right, which again are mapped
 > to inline-start/end in horizontal writing modes and block-start/end in vertical
 > writing modes, correct? I can add that, if it's not to be more complex.

In my mind, all properties map to left/right. 

 > > Prince and AntennaHouse have implemented these, so I don't think it's
 > > awfully hard. (Their programmers may correct me on this.)
 > 
 > I implemented sidenodes myself using Javascript in BookJS, and I covered
 > points 1-4 but not 5 and 6 there. It's not impossible to do, but it means
 > implementing a lot of logic and even different book styles may decide to do
 > them differently (for example: sidenodes may placed next to footnotes or
 > they may end where the body text ends). If the outside/inside is meant to
 > make the creation of sidenodes possible, I'm afraid that won't be enough.

It's sidenotes on the cheap. For example, it falls apart when you're
in a multicol environement. For more advanced sidnotes, you need
something like named areas:

  https://books.spec.whatwg.org/#named-areas

-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Tuesday, 7 April 2015 21:01:54 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:30 UTC