Frank Lion wrote:I don't think you understand what syntax highlighting is.
I most definitely do understand. They're just not highlighted differently. Don't take me for a fool.
Frank Lion wrote:I repeat, you are using a non-valid/non-working xul namespace line......caused by lack of quote marks.
I fixed it when you wrote about it. It doesn't make a difference. (It seems to me that it accepts it either way. I get an error message in the editor when there's a syntax issue)
Frank Lion wrote:If you are going to convince yourself that everything is a Firefox bug, then don't ask for .css advice in a Theme Dev Forum, where people are coding with .css all the time.
I'm not convincing myself to anything. The evidence seems to suggest this.
Particularly:
I tested with a new profile and userchrome.css and I got the exact same issue. So unless the CSS is still bugged somehow, it's a FF bug.
Did you change all fonts (serif/sans/monospace)?
Here ar my particular settings and userchrome.css:
Code: Select all
@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");
* {
font-family:"DejaVu Sans mono" !important;
}
#tabcounter-tabcount{
font-family:"Roboto" !important;
}