Skip to content
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

[Modal] calciteModalClose should not fire when open prop is toggled to false #7724

Open
2 of 3 tasks
rpanichakit9541 opened this issue Sep 11, 2023 · 3 comments
Open
2 of 3 tasks
Assignees
Labels
1 - assigned Issues that are assigned to a sprint and a team member. ArcGIS Online Issues logged by ArcGIS Online team members. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. calcite-components Issues specific to the @esri/calcite-components package. docs Issues relating to documentation updates only. estimate - 5 A few days of work, definitely requires updates to tests. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive low risk Issues with low risk for consideration in low risk milestones p - low Issue is non core or affecting less that 10% of people using the library

Comments

@rpanichakit9541
Copy link
Contributor

Check existing issues

Actual Behavior

Currently, calciteModalClose event fires both when "X" is clicked or if the open prop is toggled to false.

Expected Behavior

I asked @driskull and he said it should only fire on "X" click and not when open is toggled to false.

Reproduction Sample

https://codepen.io/rpanichakit/pen/qBLmRRN?editors=1001

Reproduction Steps

  1. Open modal
  2. click "Cancel"
  3. observe "close event" output to the console

Reproduction Version

1.8.0

Relevant Info

No response

Regression?

No response

Priority impact

p4 - not time sensitive

Impact

No response

Calcite package

  • @esri/calcite-components
  • @esri/calcite-components-react

Esri team

ArcGIS Online

@rpanichakit9541 rpanichakit9541 added 0 - new New issues that need assignment. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. needs triage Planning workflow - pending design/dev review. labels Sep 11, 2023
@github-actions github-actions bot added ArcGIS Online Issues logged by ArcGIS Online team members. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive calcite-components Issues specific to the @esri/calcite-components package. labels Sep 11, 2023
@geospatialem geospatialem added docs Issues relating to documentation updates only. 1 - assigned Issues that are assigned to a sprint and a team member. and removed 0 - new New issues that need assignment. labels Sep 18, 2023
@geospatialem geospatialem self-assigned this Sep 18, 2023
@geospatialem geospatialem added estimate - 2 Small fix or update, may require updates to tests. p - medium Issue is non core or affecting less that 60% of people using the library and removed needs triage Planning workflow - pending design/dev review. labels Sep 18, 2023
@geospatialem
Copy link
Member

Add a doc example where user events can be tracked (via keyboard/click) vs. if toggled via an attribute/prop.

@brittneytewks brittneytewks added the low risk Issues with low risk for consideration in low risk milestones label Sep 21, 2023
@geospatialem
Copy link
Member

Re-assigning the documentation update to the January 2024, in alignment and in consideration with the efforts of #3818, where we can explore a new documentation page that contains information on open and additional patterns such as validation, animation, and references mentioned in #3818 (comment).

In the meantime, this is the expected pattern with regards to the open and close events, which are asynchronous as a result of animations. Calcite emits both when setting the property, or when the user closes/opens the component.

The pattern will also be addressed via PR #7613 and issue #4398.

@geospatialem geospatialem added the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Jan 10, 2025
@geospatialem geospatialem removed their assignment Jan 10, 2025
@geospatialem geospatialem added 0 - new New issues that need assignment. and removed 1 - assigned Issues that are assigned to a sprint and a team member. labels Jan 10, 2025
@geospatialem geospatialem added p - low Issue is non core or affecting less that 10% of people using the library and removed p - medium Issue is non core or affecting less that 60% of people using the library labels Jan 10, 2025
@geospatialem
Copy link
Member

Re-assigning the documentation update to the January 2024, in alignment and in consideration with the efforts of #3818, where we can explore a new documentation page that contains information on open and additional patterns such as validation, animation, and references mentioned in #3818 (comment).

In the meantime, this is the expected pattern with regards to the open and close events, which are asynchronous as a result of animations. Calcite emits both when setting the property, or when the user closes/opens the component.

The pattern will also be addressed via PR #7613 and issue #4398.

We should reconsider the doc update for 2025 timings, as the above has changed in scope. Updated the doc update priority to p - low to address in the future.

@DitwanP DitwanP removed the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Jan 13, 2025
@DitwanP DitwanP self-assigned this Jan 13, 2025
@DitwanP DitwanP added 1 - assigned Issues that are assigned to a sprint and a team member. and removed 0 - new New issues that need assignment. labels Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - assigned Issues that are assigned to a sprint and a team member. ArcGIS Online Issues logged by ArcGIS Online team members. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. calcite-components Issues specific to the @esri/calcite-components package. docs Issues relating to documentation updates only. estimate - 5 A few days of work, definitely requires updates to tests. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive low risk Issues with low risk for consideration in low risk milestones p - low Issue is non core or affecting less that 10% of people using the library
Projects
None yet
Development

No branches or pull requests

4 participants