107748 – When resizing window after inserting chart and remaining in the chart mode, there are UI glitches

Bug 107748 - When resizing window after inserting chart and remaining in the chart mode, there are UI glitches

Summary: When resizing window after inserting chart and remaining in the chart mode, t...

Status:	RESOLVED DUPLICATE of bug 94322

Alias:	None

Product:	LibreOffice
Classification:	Unclassified
Component:	UI (show other bugs)
Version: (earliest affected)	5.3.3.2 release
Hardware:	All All

Importance:	medium minor
Assignee:	Not Assigned

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2017-05-10 08:55 UTC by ccsheller
Modified:	2022-06-16 05:41 UTC (History)
CC List:	3 users (show)

See Also:
Crash report or crash signature:

Attachments
insert a chart (27.34 KB, image/png) 2017-05-10 08:55 UTC, ccsheller	Details
resize the main window (27.34 KB, image/png) 2017-05-10 08:56 UTC, ccsheller	Details
insert a chart (32.28 KB, image/png) 2017-05-10 08:58 UTC, ccsheller	Details
Show Obsolete (1) 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 ccsheller 2017-05-10 08:55:08 UTC

Created attachment 133210 [details]
insert a chart

1.create new calc
2.insert a chart(see attachment 1)
3.resize the main window(see attachment 2)
the main window is not arrange children window

Comment 1 ccsheller 2017-05-10 08:56:02 UTC

Created attachment 133211 [details]
resize the main window

Comment 2 ccsheller 2017-05-10 08:58:12 UTC

Created attachment 133212 [details]
insert a chart

Comment 3 m_a_riosv 2017-05-11 00:18:23 UTC

Sorry, but why it should be?, chart size it's not dependent of the LibreOffice's window size.

Comment 4 ccsheller 2017-05-11 02:08:32 UTC

but this is a ui error.

Comment 5 m_a_riosv 2017-05-11 08:28:24 UTC

Please can you detail, why?

Comment 6 Buovjaga 2017-06-14 07:17:36 UTC

The point is that the sidebar elements glitch out badly. See the screenshots and try to reproduce yourself. I confirm.

Win 7 Pro 64-bit, Version: 5.3.1.2 (x64)
Build ID: e80a0e0fd1875e1696614d24c32df0f95f03deb2
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Layout Engine: new; 
Locale: fi-FI (fi_FI); Calc: CL

Version: 6.0.0.0.alpha0+ (x64)
Build ID: a1ace08b5b86a76e7275dcef2545a7d52ae2ed2d
CPU threads: 4; OS: Windows 6.1; UI render: default; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2017-06-13_03:04:47
Locale: fi-FI (fi_FI); Calc: CL

Comment 7 QA Administrators 2018-06-15 02:45:50 UTC Comment hidden (obsolete)

** Please read this message in its entirety before responding **

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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

Comment 8 QA Administrators 2020-06-15 03:40:00 UTC Comment hidden (obsolete)

Dear ccsheller,

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.

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

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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

Comment 9 QA Administrators 2022-06-16 03:44:17 UTC Comment hidden (obsolete)

Dear ccsheller,

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.

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

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

Comment 10 Aron Budea 2022-06-16 05:41:35 UTC

Let's mark this as dupe of bug 94322.

*** This bug has been marked as a duplicate of bug 94322 ***