@jimniels same here! I've replaced the #sass syntax with nested #CSS and while it worked on all major browsers (latest version), everything was broken when using an older #ipad
It looks like a serious issue. I didn't notice it but a double slash (//) in #Sass is used to include inline comments so using it as a value is not easy to parse 👀
The comma inside the var() is not a typo but an important feature. The below is only a minimal example to reproduce the issue but in my case it's more complex.
It seems to me that #communism and libertarianism (is this right?) have the same fundamental flaw: requiring non-greedy humans.
And when they fail, the proponents have the same excuse: "That wasn't REALLY C/L, next time it's going to work!"
And I'm sure some libertarian friends will try to opine that libertarianism is more complex than I give it credit, but until a convincing argument is made, I will continue to posit that Libertarianism is a political ideology not so much penned, but crayoned.
Extremely unimpressed with the ways in which Sass integrations seem like a complete afterthought in 2024. Sass is a beautiful, powerful language, made and maintained by smart, caring people. It’s really sad to see it done dirty like this. #Sass#SCSS#WebDevelopment
I’m the CEO of the Self Actualisation Support Society, a Canadian nonprofit organization dedicated to helping ensure accessible resources for the #trans community and setting up for more active advocacy.
Post >> Variations on styling variables in SSGs • The CSS-or-Sass question about styling variables is a lot simpler to answer when you’re building your site the right way.
With Drupal 9 EoL and Drupal 10+ no longer supporting IE, what are the chances we can get Olivero to drop PostCSS and return to SASS for CSS compiling?
Yeah, I know, I was away for a while and some things broke. In apology, take this: breaks fixes, and some improvements! No really, these might actually be useful to anyone reading this, and not just me. Well, some of them.
If you’re not aware, I use a modified fork of the Bilberry theme for Hugo (it’s on the “site-local” branch). Recently, major version 4 was released, which is effectively a separate theme in the v4 subdirectory, which changes a few fundamental parts. For example…
#PSA: if you've been using a custom rem() function in #SASS to convert px to rem, version 1.65 is likely to break your code, as it introduces the official #CSSrem() function, which returns the remainder of a division.
There are issues open about this, but it seems intended behaviour and the official solution seems to be to rename the custom function to something like toRem, which yes, is sadly more annoying to type... 😅
i'm updating a #drupal 8 site to 10 and tumbling through some of the changes in #css#scss#sass class conventions, maybe due to the outdated #radix theme? where underscores are now hyphens and various <div> have appeared and disappeared 😬
is there a standard/programmatic way to update the classes at least? 🤔
Hey every single #sass company out there. I don’t want to call you for pricing. I don’t want to hop on a conference call where we discuss my usage of the product and you tell me about all the other products you sell that integrate with this product.
I especially don’t want to reach out to you for pricing, wait a week for a response to my email, which is then an invitation to hop on a call the next week. My primary job is not buying software. It is to write and deliver features for internal or external customers. I don’t have 3+ weeks to fuck around with these stupid meetings.
I had budget for a product this week and ended up using an OSS that I didn’t want to use because I could not deal with talking to their sales team again. They made me “write custom C code to add the one feature I wanted” mad. Now I’ll never use you out of spite.