Don't Break Table Rows Around Floating Tables.When the object is serialized out as xml, its qualified name is w:doNotBreakConstrainedForcedTable.
Assembly: DocumentFormat.OpenXml (in DocumentFormat.OpenXml.dll)
'Declaration Public Class DoNotBreakConstrainedForcedTable _ Inherits OnOffType 'Usage Dim instance As DoNotBreakConstrainedForcedTable
public class DoNotBreakConstrainedForcedTable : OnOffType
[ISO/IEC 29500-1 1st Edition]
126.96.36.199 doNotBreakConstrainedForcedTable (Don't Break Table Rows Around Floating Tables)
This element specifies whether applications shall allow a table row to be split in two when its contents are displayed under the following circumstances:
The table row exceeds one page in height (it shall be split into two pages)
The table row would need to be split in order to accommodate a floating table also on the page (tables which have been set to floating using the tblpPr element (Part 1, §17.4.58))
Typically, assuming the cantSplit property (Part 1, §17.4.6) is not set, a table row which cannot fit on one single page shall be split as needed around any floating table on a page, in order to allow its contents to be fully displayed across two or more pages. This element, when present with a val attribute value of true (or equivalent), specifies that table rows which exceed one page in height shall never be split around floating tables in the document, and shall instead be displayed on the first page below the floating table, even if that means that part of the table row is clipped by the edge of the page.
[Example: Consider a WordprocessingML document with a long single table row which must be split across two separate pages in the document, in order to accommodate a floating table anchored in the footer, as follows:
The default presentation of this document forces that row to be split as needed around that floating table.
However, if this compatibility setting is turned on:
<w:compat> <w:doNotBreakConstrainedForcedTable /> </w:compat>
Then that table row is never split around the floating table, so it is always placed below that floating table on the page, and allowed to flow off the page as needed, resulting in the following output:
This example, while extreme, shows how the row is placed below the floating table, rather than breaking around it. end example]
compat (Part 1, §188.8.131.52)
This element’s content model is defined by the common boolean property definition in Part 1, §17.17.4.
© ISO/IEC29500: 2008.
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.