29.07 KB, image/png
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.7.5) Gecko/20050128 Epiphany/1.5.6 (Ubuntu) (Ubuntu package 1.0+dfsg.1-2ubuntu5) Build Identifier: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.7.5) Gecko/20050128 Epiphany/1.5.6 (Ubuntu) (Ubuntu package 1.0+dfsg.1-2ubuntu5) File->Send Now does not have a shortcut on MacOS X, unlike it has on Linux. Reproducible: Always Steps to Reproduce:
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
This is really something which is needed. Dunno why we missed that bug for so many years. :/ Is there any chance to get this into Thunderbird 3?
Status: RESOLVED → UNCONFIRMED
Hardware: Macintosh → All
Resolution: EXPIRED → ---
Version: unspecified → Trunk
Assignee: mscott → nobody
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: message-compose
Neil said that it could be a widget issue on OS X? Josh do you know some limitations? I'll attach a screenshot of VmWare which uses a similar shortcut.
Summary: "Send Now" does not have a shortcut on MacOS X → "Send Now" and "Send later" does not have a shortcut on OS X
Created attachment 334968 [details] Available shortcut for full screen within the main menu of VmWare
It's not an OS X issue, but a XUL-on-OS X issue, or possibly a showing-control-characters-in-XUL-menus-cross-platform issue. I did some experiments which made me feel that showing Enter/Return/Arrows in XUL just doesn't work. Don't know what Toolkit bug this is dependent on.
(In reply to comment #8) > It's not an OS X issue, but a XUL-on-OS X issue, or possibly a > showing-control-characters-in-XUL-menus-cross-platform issue. I did some > experiments which made me feel that showing Enter/Return/Arrows in XUL just > doesn't work. Don't know what Toolkit bug this is dependent on. Steven do you know something on that side?
> Steven do you know something on that side? No. But it might help for David to give more a more detailed description of the experiments he did.
If you provide a testcase XUL file which exhibits this bug, we can push this bug to Widget: Cocoa.
According to comments 6 to 10, this is actually the same as bug 294437, mark as dupe?
standard8 in comment #12 > According to comments 6 to 10, this is actually the same as bug 294437, mark as > dupe? would it be fair to say that patch in bug 294437 won't get into 1.9.1/TB3?
Severity: normal → minor
cmd + return/enter - send cmd + shift + return/enter - send later Perhaps this should be closed?
It seems to be the control characters not displaying that are actually the fault. That's bug 294437.
Status: NEW → RESOLVED
Last Resolved: 13 years ago → 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 294437
You need to log in before you can comment on or make changes to this bug.