-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
fix(module:dropdown): restore escape and hide backdrop when disabled #3831
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3831 +/- ##
==========================================
+ Coverage 95.36% 95.36% +<.01%
==========================================
Files 723 723
Lines 14722 14724 +2
Branches 1937 1937
==========================================
+ Hits 14040 14042 +2
Misses 249 249
Partials 433 433
Continue to review full report at Codecov.
|
28c3e76
to
fb1513b
Compare
Deploy preview for ng-zorro-master ready! Built with commit e6fcea0 |
fb1513b
to
756bbf8
Compare
756bbf8
to
e6fcea0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM close #3835
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
After PR #3769, I noticed that to exit the dropdown, one must click on the backdrop DOM element.
Being with
nzBackdrop=false
there was no such element, it was not possible to hide the visible dropdown.What is the new behavior?
When
nzBackdrop=false
, the backdrop is present, butopacity
is always set to0
.Also, the
Escape
functionality to hide the dropdown has been restored, as it was lost when the Component has been refactored to a Directive (cdk-connected-overlay
is no more present).Does this PR introduce a breaking change?