Skip to main content

My team works with tableau to create "single page" views that vary in size. Becasue of this, we use the range selection for dashboard sizes where we "lock" the vertical range to the desired amount by setting the min and max to the same value, anywhere from 1200 to 3600 pixels. And let the horizontal view range from 800 to 2600 pixels to ensure a mobile view and desktop view share the same data are accessible. Our site currently uses the same sized embedding element as it would be difficult to manually load in the fixed sized dimensions for all our dashboards to the html beforehand.

 

We have been on version 2 of the embedding API and are currently testing out version 3. This issue is that in version 2, if a dashboard overflowed vertically out of the default container size, it would overflow without creating scroll bars in the viz itself which was fine and our html and css could handle that.

 

In version 3, it does not overflow but generates scroll bars. This behavior would be fine except that if a vertial scroll is created, a horizontal scroll bar is created to accommodate the minimal space taken up by the vertical scroll bar created.

 

Possible solutions:

  • Allow horizontal resizing in the event a vertical scroll appears to prevent the unecessary horizontal scroll if possible
  • Allow overflow in the new embedding api as an attribute in the <tableau-viz> HTML object (in version 2 there was a scroll='hidden' attribute)
1 answer
  1. Mar 27, 2025, 10:22 PM

    Hi David,

     

    800 is a bit of a magic number in Tableau because this is the breakpoint for PC and Tablet rather than PC and mobile. Its probable that you haven't catered for gutters in either your iframe or in your embed which can be anything around 10-15 pixels.

     

    You can either shorten your viz by this amount, or jump into the code base to figure out where the misalignment is happening, but I'm assuming that you are so close to the mark that its just frustrating at this point.

     

    For safety, we just built 20 pixels under the iframe size because we had the capacity to do this but you might need those pixels.

     

    HTH

     

    Peter

0/9000