
test site: https://tgreen7.github.io/blueprint-popover/
test repo: https://github.com/tgreen7/blueprint-popover
This is expected, since the popover is outside the dialog, and outside clicks are allowed to close the dialog. You can get around this by disabling canOutsideClickClose on the Dialog or making the Popover usePortal={false}.
@adidahiya this has only started happening in v2 of blueprint though. Was this change in behavior expected?
@tnrich i'm not sure that's true--fairly sure this would happen in 1.0 too. we haven't touched the logic that closes on outside click.
@giladgray here is a test in 1.0 https://tgreen7.github.io/blueprint-popover-v1/
it seems to be working fine there. (repo https://github.com/tgreen7/blueprint-popover-v1)
(incorrect close, wrong issue number in PR)
other related issues exist