If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Scrollbar missing on report

Started by hespora, 23 May 2017 03:10:24 AM

Previous topic - Next topic

hespora

Hi there,

(sorry for choosing the wrong board; I couldn't find a better one)

weird issue: We have a report with fixed sizes that, when run on laptops with low resolution, is both taller and wider than the browser's display area. Here the fun starts: On *some* machines (not all), only the vertical scroll bar renders is visible, not the horizontal one. (Still using the touchpad for horizontal scrolling does work, but I have some consumers out there that do not know how to do that. Don't ask...)

Browser where it's happening on some machines is IE11. Tried chrome, works fine. Anybody seen this and have an idea what IE setting this might be?

AnalyticsWithJay

If there's a horizontal scroll bar that means there's an overflow of the specified width for the given resolution. There's no browser setting for this.

As a test, you can place the objects inside a block, specify a small width for the block that you know won't cause overflow (200px for example), and set the overflow property to 'content is clipped'. The scroll bar should disappear.

hespora

No, I *know* thee's overflow to the right hand side. Using two fingers on touch pad, or using middle mouse button, I can scroll to the right and see the owerflowing content.

The issue is that one machine is rendering a horizontal scroll bar, while the other is not. Yet they both have horizontal overflow.


AnalyticsWithJay

Oh, I misunderstood -- you want the horizontal scroll bar to appear.

I know you said both IE 11 - but are they the exact version down to the build number? 11.x.xxxx

If you place all the objects in a block and leave the block settings to default, is it the same behavior? I'm wondering if there's a difference in how the browser is interpreting the DOM.

I would also try to replicate this behavior in a very simple, blank report, maybe with 1 list to rule out any report specific issues that are causing browser rendering issues.