Scroll problem only in chrome

Tags: #<Tag:0x00007efc6565dea8>
#1

Hi, I’m trying to set up a big handsome table but when I try to scroll horizontally and vertically it makes a weird behaviour (the last horizontal columns disappear and the fixed header and fixed 1st column doesn’t scroll…), it only happens on chrome and inside our app, so we can’t show you any example, just a animated gif of what’s happening, can you help here?

handsone-scroll.gif769×398 58.6 KB

#2

Hi @dit

It sounds like a styling bug. If you are using any additional styling (own .css file or a framework) please comment all those and check if it still occur.

#3

Hi, thanks for the fast response, I’ve removed all our styles (css) and Js and it still happens, were using Kendo UI framework and bootstrap, is there any incompatibility with those frameworks?

#4

They should be compatible but if something is missing its position it’s the first thing to check.

Could you create a demo where this issue can be replicable?

#5

because this problem is only happening in chrome, and inside our app (firefox and IE edge are ok) the only way we can show you the problem is by remote view with team viewer or other, is it possible for you?

#6

If it is not replicable my a JSFiddle it has to be something outside the Handsontable and I can’t help you with that.

I can recommend:

  1. checking if there’s nothing printed in the console
  2. adding display: scroll to Handsontable’s parent container
  3. adding stretchH: 'all' and height/width settings
  4. playing with FF developer tools
#7

Are you sure about the display: scroll? shouldn’t be overflow: scroll? and we’re trying all of your recommendations and more, and it still doesn’t work…

#8

Yup, you’re right, my bad - the overflow.
If you could create a demo it’ll be easier to advice.

#9

The problem with the demo is the behaviour only happens on chrome and inside our app… we will try to solve it by ourselves and if it still happens we will make a demo, with all our styles, js and frameworks, thanks for the help.

#10

Hi @dit
How is your progress in this matter?

#11

So far we have solved the problem it had to do with style and js libraries that were not called in the main view or Index. they were being called in the partial view. thanks for the help

#12

Thanks for keeping my updated @dit

ps. one of our devs is working on a new styling structure (Roadmap) I think you would like to know that.
You can also leave a comment there if you have some ideas or investigation results after the above case.

#13
#14