Skip to content

table 筛选变成多个同时展开,正常只能展开一个 #43093

Closed
react-component/trigger
#412

Description

@hihuangwei

Reproduction link

https://ant.design/~demos/components-table-demo-head

微信截图_20230619141150

Steps to reproduce

操作筛选

What is expected?

不同时可展开筛选

What is actually happening?

同时展开多个

Environment Info
antd 5.6.2
React 18.0
System win10
Browser Chrome 100

Activity

  1. afc163 commented on Jun 19, 2023

    @afc163
    Member

    同时展开感觉也不算是问题,会有什么负向体验么?

  2. hihuangwei commented on Jun 19, 2023

    @hihuangwei
    Author

    同时展开感觉也不算是问题,会有什么负向体验么?

    可以加个 api 控制不同时展开,原来是不能同时展开,某个版本开始就是同时展开了

  3. afc163 commented on Jun 20, 2023

    @afc163
    Member

    同时展开感觉也不算是问题,会有什么负向体验么?

    好像没有回答我的问题?

  4. hihuangwei commented on Jun 20, 2023

    @hihuangwei
    Author

    同时展开感觉也不算是问题,会有什么负向体验么?

    好像没有回答我的问题?

    多个同时展开会有重叠问题。多个同时展开并没有实际的作用

  5. linxianxi commented on Jun 20, 2023

    @linxianxi
    Contributor

    打开第二个筛选的时候,第一个筛选没有触发 onOpenChange,去掉下面阻止冒泡就可以。但是又不能去掉,去掉会冒泡引起触发排序。猜测是 rc-trigger 改造的问题 @zombieJ
    image

  6. zombieJ commented on Jun 21, 2023

    @zombieJ
    Member

    打开第二个筛选的时候,第一个筛选没有触发 onOpenChange,去掉下面阻止冒泡就可以。但是又不能去掉,去掉会冒泡引起触发排序。猜测是 rc-trigger 改造的问题 @zombieJ image

    受控调一下就好

  7. NaveenKumarVUK commented on Jul 3, 2023

    @NaveenKumarVUK

    Is it possible to open only one filter expansion at one time?

    If NO, then its normal behaviour or its a bug?

  8. DVSoftware commented on Sep 7, 2023

    @DVSoftware

    This issue still happens to me, i can't figure out why. Upgraded both antd and trigger libraries.

  9. yoyo837 commented on Sep 7, 2023

    @yoyo837
    Contributor

    Could you provide a reproduction link and create a new issue for that?

  10. DVSoftware commented on Sep 7, 2023

    @DVSoftware

    Could you provide a reproduction link and create a new issue for that?

    I would gladly, however, i can't reproduce it on a minimal project. It would help if you could give me some pointers on how to debug this, can't find where this is handled?

  11. DVSoftware commented on Sep 7, 2023

    @DVSoftware

    @yoyo837 When i comment out e.stopPropagation(); as @linxianxi suggested, it works fine, however, i don't see it as a good solution to patch the library this way. I still can't figure out why it works on new project, and not in mine.

  12. DVSoftware commented on Sep 7, 2023

    @DVSoftware

    Removing yarn.lock solved the issue. Apparently there were multiple trigger versions installed in the different dependencies of ant, which caused a discrepancy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions