[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: <title> element forces inconsistent semantics
as i just found out the hard way, a <qandaset> element that has a <title> will consult the appropriate attribute-set "section.title.level1.properties", which may in fact introduce a page break before that <qandaset>. it's not so much that this is non-intuitive, but that it's inconsistent. as i read it, the <qandaset> itself is not what causes the page break -- only the fact that it has a <title>. removing its child <title> element removes the i(potential) page break. this is inconsistent since other elements (the lists, for example), can also have a <title> element, but those will *not* cause a page break. this is inconsistent as there is nothing to suggest why a <qandaset> should somehow be treated differently in this respect. either all <title>s should have this effect, or none of them. rday
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]