Closed Bug 852576 Opened 13 years ago Closed 13 years ago

Monocle positioning problems when transitioning from caret to drag selection

Categories

(Firefox for Metro Graveyard :: Input, defect)

x86_64
Windows 8.1
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jimm, Assigned: jimm)

References

Details

Attachments

(1 file, 1 obsolete file)

Not sure what causes this, maybe be something in custom dragger. When we swap out a caret monocle for a drag monocle, the monocle image is adjusted down _monocleYHitTextAdjust. Also the starting monocle is adjusted up by the same.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Thought this was addressed, but it's not.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Attached patch patch (obsolete) — Splinter Review
Assignee: nobody → jmathies
Attached patch patchSplinter Review
Slight tweak to the transition phase of this. Sending a markerDragStart and markerDragMove wasn't working quite right. After markerDragStart fires, SelectionHandler sends back updated monocle positions for *both* monocles. Normally during a drag you only update the monocle that isn't being dragged, which prevents the image from getting repositioned underneath your finger. So this patch adds a new 'SwitchMode' message that replace the call to markerDragStart, which gets SelectionHandler set up properly and only updates the monocle that isn't getting dragged.
Attachment #727848 - Attachment is obsolete: true
Attachment #727862 - Flags: review?(mbrubeck)
Comment on attachment 727862 [details] [diff] [review] patch Review of attachment 727862 [details] [diff] [review]: ----------------------------------------------------------------- ::: browser/metro/base/content/contenthandlers/SelectionHandler.js @@ +1050,5 @@ > break; > > + case "Browser:SwitchMode": > + this._onSwitchMode(json.newMode, json.change, json.xPos, json.yPos); > + break; Whitespace nit: This "break" and the ones above it are indented differently than in most of our code.
Attachment #727862 - Flags: review?(mbrubeck) → review+
> Whitespace nit: This "break" and the ones above it are indented differently > than in most of our code. Fixed. https://hg.mozilla.org/integration/mozilla-inbound/rev/6d7a01a43fe4
argh, at least I thought it was. I'll add it to the patch in bug 853604.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
OS: Windows 8 Metro → Windows 8.1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: