From a site I've inherited which is full of things like this (and lots of other very !important things). Send help.
That's why css names should be semantic. I'm sure it started actually purple until UX said "can we make this primary text more blue so it doesn't look like a clicked link?" Replacing all references to "purple" wasn't an option because of unrelated usage of that word elsewhere and they weren't using an IDE capable of contextual rename of a css class. So they just changed the color code and called it a day.
sed -i 's/.purple/.not-purple/g' *.css
done, boss
This just gave me a panic attack
It's fine as long as you have proper source control. Run it and check the diff before committing.
But I set my .git directories to have .css filename extensions!!?! It shouldn’t be my job to educate you.
Gotta do it on the HTML files and JS files too. Then you gotta re-test every page that uses those files.
Then the boss looks over your code and asks why you didn’t just change the actual color because that’s easier to QC.
Yeah, but if you just used css variables, this would’ve been a doddle. One and done.
I’m sorry but the solution to every argument is not just to throw of the word “semantic” in the sentence. Context is everything.
I’m sorry but the solution to every argument is not just to throw of the word “semantic” in the sentence.
I'm sorry but who is saying that? Nobody is. If you are paying attention to the context, you will notice they are talking about CSS class names. That's the context, and it's a valid point within that context.
That's why css names should be semantic. I'm sure it started actually purple until UX said "can we make this primary text more blue so it doesn't look like a clicked link?" Replacing all references to "purple" wasn't an option because of unrelated usage of that word elsewhere and they weren't using an IDE capable of contextual rename of a css class. So they just changed the color code and called it a day.
sed -i 's/.purple/.not-purple/g' *.cssdone, boss
This just gave me a panic attack
It's fine as long as you have proper source control. Run it and check the diff before committing.
But I set my
.gitdirectories to have.cssfilename extensions!!?! It shouldn’t be my job to educate you.Gotta do it on the HTML files and JS files too. Then you gotta re-test every page that uses those files.
Then the boss looks over your code and asks why you didn’t just change the actual color because that’s easier to QC.
Yeah, but if you just used css variables, this would’ve been a doddle. One and done.
I’m sorry but the solution to every argument is not just to throw of the word “semantic” in the sentence. Context is everything.
I'm sorry but who is saying that? Nobody is. If you are paying attention to the context, you will notice they are talking about CSS class names. That's the context, and it's a valid point within that context.
Fun fact: Purple doesn't exist.
Neither does magenta
Nor brown
Excuse me, don't you mean dark orange?
Sure does, as a mixture of multiple wavelengths.
the popups on the mobile version of this site are nauseating
My apologies. With Firefox and uBlock Origin I don't see any ads or popups anymore.
Hey if you're colourblind, all blues can be blurple. And so can all purples!
Why is a color class also changing the display to inline is what I wanna know
Tip of the iceberg. I’m perplexed about every 30 minutes working on this codebase.
My guess is that this tactical tornado here didn't know the difference between a span and a div
I prefer the color plue, myself.
Set up something to change all fonts to Comic Sans before you leave. That's all the help I can offer you, OP
That’s bleal not blurple.
Still better than brorange.
Broforce's favorite fruit
I prefer pluep