521976 – Arrange All result is different following the zoom and the scroll bar parameters

Bug 521976 - Arrange All result is different following the zoom and the scroll bar parameters

Summary: Arrange All result is different following the zoom and the scroll bar parameters

Status:	NEW

Alias:	None

Product:	Sirius
Classification:	Modeling
Component:	Diagram (show other bugs)
Version:	5.0.0
Hardware:	PC All

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Project Inbox
QA Contact:

URL:
Whiteboard:
Keywords:	triaged

Depends on:
Blocks:

Reported:	2017-09-07 04:08 EDT by Florian Barbin
Modified:	2017-10-17 09:10 EDT (History)
CC List:	1 user (show)

See Also:	520633

Attachments
Use case to reproduce this issue (80.40 KB, application/zip) 2017-09-07 04:08 EDT, Florian Barbin	no flags	Details
Result with 200% (30.96 KB, image/png) 2017-09-07 04:09 EDT, Florian Barbin	no flags	Details
Result with 100% (30.70 KB, image/png) 2017-09-07 04:09 EDT, Florian Barbin	no flags	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 Florian Barbin

2017-09-07 04:08:01 EDT

Created attachment 270103 [details]
Use case to reproduce this issue

Open the "new TestReconnect" diagram.
Make sure the snap to shap and shap to grid are deactivated.
Make sure the zoom is 100% and there is no scroll bar.
Perform the arrange all. Take a screenshot of the result.
Revert the arrange all.
Set the zoom at 200% and locate the vertical scroll bar in the middle.
Perform the arrange all.
Set the zoom at 100% and take a screenshot.
If you compare with the previous screenshot, the result is different. KO

Comment 1 Florian Barbin

2017-09-07 04:09:00 EDT

Created attachment 270104 [details]
Result with 200%

Comment 2 Florian Barbin

2017-09-07 04:09:19 EDT

Created attachment 270105 [details]
Result with 100%

Comment 3 Maxime Porhel

2017-10-17 09:10:06 EDT

Hi Florian, 

Thanks for your detailed bug report.
We have reproduced this issue and we reckon it is valid. 
Nevertheless, it's not yet in the scope of a future release.

Regards