Bug 102519 - [EDITING][FORMATTING][TABLE][REGRESSION] Broken object positioning and selection
Summary: [EDITING][FORMATTING][TABLE][REGRESSION] Broken object positioning and selection
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:odt, regression
Depends on:
Blocks:
 
Reported: 2016-09-26 13:20 UTC by Nicolas Mailhot
Modified: 2017-05-31 10:46 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Testcase (21.71 KB, application/vnd.oasis.opendocument.text)
2016-09-26 13:21 UTC, Nicolas Mailhot
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Mailhot 2016-09-26 13:20:38 UTC
User-Agent:       Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:49.0) Gecko/20100101 Firefox/49.0
Build Identifier: 

The format of the attached testcase broke in latest libreoffice versions (5.2 windows x86_64):

1. The first table sometimes moves to the second page even though there is enough empty space for it (and the next one) on the fist page. The document is not 3 pages, it was two in previous LO versions

2. The blue "+" text frame is supposed to have table text flowing around it, but it is not happening anymore

3. writer refuses the select the text shape (upper right corner) to change its text. Writer tries to select the blue frame instead

Reproducible: Always







Reset User Profile?No
Comment 1 Nicolas Mailhot 2016-09-26 13:21:21 UTC
Created attachment 127642 [details]
Testcase
Comment 2 Xisco Faulí 2016-10-08 15:16:01 UTC
Hi Nicolas,

Thanks for your report but I can't reproduce it in master:

Version: 5.3.0.0.alpha0+
Build ID: ae3ec79354f7b4967e736c6a4cd7c08fc52e2b7d
CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

Could you please try to reproduce it in master -> http://dev-builds.libreoffice.org/daily/master/

On the other hand, please try to report each issue in a different bug so it's easier for us to triage the bugs.

Regards
Comment 3 Nicolas Mailhot 2016-10-10 12:51:35 UTC
(In reply to Xisco Faulí from comment #2)

> Could you please try to reproduce it in master ->
> http://dev-builds.libreoffice.org/daily/master/

I don't see any windows x86_64 build there

> On the other hand, please try to report each issue in a different bug so
> it's easier for us to triage the bugs.

That's really hard to do when the testcase is partly un-editable in writer :(
Comment 4 Xisco Faulí 2016-10-10 13:18:39 UTC Comment hidden (obsolete)
Comment 5 Xisco Faulí 2016-10-10 13:21:31 UTC
Please don't change the status to NEEDINFO unless someone else confirms this bug.
You can use http://dev-builds.libreoffice.org/daily/master/Win-x86@42/current/
Comment 6 QA Administrators 2017-05-02 11:37:22 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2017-05-31 10:46:58 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20170531