Block - manually setting to open still fires calciteBlockOpen event #8453
Labels
0 - new
New issues that need assignment.
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.
impact - p2 - want for an upcoming milestone
User set priority impact status of p2 - want for an upcoming milestone
spike
Issues that need quick investigations for time estimations, prioritization, or a quick assessment.
Milestone
Check existing issues
Actual Behavior
Setting a
calcite-block
to open manually (open = true
) still fires thecalciteBlockOpen
event. Note that the deprecated eventcalciteBlockToggle
is not fired in this case.Expected Behavior
Setting
open = true
manually should not fire an open event. Specifically relevant when a block should be open on page load, but no event should occur as a result.Reproduction Sample
https://codepen.io/iyouth66/pen/poYzyjp
Reproduction Steps
1.) Open DevTools
2.) Observe that the
calciteBlockOpen
event is called even when the propertyopen
is set totrue
manually (rather than actually clicking thecalcite-block
element).Reproduction Version
2.0.0
Relevant Info
cc @AdelheidF
Regression?
No response
Priority impact
p3 - want for upcoming milestone
Impact
Specifically relevant when a block should be open on page load, but no event should occur. For example, opening the block by clicking might trigger a focus event, but this event should not be triggered if the block is just set to open on page load (maybe the focus should be elsewhere).
Calcite package
Esri team
ArcGIS Online
The text was updated successfully, but these errors were encountered: