Selecting optimize for printing exports pdf graphs with the X-axis labels moved into the chart

[TinaHeiligers]

Kibana version:
7.7.1
Elasticsearch version:
7.7.1
Server OS version:
macOS
Browser:
Chrome
Version 83.0.4103.116 (Official Build) (64-bit)
Original install method (e.g. download page, yum, from source, etc.):
from source
Describe the bug:
Creating a pdf report of a dashboard using the 'optimize for printing', the x-axis labels on graphs move into the graph panel. The scroll bar also fires its rendered event early.

Steps to reproduce:

1. run kibana version 7.7.1
2. load the eCommerce sample dataset
3. open the dashboard
4. select Share -> PDF Reports -> Optimize for printing -> Generate PDF
5. repeat step 4 without the Optimize for printing option: Share -> PDF Reports -> Generate PDF
6. wait for the reports to generate
7. open the reports and observe that the x-axis label for [eCommerce] Sales by Category has moved into the visualization panel for the optimized for printing report

Expected behavior:
The x-axis should remain below the visualization layer in PDF reports generated when Optimize for printing is selected.

Screenshots (if relevant):
Not optimized for printing:

Optimized for printing:

Errors in browser console (if relevant):
Non
Provide logs and/or server output (if relevant):
No errors or warnings logged

Any additional context:
The reporting team looked into the issue and noticed that the scroll bar seems to be firing its "rendered" event early. I wasn't able to track the early rendering in my local setup.

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[flash1293]

Looked into this further and my first suspicion about this being a timing issue turned out to be wrong. The issue is the position: absolute applied by the print layout logic in the reporting service

This is the chart without styling

This is the same chart with position: absolute:

Even after re-rendering the axes are not placed correctly - seems like something in the layout changed so position: absolute doesn't work anymore.

cc @timroes Would this be a good fit for the visualization roadmap?

[VladLasitsa]

I checked on master and this bug is not reproduced anymore. I think this PR #80744 fixed this issue.