Fix mobile controls gesture on discussion deletion/restoration #2324
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
askvortsov1
approved these changes
Sep 28, 2020
askvortsov1
requested review from
dsevillamartin,
clarkwinkelmann and
tankerkiller125
dsevillamartin
approved these changes
Sep 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1427
Changes proposed in this pull request:
Because the
Slidableclass was always added on creation, it was lost every time the class list changed (in this case when the discussion was hidden/unhidden which added/removedDiscussionListItem--hiddenclass). So by determining theSlidableclass's presence inelementAttrs()method, it guarantees it always properly set.Reviewers should focus on:
..
Confirmed