Re: [csswg-drafts] Source maps for CSS (#13098)

The CSS Working Group just discussed `lunch`.

<details><summary>The full IRC log of that discussion</summary>
&lt;astearns> topic: lunch<br>
&lt;ydaniv> scribe+<br>
&lt;Euclid> +present<br>
&lt;ydaniv> nicolo-ribaudo: source maps, does anyone here know what it is?<br>
&lt;kbabbitt> github: https://github.com/w3c/csswg-drafts/issues/13098<br>
&lt;ydaniv> ... recap, mostly for JS but also now for HTML<br>
&lt;ydaniv> ... you write some code and then go through build tools<br>
&lt;ydaniv> ... more and more the code you write is now what ends up in the browser<br>
&lt;ydaniv> ... source maps have been around for some time now<br>
&lt;ydaniv> ... they are instructions for build tools<br>
&lt;kbabbitt> s/write is now what/write is not what/<br>
&lt;ydaniv> ... to make sure the code in browser looks like what you wrote in editor<br>
&lt;ydaniv> ... there's partial description in a google doc of what it does<br>
&lt;ydaniv> ...  in ECMA we started defining it, and talking with browser dev teams<br>
&lt;ydaniv> ... where is it still problematic<br>
&lt;ydaniv> ... evolving the idea<br>
&lt;ydaniv> ... maybe you're using SASS or others and they do create source maps<br>
&lt;ydaniv> ... we should also try to focus on what can be done in CSS<br>
&lt;ydaniv> ... is ti just for build tools?<br>
&lt;ydaniv> ... what can we do more for CSS? ...<br>
&lt;ydaniv> ... one is nesting, that may be transpiled<br>
&lt;ydaniv> ... there are other bunch of build tools features that transpile<br>
&lt;ydaniv> ... I'm preseting this here because I think this transpiling may be confusing for authors<br>
&lt;astearns> the namespacing we just talked about might also be a use case<br>
&lt;ydaniv> ... could be great if we could work this out together<br>
&lt;ydaniv> ... find if we have dev experience issues<br>
&lt;kizu> q+<br>
&lt;astearns> ack kizu<br>
&lt;ydaniv> ... if ppl have opinions<br>
&lt;ydaniv> kizu: would be great to have<br>
&lt;ydaniv> ...  a lot of it is not actually CSS, like comments etc.<br>
&lt;ydaniv> ... the source for things in CSS may not be just CSS itself, may come from JSON or JS<br>
&lt;ydaniv> ... [examples]<br>
&lt;ydaniv> ... also may come from [missed]<br>
&lt;ydaniv> nicolo-ribaudo: it's something you can do with source maps ideally<br>
&lt;ydaniv> TabAtkins: you mentioned some features, like nesting<br>
&lt;ydaniv> ... it's not only transpiling things that can't be, it may be also things from JS,<br>
&lt;miriam> q+<br>
&lt;ydaniv> ... also there's a lot of source transforms that can't be done<br>
&lt;ydaniv> nicolo-ribaudo: to be clear, there's no one with CSS experience<br>
&lt;ydaniv> ... so happy to see others for helping out<br>
&lt;astearns> ack miriam<br>
&lt;ydaniv> miriam: because transpiling is in external tools, would be nice to reach out for those tool makers<br>
&lt;ydaniv> kizu: tailwind is intreresting, the source is in CSS but tranforms to HTML<br>
&lt;ydaniv> nicolo-ribaudo: if you want to see the slides we have contact info there<br>
&lt;ydaniv> ... thanks!<br>
&lt;emilio> q+<br>
&lt;astearns> ack emilio<br>
&lt;ydaniv> emilio: you have comment syntax there, is that what would be strandardised?<br>
&lt;ydaniv> nicolo-ribaudo: yes<br>
&lt;ydaniv> ... there are ppl from FF dev tools on there<br>
&lt;ydaniv> astearns: thank you, moving on<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13098#issuecomment-3530868620 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 14 November 2025 05:15:36 UTC