Closed
Bug 219542
Opened 21 years ago
Closed 6 years ago
<home> and <end> keys not working in mail composition
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: MMx, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20030916 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20030916 When composing an email on my PB G4, the <home> and <end> keys (fn+< or fn+>) are not working. Reproducible: Always Steps to Reproduce: 1.write an email 2.hit <home> or <end> with the cursor in the middle of one line Actual Results: nothing. Expected Results: jump to the beginning (or end) of the current line already existed in 1.3.1 and 1.4
Comment 1•20 years ago
|
||
WFM with seamonkey 2004-09-28 build 5 and Thunderbird 0.8, on Windows XP. Tested both HTML and plaintext mail.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 2•20 years ago
|
||
reopening as this bug is not about WinXP, nor Windows at all. It is MacOS X and still does not work in "Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; de-AT; rv:1.8a3) Gecko/20040817", will test it in 1.8a4 soon.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Reporter | ||
Updated•20 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: esther
Updated•20 years ago
|
Product: MailNews → Core
*** Bug 279822 has been marked as a duplicate of this bug. ***
Reproducable all the time also. I'm also on a PowerBook G4, MacOS 10.3.8. Is this only a PowerBook issue? Can someone check on a different keyboard?
Comment 5•19 years ago
|
||
The problem seems /not/ to be Mozilla's actual key recognition, as the keyboard test page <https://bugzilla.mozilla.org/show_bug.cgi?id=50255> shows correct key codes for Fn+<-/Fn+-> (and even for the Fn+F-Keys that do not work as expected from other platforms, eg. F9 should open the sidebar).
Comment 6•17 years ago
|
||
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Comment 7•17 years ago
|
||
I have collected all of the bugs that display these symptoms under Bug 389768.
Comment 9•16 years ago
|
||
version 3.0a2pre (2008062703) fn+(right arrow), which should be END, moves to the scrollbar to the BOTTOM. fn+(left arrow), which should be HOME, moves the scrollbar to the TOP. This is the same functionality in Firefox 3.0 and the nightly build of Thunderbird I am using. The keys do not appear to have anything to do with cursor placement, only scrollbar placement. When I am in an Text Input Box (like the one I'm typing in right this second), the keys do not do anything at all if there is no scroll bar. Once a scrollbar appears though, then the keys have the same TOP/BOTTOM scrollbar functionality. Perhaps the correct functionality is if you are in a Text Input Box, the keys should perform as the original report requests. Makes sense to me at least. But I've never used these keys for either thing. I will say, in Thunderbird CTRL-A moves your cursor to the beginning of your current line and CTRL-E moves you to the end of your current line.
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Comment 10•6 years ago
|
||
Is this bug still valid after all the years. The reporter mentions de-AT locale (maybe also keyboard) on Mac OS X.
Flags: needinfo?(richard.marti)
Comment 11•6 years ago
|
||
fn+left arrow/right arrow does nothing but CMD+left arrow/right arrow which are the default keys for this functionality. Maybe this has changed in this 10 years.
Status: NEW → RESOLVED
Closed: 20 years ago → 6 years ago
Flags: needinfo?(richard.marti)
Resolution: --- → WORKSFORME
Reporter | ||
Comment 12•6 years ago
|
||
Yes, I can confirm these key combinations work also on a German MacOS X 10.11, in recent release versions of both Seamonkey and Thunderbird. The dedicated "home" and "end" keys on the fullsize Apple keyboard still don't work, but they also don't work in Apple applications, so I guess that's "broken by design".
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•