keybaord shortcuts should be next to Thunderbird help.
The screen shots are Mac, so I assume that "About Thunderbird" has not been removed for the other OS.
> For the blog and developer documentation, it's hard to make a case for it.
Developer may be a stretch. But our UX person has requested blog.
And so again I make the case for more direct visibility. We want to educate users, we want more participation then these things be **in front** of our users eyes, which means in the product. Having it on the website is great, sure, it's available. But if it's not in the product, then it's simply not visible to our users. It seems part of what's driving your opinion is a fascination with minimizing the size of menu - I fail to understand how that trumps other goals.
Bug 1134760 Comment 29 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
keybaord shortcuts should be next to Thunderbird help.
The screen shots are Mac, so I assume that "About Thunderbird" has not been removed for the other OS.
> For the blog and developer documentation, it's hard to make a case for it.
Developer may be a stretch. But our UX person has requested blog.
And so again I make the case for more direct visibility. We want to educate users, and we want more participation, then these things be **in front** of our users eyes, which means in the product. Having it on the website is great, sure, it's available. But it's not in the product, so it's simply not visible to our users.
It seems part of what's driving your opinion is a fascination with minimizing the size of menu - I fail to understand how that trumps other goals.
keybaord shortcuts should be next to Thunderbird help.
The screen shots are Mac, so I assume that "About Thunderbird" has not been removed for the other OS.
> For the blog and developer documentation, it's hard to make a case for it.
Developer may be a stretch. But our UX person has requested blog.
And so again I make the case for more direct visibility. We want to educate users, and we want more participation, then these things must be **in front** of our users eyes, which means in the product. Having it on the website is great, sure, it's available. But it's not in the product, so it's simply not visible to our users.
It seems part of what's driving your opinion is a fascination with minimizing the size of menu - I fail to understand how that trumps other goals.