Comments (4)
We have some issues in LibSass with regards to sourcemap being different. We have some hacks targeted at making Chrome behaviour. No browser follows the full sourcemaps spec, current implementations are varying degrees of under baked.
Sass spec has a very limited scope. It's job is to assert the semantic equality of output CSS of different engines. Currently we do exact output + some normalisation. This is just because there isn't a good prebuilt library for assert semantic equality of CSS.
This is also the reason we've recently moved output style spec off to the side. The insignificant whitespace in output styles doesn't affect semantic equality.
For this reason I don't think it's reasonable to expect implementations to agree on sourcemaps. IMHO this is out of scope for sass spec in the same way output formats are.
from sass-spec.
We have some issues in LibSass with regards to sourcemap being different.
This should be fixed if sass/sass#2150 and sass/libsass#2193 land.
from sass-spec.
I don't believe that's true. The sourcemaps generated by LibSass are structurally different mapping. I'm still of the opinion this does not belong in sass spec.
from sass-spec.
I agree with @xzyfer. How each implementation handles source maps is up to that implementation, and not something that should be mandated by sass-spec.
from sass-spec.
Related Issues (20)
- Update tests for strict function units
- Update tests for floating-point numbers
- spec linter should allow large HRX files if they are test units HOT 2
- Add specs for color spaces
- Add tests for string.split()
- Add specs for modified color module functions
- Add specs for new global color functions
- Add specs for modified global color functions
- Add specs for new color module functions
- Add tests for calc constants
- Add JS API tests for calculations
- Add tests for nesting in plain CSS
- Add tests forbidding multiple !global or !default flags
- Add tests for additional calculation functions
- Add tests for source order for comments with @use
- Add tests for the containing stylesheet's URL
- Add tests for first-class mixins
- The specs for meta.feature-exists don't actually enforce an interoperable behavior HOT 2
- Add tests for deprecating/removing plain-CSS-like functions and mixins
- Add tests for base importer without URL HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sass-spec.