Material-ui: Scrollable Tabs not work when user scale display settings to 125%

Created on 29 May 2018  路  6Comments  路  Source: mui-org/material-ui

Problem

I am having some problems with Scrollable Tabs.
Some users change their display settings, scale from 100% to 125%, and when user clicks the next button on Scrollable Tabs, the tabs will go back to original position.

test

My users' environment

Tech Version
Windows 10
Material-UI 1.1.0
Browser Google Chrome 66.0.3359.181
Screen Resolution 1920x1080

Thanks!

bug 馃悰 Tabs good first issue

Most helpful comment

This reproduces on the Material UI demo page, in chrome, with display zoom set to 125%

  • Go to chrome://settings -> Appearance -> Page Zoom -> Set to 125%
  • Navigate to https://material-ui.com/demos/tabs/
  • Scroll down to the "Automatic scroll buttons demo"
  • Click the scroll button on the right.
  • The tabs will scroll right, then back to the original position.
  • You can work around this by first selecting the right-most visible tab, then clicking the scroll button.

I tested these steps on Mac and Linux.

All 6 comments

i am also facing some issues with tab selector which appears below selected tab, when page resizes it's size remains the same even though tab works perfectly, i will try to post example tomorrow here...

Yes, please, can you share a reproduction :)

This reproduces on the Material UI demo page, in chrome, with display zoom set to 125%

  • Go to chrome://settings -> Appearance -> Page Zoom -> Set to 125%
  • Navigate to https://material-ui.com/demos/tabs/
  • Scroll down to the "Automatic scroll buttons demo"
  • Click the scroll button on the right.
  • The tabs will scroll right, then back to the original position.
  • You can work around this by first selecting the right-most visible tab, then clicking the scroll button.

I tested these steps on Mac and Linux.

Thanks for reproduction instructions! @novascreen has found a nice workaround https://github.com/mui-org/material-ui/issues/10826#issuecomment-406889161.

Sorry but continue to happen after updated to 1.4.1...
Its specified that it's included in this version (CHANGELOG.md)

@michael-ecb It wasn't released.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

finaiized picture finaiized  路  3Comments

ryanflorence picture ryanflorence  路  3Comments

activatedgeek picture activatedgeek  路  3Comments

zabojad picture zabojad  路  3Comments

mattmiddlesworth picture mattmiddlesworth  路  3Comments