ISSUE-48: Where is content displayed if the next page doesn't have a slot for it?

differing page templates

Where is content displayed if the next page doesn't have a slot for it?

State:
RAISED
Product:
CSS3 Template Layout
Raised by:
Bert Bos
Opened on:
2008-05-14
Description:
It is possible to attach a template to '@page :first' that is different from the template attached to '@page', e.g.,

@page :first {
display: "ab" "cd"
}
@page {
display: "ab" "cc"
}

In this case, content that overflows slots a, b or c will find a place on the next page(s), but where does content go that overflows slot d if that slot's 'overflow' property is not 'hidden'?

1) It is not displayed, because there is no slot for it.

2) It is displayed in the default slot of the next page (i.e., slot '@' or the top left one).

(The same may happen with named pages, if named pages can be forced to not repeat, as http://www.w3.org/Style/Group/css3-src/css3-gcpm/Overview.html#named3 currently proposes.)

On the principle that content should not be hidden from readers unless the author is explicit about hiding it, option 2 seems the best. It may destroy a layout, but then at least it is clear that something is wrong...
Related Actions Items:
No related actions
Related emails:
  1. [CSSWG] Resolutions August F2F: CSS2.1 (from fantasai.lists@inkedblade.net on 2008-09-08)
  2. [CSSWG] Minutes F2F 2008-08-20 (from fantasai.lists@inkedblade.net on 2008-09-08)
  3. Minutes ftf Wed Aug 20, 2008, am (from bert@w3.org on 2008-09-03)
  4. Re: [css3-fonts] Nested 'bolder' and 'lighter' question (from brkemper.comcast@gmail.com on 2008-08-29)
  5. Re: [css3-fonts] Nested 'bolder' and 'lighter' question (from jackalmage@gmail.com on 2008-08-29)
  6. Re: [css3-fonts] Nested 'bolder' and 'lighter' question (from bert@w3.org on 2008-08-29)
  7. Re: [css3-fonts] Nested 'bolder' and 'lighter' question (from dbaron@dbaron.org on 2008-08-28)
  8. Re: Agenda CSS WG Conf Call 10-june - CSS2.1 Issues (from fantasai@inkedblade.net on 2008-06-10)
  9. Re: [CSS21] Remove some old bolder/lighter text that disagrees with new (from fantasai.lists@inkedblade.net on 2008-06-10)
  10. ISSUE-48 (differing page templates): Where is content displayed if the next page doesn't have a slot for it? [CSS3 Template Layout] (from sysbot+tracker@w3.org on 2008-05-14)

Related notes:

No additional notes.

Changelog:

Created issue 'Where is content displayed if the next page doesn't have a slot for it?' nickname differing page templates owned by Bert Bos on product CSS3 Template Layout, description 'It is possible to attach a template to '@page :first' that is different from the template attached to '@page', e.g.,

@page :first {
display: "ab" "cd"
}
@page {
display: "ab" "cc"
}

In this case, content that overflows slots a, b or c, will find a place on the next page(s), but where does content go that overflows slot d if that slot's 'overflow' property is not 'hidden'?

1) It is not displayed, because there is no slot for it.

2) It is displayed in the default slot of the next page (i.e., slot '@' or the top left one).

(The same may happen with named pages, if named pages can be forced to not repeat, as http://www.w3.org/Style/Group/css3-src/css3-gcpm/Overview.html#named3 currently proposes.)

On the principle that content should not be hidden from readers unless the author is explicit about hiding it, option 2 seems the best. It may destroy a layout, but then at least it is clear that something is wrong...' non-public

Bert Bos, 14 May 2008, 12:34:10

Description changed to 'It is possible to attach a template to '@page :first' that is different from the template attached to '@page', e.g.,

@page :first {
display: "ab" "cd"
}
@page {
display: "ab" "cc"
}

In this case, content that overflows slots a, b or c will find a place on the next page(s), but where does content go that overflows slot d if that slot's 'overflow' property is not 'hidden'?

1) It is not displayed, because there is no slot for it.

2) It is displayed in the default slot of the next page (i.e., slot '@' or the top left one).

(The same may happen with named pages, if named pages can be forced to not repeat, as http://www.w3.org/Style/Group/css3-src/css3-gcpm/Overview.html#named3 currently proposes.)

On the principle that content should not be hidden from readers unless the author is explicit about hiding it, option 2 seems the best. It may destroy a layout, but then at least it is clear that something is wrong...'

14 May 2008, 12:34:48


Peter Linss <peter.linss@hp.com>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>, Chairs, Chris Lilley <chris@w3.org>, Bert Bos <bert@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.323 2013-12-19 14:47:09 dom Exp $