Last modified: 2012-10-19 23:46:18 UTC
If in a link inspector or in the edit summary, pressing Page Up, Page Down, Home or End works in that box but also triggers the main edit space to move to the top or bottom. It needs to ignore if it's not got the caret. :-)
Can't reproduce in Firefox 13.0/Linux.
Indeed - the problem as described seems only to happen in Safari and Chrome for me; in Firefox, instead the characters do nothing (pressing "Home" when in revision description box should move caret to before first character).
This is probably fixed now, but I'll have to test in the morning when I have a keyboard with these buttons properly.
Okay, I looked more closely at this bug an understand it better. We're not doing any sort of processing of those keys, so the browser is doing what the browser naturally does. I use a Macbook Air and Chrome most of the time and for moving my cursor around a textarea (including the one that I'm typing in now), I use Command + [up, down, left, right] for jumping to the first char, last char, beginning of line, and end of line. I plugged in an external keyboard with proper page up, page down, home, and end keys and was able to reproduce the described behavior. Trevor and I just spoke about this and we don't think we should try to override the browser's handling of this. A "fix" may have other user experience consequences. Please reopen if you think I'm misunderstanding something.
