office-gobmx/sw/qa
Miklos Vajna 607fcac441 tdf#160067 sw floattable: fix missing move bwd of paras in split section frame
The last (5th) paragraph in the index was on page 2, even if page 1
still had space for it.

This is a regression from commit
397d72e582 (Related: tdf#158986 sw
floattable: fix unexpected page break with sections, 2024-02-23), in
case SwLayAction::FormatLayout() doesn't calc its lower content frames
then this bugdoc is good, but the old bugdoc moves its floating table to
the next page, which would be bad.

Fix the problem by making the condition for this "calc lower in
FormatLayout()" action more strict: only do this for content frames
which are in sections, followed by sections.

Note that probably a cleaner way would be to completely stop calculating
content frames in SwLayAction::FormatLayout() and only do that in
FormatContent(), but then it's not clear how to re-fix tdf#158986, and
at least this resolves the regression.

Change-Id: Id671b3b68d8af8ad1cca3399a9aa028de58df3a0
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165878
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
Tested-by: Jenkins
2024-04-08 08:05:33 +02:00
..
api
complex/indeterminateState
core tdf#160067 sw floattable: fix missing move bwd of paras in split section frame 2024-04-08 08:05:33 +02:00
extras tdf#160526, tdf#160549: fix split conditions at page start 2024-04-07 18:46:59 +02:00
filter
inc CppunitTest_sw_htmlexport: use more CPPUNIT_TEST_FIXTURE() 2024-03-27 09:33:15 +01:00
python tdf#158803 Remove unused imports from uitest 2024-03-28 16:13:25 +01:00
uibase CppunitTest_sw_uibase_uiview: turn on set_non_application_font_use 2024-03-21 21:12:05 +01:00
uitest disable part of tdf150443 UITest for now 2024-03-28 19:12:20 +01:00
unit
unoapi
README

You can find different types of Writer tests here, the following directories
are available:

- core:
  - filters-test: loads different file types (see SwFiltersTest::testCVEs() for
    the list of supported filter types), and only makes sure Writer does not
    crash. To add new tests, you just need to drop in the test files to the
    relevant directory, no code change is necessary.
  - uwriter: this test has access to private Writer symbols, add new tests here
    if you need that.
- extras:
  - see its own README -- executes import and export filters and asserts the
    UNO model to verify the resulting document is the expected one.
  - also, any new C++ test that links to libsw (but does not need access to
    private Writer symbols) should go in this directory, whether using the UNO
    API or the internal one.
- complex: JUnit-based tests using the UNO API
- unoapi: JUnit-based test trying to get/set every UNO property, etc.