Bug 86602 - Float Frame should require real filename in Content
Summary: Float Frame should require real filename in Content
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.4.0.0.beta1
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Frame
  Show dependency treegraph
 
Reported: 2014-11-23 02:44 UTC by Maxim Britov
Modified: 2023-09-10 03:20 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maxim Britov 2014-11-23 02:44:24 UTC
From https://help.libreoffice.org/Common/Floating_Frame_Properties#Contents
Contents should contains filename.

Try Insert - Float Frame with Contents "qqqq" and you will have potentially problem documents. Yes, it say file not exit. Yes, visually it looks like frame not inserted.

Good example (work for me on linux):
Create new Draw document
Insert shape, for example oval.
Insert - Float Frame: Name= "1111" Contents="2222", - press Ok
1. I seen here gree dots around empty object-frame.
2. When I scroll down, scroll up I see garbage.
Comment 1 Buovjaga 2014-12-16 15:18:53 UTC
Reproduced everything described.

Ubuntu 14.10 64-bit Version: 4.5.0.0.alpha0+
Build ID: f92183833fa569006602ac7e93c906d2094e0d4d
TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2014-12-14_00:21:45
Comment 2 QA Administrators 2016-01-17 20:01:40 UTC Comment hidden (obsolete)
Comment 3 Maxim Britov 2016-01-29 12:10:29 UTC
I can reproduce this on 5.0.5.1 and 5.1.0.1
Comment 4 QA Administrators 2017-03-06 13:41:02 UTC Comment hidden (obsolete)
Comment 5 Thomas Lendo 2019-09-09 19:07:44 UTC
Still reproducible.
Version: 6.4.0.0.alpha0+
Build ID: 4e527f55d74e3220873075a8ec2799e2206fdb2d
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-08-31_02:35:57
Comment 6 QA Administrators 2021-09-09 03:41:35 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2023-09-10 03:20:33 UTC
Dear Maxim Britov,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug