Fixed parser issue - AdvancedTag has no attribute 'get' #1
Conversation
This file contains hidden or 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
|
Yes thank you for this catch! I will apply the patch and make a new release. |
|
I've released a new version with the fix (6.5.1), and added a test which calls getElementsByAttr through Parser. Thanks again! |
kata198
added a commit
that referenced
this pull request
May 19, 2017
Fixed parser issue - AdvancedTag has no attribute 'get'
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue
Parsing using
getElementsByAttrfails due to wrong methodgetbeing called during parseFix
Change
gettogetAttribute, as this is what I suspect was intended