Make EQ work with IE/edge #69
Closed
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
| @@ -187,10 +187,12 @@ | |||
| function extractQuery(css) { | |||
| var match; | |||
| var smatch; | |||
| var ieSelector = '.' + css.split('.')[1].trim(); | |||
There was a problem hiding this comment.
good point. I haven't tested how IE handles ID's.
|
Hey cool, thanks! so comma separated rules are OK in IE/Edge now? |
|
@marcj No they need to be specified individually. But at least it works now. ;) |
juneidy
added a commit
to juneidy/css-element-queries
that referenced
this pull request
Dec 15, 2015
|
Heyho! We've pulled in some code lately which should fix this already. @jacobjuul, can you please confirm that your issue is fixed with current master version? |
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.
IE and Edge parses cssRules with [attributes] differently