-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛S2父级及以上的节点,添加了transform: scale(1.1)后,透视表分组排序按钮失效;(设置supportCSSTransform后依然无效) #2879
Comments
特别备注:原bug提交后给出了修复方案,但该方案尝试无用,因无法reopen issue,故不得已,又开了一个 |
const s2Options = {
width: 600,
height: 480,
showDefaultHeaderActionIcon: true, // 默认打开
supportCSSTransform: true,
+ interaction: {
+ autoResetSheetStyle: false
+ }
}; 由于外层有 transform, 导致判断 "是否点击了表格外区域" 有问题, 感兴趣的话可以来个 PR, 近期有点忙, 可能要晚一点修复 S2/packages/s2-core/src/interaction/event-controller.ts Lines 182 to 187 in 11bb92c
|
配置autoResetSheetStyle: false后确实可以显示下拉框了,但同时因为autoResetSheetStyle: false,所以点击空白区域无法关闭下拉框了,这个还是等修复吧。 |
🎉 This issue has been resolved in version @antv/s2-v1.56.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version @antv/s2-v2.0.0-next.30 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version @antv/s2-react-v2.0.0-next.29 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🏷 Version 1.55.8
Sheet Type
🖋 Description
在S2表格的父级及以上的任意结点,添加transform: scale(1.1)样式后,透视表的分组排序按钮失效;通过调试及源码解读,因是点击位置已经不在S2的原始设定范围内,导致无法正确获取canvas内部点击位置
也曾尝试官网的高清适配方案,但是两种场景并不相同,changSheetSize后仍受控与父级scale css样式影响
特别备注:原bug提交后给出了修复方案,但该方案尝试无用,因无法reopen issue,故不得已,又开了一个
原issue链接:#2849
⌨️ Code Snapshots
使用官网示例:https://s2-v1.antv.antgroup.com/examples/analysis/sort#group-sort
并修改示例项目中的index.html文件,内容更改为:
🔗 Reproduce Link
修改后的codeSandbox连接:https://codesandbox.io/s/silly-gould-v447zf?file=/index.html
🤔 Steps to Reproduce
放大前:
放大后:
😊 Expected Behavior
希望放大后组内排序按钮功能正常;另,我们尝试使用S2 2.x版本,发现存在这样的问题
😅 Current Behavior
父级配置scale放大后,组内排序按钮失效
💻 System information
The text was updated successfully, but these errors were encountered: