RE: Predictability of rendering regions on the page

Ken,

The XSL FO SG discussed making z-index applicable to region-*
in XSL 1.1.  Unfortunately, things are more complicated than
they seem, and it was decided that we have to cut off changes
to XSL 1.1 if we are ever going to get it out, so we have
decided not to make such a change.

[Things are more complicated because some SG members have 
plans to come up with a more general region capability that 
needs to be upward compatible with the current regions, but 
this more general thing--for reasons I don't understand fully 
myself--can't necessarily use z-index.]

Apparently, this leaves you having to determine for each 
implementation how it layers region-* and putting in 
implementation-dependent code to account for this.

paul
(on behalf of the XSL FO SG)

> -----Original Message-----
> From: xsl-editors-request@w3.org 
> [mailto:xsl-editors-request@w3.org] On Behalf Of G. Ken Holman
> Sent: Friday, 03 June, 2005 21:32
> To: XSL Editors; XSL-FO W3C; XSL-FO-Yahoo List
> Subject: RE: Predictability of rendering regions on the page
> 
> 
> At 2005-06-03 16:16 -0400, Paul Grosso wrote:
> > > From: xsl-editors-request@w3.org On Behalf Of G. Ken Holman
> > > Sent: Friday, 03 June, 2005 9:17
> > > To: XSL Editors; XSL-FO W3C; XSL-FO-Yahoo List
> > > Subject: Predictability of rendering regions on the page
> > > ...
> > > Does XSL-FO 1.0 dictate that the perimeter regions are
> > > rendered before the body region?
> >
> >No.
> >
> > >
> > > Does XSL-FO 1.0 dictate that the static content is rendered
> > > before the flowed content?
> >
> >No.
> 
> Drat!  This is quite necessary for what I need to accomplish.
> 
> > > I cannot, however, find any predictability in the XSL-FO 1.0
> > > specification
> > > ... perhaps I just cannot find it ... if it isn't there, can
> > > the XSL-FO 1.1 specification dictate this?
> >
> >I don't think it should.  That is getting to close to
> >specifying a processing model.
> 
> Good point, I can see that to be true.
> 
> >XSL-FO tries to avoid
> >that and instead specifies constraints that should hold
> >for the composed result.
> 
> Yes, of course ... I just had not considered ordering to be 
> related to processing.
> 
> >I'd think a better way to accomplish this would be to
> >use the z-index property, but I note z-index is not
> >applicable to region-*.
> 
> Indeed.
> 
> >So your request should be for the XSL FO SG to consider
> >adding z-index to the list of properties applicable to
> >the region-* FOs in XSL 1.1.  [I have no idea what the
> >SG members will think of this.]
> 
> I hope the SG members do consider this worthwhile as it would bring 
> predictability to my real-world requirement of overlapping regions.
> 
> Having included XSL Editors on this list, I hope this note is 
> sufficient to the task of requesting such a feature.
> 
> >paul
> >(just speaking for myself)
> 
> Thank you, Paul, for your opinion and for bringing light to 
> an aspect of my request of which I was unaware.
> 
> . . . . . . . . . . Ken
> 
> --
> World-wide on-site corporate, govt. & user group XML/XSL training.
> G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
> Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/f/
> Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
> Male Breast Cancer Awareness  http://www.CraneSoftwrights.com/f/bc
> Legal business disclaimers:  http://www.CraneSoftwrights.com/legal
> 
> 
>

Received on Tuesday, 21 June 2005 21:08:05 UTC