Confirming on trunk: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20060415 Firefox/3.0a1
Assignee: nobody → selection
Status: UNCONFIRMED → NEW
Component: Keyboard Navigation → Selection
Ever confirmed: true
OS: Windows ME → All
Product: Firefox → Core
QA Contact: keyboard.navigation
Hardware: PC → All
Version: unspecified → Trunk
We probably need to set the hint (to HINTRIGHT) somewhere, but I'm not sure where. Perhaps in nsTypedSelection::setAnchorFocusRange()? Robert, Blake - ideas?
I guess so. Maybe the thing to do is to HINTRIGHT if the anchor is moved earlier in the document, and HINTLEFT if the anchor is moved later.
I don't think so. Specifically, In this testcase, I would expect setting the selection to offset 5 to move the caret to the beginning of the second line, regardless of where it was previously. I can't think of a case where HINTLEFT would yield the expected result, except perhaps for the bidi case (between reverse-direction frames), where either hint would be equally "correct", IMO. We just have to make sure that wherever we're setting the hint only affects programmatic changes to the selection, and doesn't interfere with the other use cases (arrows, mouse, typing, etc.).
Yeah, OK. It looks like the only places calling setAnchorFocusRange to something non-empty are AddRange, RemoveRange and Collapse, none of which should have reasonable expectations about the hint afterwards.
Created attachment 218987 [details] [diff] [review] patch
Checked in: Checking in layout/generic/nsSelection.cpp; /cvsroot/mozilla/layout/generic/nsSelection.cpp,v <-- nsSelection.cpp new revision: 3.228; previous revision: 3.227 done
Status: ASSIGNED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9alpha
*** Bug 333276 has been marked as a duplicate of this bug. ***
*** Bug 327653 has been marked as a duplicate of this bug. ***
*** Bug 356034 has been marked as a duplicate of this bug. ***
This bug has reappeared or is still there in SeaMonkey 1.1.11, but is absent in Firefox Firefox/3.0.1. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11) Gecko/2008070208 Firefox/3.0.1 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20080702 MultiZilla/22.214.171.124e SeaMonkey/1.1.11
(In reply to comment #11) SeaMonkey 1.1.x is based on Gecko 1.8.1. This bug was only fixed for Gecko 1.9.0, hence the fix is not yet available in SeaMonkey.
You need to log in before you can comment on or make changes to this bug.