-
Notifications
You must be signed in to change notification settings - Fork 463
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
@at-root regression with nested mixin #2198
Comments
xzyfer
added a commit
to xzyfer/sass-spec
that referenced
this issue
Oct 1, 2016
This PR add specs for sass/libsass#2198
Looks like the regression was caused by a new feature in #2089. Hopefully this means it should be a straight forward fix. |
This was referenced Oct 1, 2016
Closed
xzyfer
added a commit
to xzyfer/sass-spec
that referenced
this issue
Oct 3, 2016
This PR activates specs for sass/libsass#2198
This was referenced Oct 3, 2016
xzyfer
added a commit
to xzyfer/libsass
that referenced
this issue
Oct 4, 2016
LibSass fully parses selectors during the parsing stage. This is different from Ruby Sass which parse selectors and string during the parsing stage, and lazily eval'ing when required. This difference causes some pathological selector issues. Our eager parsing of selectors has resulted in us hacking in fake `Parent_Selector` into `Sequence_Selector` during parsing. These fake `Parent_Selector` play havoc with `resolve_parent_refs` when within `@at-root` blocks. I spent a couple weeks going down the rabbit whole of refactoring our selector parsing to be lazy before bailing. Explicitly marking which `Parent_Selector` are fake during parsing allows us faithfully implement the `implicit_parent` flag in `resolve_parent_refs`. Fixes sass#2006 Fixes sass#2198 Spec sass/sass-spec#936
xzyfer
added a commit
to xzyfer/libsass
that referenced
this issue
Oct 4, 2016
LibSass fully parses selectors during the parsing stage. This is different from Ruby Sass which parse selectors and string during the parsing stage, and lazily eval'ing when required. This difference causes some pathological selector issues. Our eager parsing of selectors has resulted in us hacking in fake `Parent_Selector` into `Sequence_Selector` during parsing. These fake `Parent_Selector` play havoc with `resolve_parent_refs` when within `@at-root` blocks. I spent a couple weeks going down the rabbit whole of refactoring our selector parsing to be lazy before bailing. Explicitly marking which `Parent_Selector` are fake during parsing allows us faithfully implement the `implicit_parent` flag in `resolve_parent_refs`. Fixes sass#2006 Fixes sass#2198 Spec sass/sass-spec#936
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Testing against latest libsass/master, we encountered an odd issue when a selector is generated by a mixin nested within an
@at-root
directive. Possibly related to #2187test case:
expected (ruby Sass 3.4, libsass 3.3.6):
actual (libsass/master (3.4rc)):
Spec added sass/sass-spec#935
The text was updated successfully, but these errors were encountered: