Bug 113661 - Bottom of the button is cut off on sidebar after switching back from handout view
Summary: Bottom of the button is cut off on sidebar after switching back from handout ...
Status: RESOLVED DUPLICATE of bug 113725
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.0.0.0.alpha1+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: difficultyBeginner, easyHack, skillCpp, topicUI
Depends on:
Blocks:
 
Reported: 2017-11-05 16:43 UTC by Tamás Zolnai
Modified: 2017-11-09 20:37 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Screenshot of the cut off button (106.00 KB, image/png)
2017-11-05 16:44 UTC, Tamás Zolnai 		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 Tamás Zolnai 2017-11-05 16:43:34 UTC 
Description:
On the sidebar we have a Slide pane which there is a Master Slide / Close Master Slide button. Sometimes the button's bottom is cut off.

Steps to Reproduce:
1. Open an empty Impress document (we are in normal view)
2. Switch to handout view (View -> Master Handout)
3. Switch to master slide view (View -> Master Slides)

Actual Results:  
Master Slide / Close Master Slide button is cut off.

Expected Results:
Master Slide / Close Master Slide button should be rendered correctly.


Reproducible: Always


User Profile Reset: No



Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
Comment 1 Tamás Zolnai 2017-11-05 16:44:05 UTC 
Created attachment 137540 [details]
Screenshot of the cut off button
Comment 2 Tamás Zolnai 2017-11-05 16:46:09 UTC 
Let's turn this into an easy hack. The code is here:
sd/source/ui/sidebar/SlideBackground.cxx

SlideBackground::HandleContextChange() method might be a good starting point.
Comment 3 Tamás Zolnai 2017-11-09 20:37:18 UTC 

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