Closed Bug 940632 Opened 11 years ago Closed 11 years ago

Fixup findbar scroll positioning code and remove some text zoom cruft

Categories

(Firefox for Metro Graveyard :: Browser, defect)

x86_64
Windows 8.1
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 28

People

(Reporter: jimm, Assigned: jimm)

References

Details

Attachments

(1 file, 1 obsolete file)

      No description provided.
Attached patch patch v.1 (obsolete) — Splinter Review
Attached patch patch v.1Splinter Review
Improving how we position selected text generated by the find bar. This was partially broken, the css wasn't working and positioning was off.

Note I specifically do not want to run these coords through the browser translation routines in bindings since I'm controlling browser offsets here myself.

Also, this doesn't fix find text positioning with zoom. I've kicked off an email thread with kats and botond on this. We currently don't have a way to tell the apzc to center on a dom point which we'll need to make this work perfectly.
Attachment #8335224 - Attachment is obsolete: true
Attachment #8335228 - Flags: review?(mbrubeck)
(In reply to Jim Mathies [:jimm] from comment #2)
> Also, this doesn't fix find text positioning with zoom. I've kicked off an
> email thread with kats and botond on this. We currently don't have a way to
> tell the apzc to center on a dom point which we'll need to make this work
> perfectly.

There's a patch posted in bug 940952 for this. I had to touch up some of the scroll values using the current scale.
Comment on attachment 8335228 [details] [diff] [review]
patch v.1

Review of attachment 8335228 [details] [diff] [review]:
-----------------------------------------------------------------

::: browser/metro/base/content/browser-scripts.js
@@ -101,5 @@
>    ["SelectHelperUI", "chrome://browser/content/helperui/SelectHelperUI.js"],
>    ["SelectionHelperUI", "chrome://browser/content/helperui/SelectionHelperUI.js"],
>    ["SelectionPrototype", "chrome://browser/content/library/SelectionPrototype.js"],
>    ["ChromeSelectionHandler", "chrome://browser/content/helperui/ChromeSelectionHandler.js"],
> -  ["AnimatedZoom", "chrome://browser/content/AnimatedZoom.js"],

Can we delete this file now?

::: browser/metro/base/content/helperui/FindHelperUI.js
@@ +193,4 @@
>  
> +    // Adjust for keyboad display and position the text selection rect in
> +    // the middle of the viewable area.
> +    let xPos = aElementRect.center().x;

Why are we scrolling to the horizontal center of the rect?  Shouldn't we scroll to the top left of the rect, so that its top left ends up near the top left of the screen?
Attachment #8335228 - Flags: review?(mbrubeck) → review+
(In reply to Matt Brubeck (:mbrubeck) from comment #4)
> Comment on attachment 8335228 [details] [diff] [review]
> patch v.1
> 
> Review of attachment 8335228 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> ::: browser/metro/base/content/browser-scripts.js
> @@ -101,5 @@
> >    ["SelectHelperUI", "chrome://browser/content/helperui/SelectHelperUI.js"],
> >    ["SelectionHelperUI", "chrome://browser/content/helperui/SelectionHelperUI.js"],
> >    ["SelectionPrototype", "chrome://browser/content/library/SelectionPrototype.js"],
> >    ["ChromeSelectionHandler", "chrome://browser/content/helperui/ChromeSelectionHandler.js"],
> > -  ["AnimatedZoom", "chrome://browser/content/AnimatedZoom.js"],
> 
> Can we delete this file now?

yeah totally.

> ::: browser/metro/base/content/helperui/FindHelperUI.js
> @@ +193,4 @@
> >  
> > +    // Adjust for keyboad display and position the text selection rect in
> > +    // the middle of the viewable area.
> > +    let xPos = aElementRect.center().x;
> 
> Why are we scrolling to the horizontal center of the rect?  Shouldn't we
> scroll to the top left of the rect, so that its top left ends up near the
> top left of the screen?

I'd also like to make this change. Since you're cool with this then I'll go ahead and change it. I filed bug 941032 on improving the logic here as well.
follow up to fix some test failures - 

https://hg.mozilla.org/integration/fx-team/rev/a15e63b297e4
https://hg.mozilla.org/mozilla-central/rev/930f4fee3e3d
https://hg.mozilla.org/mozilla-central/rev/a15e63b297e4
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 28
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: