Closed ghost closed 6 years ago
This matches the behavior of the default CSS package.
As I understand the specs, user agents indeed should interpret values case-insensitively. However, the specification for translateX
very clearly and consistently capitalizes the X. Wether or not lower-case x also works to me sounds like an implementation detail. I don't feel like trying to figure out exactly what is considered case-sensitive and what isn't, when the spec already clearly states the "correct" or at least "canonical" case.
But if you can get the default CSS package to change to case-insensitive highlighting, I'll follow.
By the way, thanks for contributing ideas! 🏅
By default all CSS syntax is case-insensitive. Current highlighting is case-sensitive and breaks when CSS properties or values use different case from what's defined in the
.sublime-syntax
files.Here's a concise SO answer on the topic.
Cheers!