Updated syntax highlighting causes issue for namespaced CSS selectors about language-css HOT 3 CLOSED

Also, you may be unaware the CSS spec already features a formal namespace construct, which this grammar is already highlighting. It would be strange (and potentially confusing) to tokenise Facebook's internal/non-standard "namespaces" in conjunction with "true" CSS namespaces.

A CSS selector which contains an unescaped slash is invalid: the entire selector block will be dropped from the parsed stylesheet. This is the sort of error that should be visible to a user.

You can always use your stylesheet to override the error highlighting:

.syntax--css{
	&.syntax--bad-identifier{
		background-color: transparent !important;
		color: inherit !important;
	}
}

from language-css.

Uhm, this grammar adheres quite strictly to the formal grammar defined by the CSS specification. It wouldn't be fair to add such an ad-hoc exception.

What's stopping you from bundling a fork with Nuclide?

from language-css.

It looks like this has been resolved?

from language-css.