Bug 164491 - LAYOUT: AS_CHAR image lost
Summary: LAYOUT: AS_CHAR image lost
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.6.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: Writer-Images DOCX-Anchor-and-Text-Wrap
  Show dependency tree / graph
 
Reported: 2024-12-27 20:20 UTC by Justin L
Modified: 2025-01-11 01:47 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Attachments
tdf111341-6.docx_mso.pdf: how it looks in Word 2019 (75.25 KB, application/pdf)
2024-12-27 20:20 UTC, Justin L 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Justin L 2024-12-27 20:20:31 UTC 
Created attachment 198295 [details]
tdf111341-6.docx_mso.pdf: how it looks in Word 2019

A colourful table-looking AS_CHAR image is lost on page 2.

Steps to reproduce.
1.) Open 111341 TAnf reduced MSO 42-43.docx (attachment 166179 [details]) from bug 111341 comment 16.

This started in LO 7.6 with commit cbdd54e41a78e6a567d7ff97935721b07461cce5
Author: Justin Luth on Wed Apr 5 08:19:11 2023 -0400
    tdf#105035 writerfilter framePr: don't allow overlap in extreme case

It seems to have invoked a layout loop at this point, so not a regression, but just exposing an existing bug.

The layout loop was solved (but the floating image still not seen) with
24.8 commit ae9e8f3f6d10b0be2fe5b9b238a531b17e0d67da
Author: Mike Kaganski on Sun Apr 7 18:23:52 2024 +0500
    tdf#160526, tdf#160549: fix split conditions at page start
Comment 1 Telesto 2024-12-28 08:14:50 UTC 
Confirm
Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 2b68e8bc0303432625a87d6dd60d5e6c3de9be72
CPU threads: 8; OS: macOS 14.7.1; UI render: Skia/Metal; VCL: osx
Locale: nl-NL (nl_NL.UTF-8); UI: en-US
Calc: threaded

Although lost being overstatement in some sense, the image is invisible. It still shows in the navigator