Forum Discussion
Embedded report datagrid row heights load with zero height
Figured it out for those seeing the same issue. The browser difference is just DOM render speed. I'm using an MV* JS framework (aurelia) and using a show/hide binding that hides the DIV container that contains the iframe. When the embedReport() method runs, I'm using on('rendered') event handler to show the div container with the iframe so we dont see the PBI loader since our site will be more than just PBI and isn't consistant with our styling. So I just changed the show/hide functionality (which is using display:none) to opacity:0 for hide and opacity:1 to show and we're back in business. I'm assuming this is because the iframe contents need a visible element to render properly to the available dimentions which don't really exist when display:none is set.
I decided to test it again and the datagrids do render properly on first load on Safari but not in Chrome or FF (we aren't setup for IE or Edge as we haven't added the JS polyfills). Any reason why embeded angular UI would do this for embed only in Chrome/FF and not Safari??
This is what we have set for the iframe with no additional config in the JS embedReport() method.
<iframe src="_URL_" scrolling="no" allowfullscreen="true" style="width: 100%; height: 100%;"></iframe>
Figured it out for those seeing the same issue. The browser difference is just DOM render speed. I'm using an MV* JS framework (aurelia) and using a show/hide binding that hides the DIV container that contains the iframe. When the embedReport() method runs, I'm using on('rendered') event handler to show the div container with the iframe so we dont see the PBI loader since our site will be more than just PBI and isn't consistant with our styling. So I just changed the show/hide functionality (which is using display:none) to opacity:0 for hide and opacity:1 to show and we're back in business. I'm assuming this is because the iframe contents need a visible element to render properly to the available dimentions which don't really exist when display:none is set.
That's quite an obscure bug to find, but makes sense from the DOM layout perspective.
I would have thought that it would have caused more issues than just the data tables though.
Nice one!