升级到Chrome 72后是否有人遇到布局问题? [英] Is anyone experiencing layout issues after upgrading to Chrome 72?
问题描述
在我的一些客户升级到Chrome v72之后，他们注意到< = v71中不存在的一些布局问题.根据我的发现，它主要发生在具有溢出元素的情况下:自动或溢出:在使用flexbox定位其子元素的父元素中滚动.
After a few of my customers upgraded to Chrome v72 they've noticed a few layout issues that were not present in <= v71. From what I've found it mostly occurs when having an element with overflow: auto or overflow: scroll within a parent element that is using flexbox to position its children.
还有其他人遇到这种情况吗?请注意，这仅在v72中发生，我已经测试了< 72和其他Webkit浏览器，无法重现.
Is anyone else experiencing this? Note this is only occurring in v72, I've tested < 72 and other webkit browsers and can't reproduce it.
推荐答案
自v72以来，Chrome浏览器渲染的弹性框看上去与溢出不同.这些更改中至少有一部分是有意使Chrome更符合规范和其他浏览器的.
Looks like Chrome renders flex boxes with overflows differently since v72. At least parts of those changes were intentional to make Chrome more compliant to the spec and other browsers.
有关详细信息，请参见此问题: https://bugs.chromium.org/p/chromium/issues/detail ?id = 927066
See this issue for details: https://bugs.chromium.org/p/chromium/issues/detail?id=927066
更新:
我们听到您的声音很清晰，因此决定还原Chrome 72中的更改，以避免破坏现有网站，并让开发人员有更多时间更新其页面.
We've heard you loud and clear and have decided to revert the change in Chrome 72 to avoid breaking existing sites and to allow developers a bit more time to update their pages.
该更改将随Chrome 73一起提供.因此，进行必要的更改对于避免在以后的Chrome版本中破坏它并确保与Firefox兼容仍然很重要.
The change will instead ship with Chrome 73. As such it's still important to make the required changes to avoid breaking it in future versions of Chrome and to ensure compatibility with Firefox.
这篇关于升级到Chrome 72后是否有人遇到布局问题?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
