-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chromium print reports seem to be rendering before the visualisations are complete #22581
Labels
(Deprecated) Feature:Reporting
Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
v7.0.0
Comments
chrisdavies
added
:Sharing
v7.0.0
(Deprecated) Feature:Reporting
Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead
v6.5.0
labels
Aug 31, 2018
chrisdavies
added a commit
to chrisdavies/kibana
that referenced
this issue
Aug 31, 2018
chrisdavies
added a commit
to chrisdavies/kibana
that referenced
this issue
Aug 31, 2018
chrisdavies
added a commit
to chrisdavies/kibana
that referenced
this issue
Aug 31, 2018
waitForRenderComplete function in reporting
chrisdavies
added a commit
to chrisdavies/kibana
that referenced
this issue
Sep 5, 2018
Introduce a delay into reports to allow visualizations time to appear in the DOM. This is intended as a temporary (and hacky) workaround until we come up with a more robust way to determine that all of the visualizations on the page are ready for capture.
chrisdavies
added a commit
that referenced
this issue
Sep 5, 2018
Introduce a delay into reports to allow visualizations time to appear in the DOM. This is intended as a temporary (and hacky) workaround until we come up with a more robust way to determine that all of the visualizations on the page are ready for capture.
timroes
added
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
and removed
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
:Sharing
labels
Sep 13, 2018
Hit here: #23507 (comment) This we may need to extend the timeout. |
@stacey-gammon are we still planning to fix this for 6.5? |
We "fixed" it in a hacky way, but it still needs to be fixed legit style at some point. |
Closing, as it's "fixed" for now. We can re-address it in the future if it surfaces again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
(Deprecated) Feature:Reporting
Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
v7.0.0
The first visualization is blank (sometimes), and the rest are correct. This leads me to believe that Chromium is beginning the report rendering process too early. By the time the first visualization has been captured, the rest have rendered, so they are correctly captured.
Here's an example screenshot:
The text was updated successfully, but these errors were encountered: