Comment 42 for bug 1347305

Before even reading any intervening comments, I'd like to apologize for the tone of my previous comment.

It's just that it's depressing to go from the positive thought of "today I'm going to finally migrate to a new Thunderbird, with all the problems I've had with it fixed!" to "oh, there's now even more problems to fix, and there's no hope of getting them fixed upstream because they're intentional changes.". Add in the difficulty (impossibility?) of reverting / ignoring CSS changes, as opposed to explicitly overriding them with hardcoded values, and my frustration boiled over.

Since my previous comment, I've discovered that part of the reason I didn't think any of the existing userChrome.css fixes were enough to revert the change is that I was trying to revert the compose UI to the form it had in TB2, whereas the form the existing fixes were trying to restore is apparently one which was introduced sometime between TB5 and TB8. I think I can probably adjust to that form of the UI if necessary, I just wasn't expecting it to have changed.