This PR will change this, so only the report contained in the response (based on the reportid) will be initialized.
Locally that seems to work fine for me.
Seems the UI tests are passing so far. There are a couple of failures that are unrelated though. All those are already fixed on
4.x-dev. So fixing them here might result in even more merge conflicts when merging
@sgiehl I just tested this with a range and I still had the issue:
I double checked that there was no browser caching.
@tsteur moved some js calculation to simpler css usage. hope that should fix it finally. At least I wasn't able to reproduce in local testing.
@tsteur I actually had a closer look at those tests. The full page of the pivot test looks like this:
So the reason that it looks cut off, is actually that the resolution in tests is too low, to display the full size. Before it was displayed with a fixed width of 1200px, causing the full page to be scrollable, and that way it had enough space to be displayed fully.
The screenshots that still needs to be updated, are located in a submodule. Will do that now, before merging this