Bugzilla

@David
> Just because it's in a spec doesn't mean it's important. There are lots of things that are in specs that we don't implement.
"A" spec. Just some random spec. It's not like it's an important spec. Not, like, one of the spec that govern the entire web. Nah. Not necessarily important. How silly of me to assume it would be.

/s

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. 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?

It's not like I don't know who you are. 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. Why devote this much energy to quashing someone's request that you, or someone you direct, do exactly that?

You're very clearly _resisting_ the idea of getting this and the other associated bug fixed. I won't try to read your mind about why you would do that, but it's pretty clear that you don't want to fix it. So, given your attitude and your role in the project, it presently seems to me that this bug will _never_ be fixed. You might as well mark it "Will not fix, David doesn't think supporting tab-size is important".

@Thomas
We're not clueless about vendor prefix versions. I've said as much. Of course we can work around it.

And hey, we all worked around IE for, what, 20 years? Wasn't _that_ fun?

I'm _not_ here in search of a workaround. I'm trying to find/trigger/elicit an actual solution. If you offered that idea in earnest, then I appreciate the thought, but that's not what I'm here for.

@David
> Just because it's in a spec doesn't mean it's important. There are lots of things that are in specs that we don't implement.

"A" spec. Just some random spec. It's not like it's an important spec. Not, like, one of the spec that govern the entire web. Nah. Not necessarily important. How silly of me to assume it would be.

/s

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. 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?

It's not like I don't know who you are. 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. Why devote this much energy to quashing someone's request that you, or someone you direct, do exactly that?

You're very clearly _resisting_ the idea of getting this and the other associated bug fixed. I won't try to read your mind about why you would do that, but it's pretty clear that you don't want to fix it. So, given your attitude and your role in the project, it presently seems to me that this bug will _never_ be fixed. You might as well mark it "Will not fix, David doesn't think supporting tab-size is important".

@Thomas
We're not clueless about vendor prefix versions. I've said as much. Of course we can work around it.

And hey, we all worked around IE for, what, 20 years? Wasn't _that_ fun?

I'm _not_ here in search of a workaround. I'm trying to find/trigger/elicit an actual solution. If you offered that idea in earnest, then I appreciate the thought, but that's not what I'm here for.