On optimize for printing pdf reporting - data points are not printing for coordinate maps when they are on dashboards

[bhavyarm]

Kibana version: 6.7.0 BC3

Elasticsearch version: 6.7.0 BC3

Server OS version: darwin_x_86_64

Browser version: chrome latest

Browser OS version: OS X

Original install method (e.g. download page, yum, from source, etc.): from staging

Describe the bug: If user adds a co-ordinate map to dashboard and picks the option of pdf reporting with Optimize for printing - datapoints are not getting printed.
Please note this is fine on visualize app.

Steps to reproduce:

1. add a coordinate map to dashboard
2. save the dashboard click on share and pick pdf and toggle optimize for printing and click print
3. The resulting pdf is empty of data points

tile_map.pdf

[elasticmachine]

Pinging @elastic/kibana-gis

[elasticmachine]

Pinging @elastic/kibana-app

[thomasneirynck]

I can reproduce this. The difference seems to be between optimizing for print layout (buggy) and keeping the regular webpage layout.

• dashboard page layout (ok): dashboard_webpagelayout.pdf
• dashboard print layout (bug): printlayout.pdf

The issue seems to only occur on dashboards, and not on single visualizations

• vis page layout (ok): vis_webpagelayout.pdf
• vis print layout (ok):vis_printlayout.pdf

[joelgriffith]

I'm taking a look now, might be a bit before I can unravel this though!

[joelgriffith]

I'm seeing this behavior back until 6.5.4. I'm not sure what the cause is yet, or when it became an issue, but still digging.

[joelgriffith]

@thomasneirynck @bhavyarm I can reproduce this on versions 6.5.4 and 6.6.1. I'm not sure if it's appropriate to label this as a regression since it seems to be present prior to 6.7.0. Definitely needs fixing, but not sure if we should block release based upon it.

[tsullivan]

I can also repro on 6.6.1.

++ for removing regression label

[thomasneirynck]

+1 on removing regression label

[joelgriffith]

I've found where the regression is, putting together a PR

[joelgriffith]

Fixed in #31949

[joelgriffith]

This is now in master, 6.7 and 7.0 branches!

[marius-dr]

@joelgriffith this showed up again in 7.2.0
[Flights] Global Flight Dashboard map test.pdf

Easiest way to reproduce is to use the Flights sample data dashboard and generate a report with "Optimize" enabled.

[tsullivan]

@marius-dr I tried your steps in 7.2.1 and I see it too:

[elasticmachine]

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

[nreese]

fixed by #55137