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.

Sign up for GitHub

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

Jump to bottom

GetLastVisibleChild/NoInit checks wrong node #659

Closed
AlexGraef opened this issue Sep 21, 2016 · 1 comment
Closed

GetLastVisibleChild/NoInit checks wrong node #659

AlexGraef opened this issue Sep 21, 2016 · 1 comment
Assignees
@sanjayssk
Labels
Bug
Milestone
Version 6.4

Comments

@AlexGraef
Copy link

GetLastVisibleChild/NoInit checks the wrong node in IsEffectivelyFiltered. (Should be Result instead of Node)
Same problem as in issue #653
@joachimmarder joachimmarder added this to the Version 6.4 milestone Sep 21, 2016
sanjayssk pushed a commit that referenced this issue Sep 23, 2016
Fixed issue #659: GetLastVisibleChild/NoInit checks wrong node
d8a8048 
Fixed based on the comment given.
@sanjayssk
Copy link
Contributor

Thanks for reporting the problem along with the suggestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sanjayssk sanjayssk

Labels
Bug
Projects
None yet
Milestone
Version 6.4
Development

No branches or pull requests
3 participants
@joachimmarder @sanjayssk @AlexGraef