#Tailwind publisher add on firefox code#

Why devote this much energy to quashing someone's request that you, or someone you direct, do exactly that? Unless I'm mistaken or out-of-date (admittedly not unusual), you're the guy when it comes to making sure Firefox follows the CSS spec. How can you have any pride in your work and still argue that a failure to support the spec doesn't warrant attention even after it's been failing for eight years? The whole point of a web browser is that it conforms to a spec so that authors can create web content that users can view consistently. Not, like, one of the spec that govern the entire web. There are lots of things that are in specs that we don't implement. But nobody's working on making '-moz-tab-size' work in all cases, because this bug is effectively shielding that bug from ever being in the spotlight by disguising it as a vendor-specific style.ДЄ world in which we have a mostly-spec-supporting 'tab-size' would be a lot better than a world in which we have no 'tab-size' for another 8+ years while you continue to say, 'it's not about how long the bug has been because it's in a spec doesn't mean it's important. However, apparently 'policy' (whose? yours?) says that you can't do that, because '-moz-tab-size' doesn't work right in certain cases and it can't be 'tab-size' until it does. This isn't new tech, it's not a new, complex layer on the web, it's just a single style setting that dictates the width of a single Unicode/ASCII character.ДЇixing this bug would be as simple as putting in an alias for 'tab-size' в†’ '-moz-tab-size'. We're talking about handling simple tab characters, which have existed practically since the dawn of computers. Well, I don't accept your argument as valid. You wrote up that argument 12 years ago and apparently you've been relying on it ever since to deflect reasonable criticisms. I'm looking for support for part of the current CSS spec, on the display of a fundamental Unicode/ASCII character, not some proprietary software, the publisher of which you know the average reader looks at with a sneer. Specifically in this case, I'm not asking you to support MS Word documents. I consider it a very facile argument that relies on a strawman to make its point. Explaining why, in real-world terms, this needs fixing, is clearly ineffectual in motivating anyone.ДЄs for your blog post, I've read it before.

#Tailwind publisher add on firefox code#

I mentioned that this is a problem for a site I use that displays source code that includes tabs. I did that two years ago, if you actually read the history on this bug. (Arguing on the basis of user or developer need, or the basis of what other browsers support, is much more relevant.)