Touchscreen lap-tops breaking UI layout.

[diabuddha]

Hello,
We are using Extjs 6.0.1 on a project I am currently working on and In a nested panel using the "fit" layout the inner contents are getting shoved down causing a scrollbar to become necessary, due to the machine loading the page having a touchscreen. This issue does not occur if a touchscreen isn't present. After determining that, we decided to attempt to override Ext.feature.detect() to prevent Extjs from detecting a touchscreen. However this failed in the override folder because the resident Extjs expert believes that the check is done earlier than overrides are applied. We then directly edited the feature.js file with the fix. However this is not getting picked up by Extjs when the project is built. Any ideas on how to fix this issue? Let me know if any other information is needed, I'm not used to posting on forums for assistance.
Thanks.

[Gary Schlosberg]

Do you have a small test case which can be used to recreate this issue?
https://fiddle.sencha.com/#view/editor

[diabuddha]

Not currently, I'll see if I can whip something up. Unfortunately it seems like somewhat of a finicky error.

[diabuddha]

I havent been able to get it to reproduce in the fiddle. Like I said earlier this is a tricky error to reproduce.

[Gary Schlosberg]

Does this occur with newer versions of Ext JS? Any chance you are over-nesting your panels?

[diabuddha]

I do not believe that to be the issue. We have a fix in place that works, but its not getting picked up in the build process. The change is directly to the extjs feature.js file.

[Gary Schlosberg]

Not sure why your build wouldn't be using your change, but I recommend against modifying framework files directly. It is preferable to override the class.

Just to be sure, there's no browser or OS zoom engaged when using the touchscreen laptop, correct?

[geertplaisier]

I do not believe that to be the issue. We have a fix in place that works, but its not getting picked up in the build process. The change is directly to the extjs feature.js file.

We are also having this issue. Would it be possible for you to share the fix you found? Thanks