The java front end is handling zoom now. We shouldn't need to and
so don't need these transformations at all. This fixes link
hilighting because we're now selecting the right element to hilight.
--HG--
extra : rebase_source : 961b7bba2e7ae90eac7a8957867af7aea11b737b
This fixes scrollToFocusedInput by doing the extra scrolling that scrollIntoView
can't do (due to the way we zoom), and by making sure the events land in the
right order.
While the bug was originally filed for the Java-compositor version of fennec,
the same symptoms also occur in Maple. This patch removes the vbox that browsers
were put in, as it's no longer necessary.
Zooming in caused the right and bottom edges of the page to be clipped. This
was because we would try to scroll to coordinates that, untransformed, would be
invalid. The document has no knowledge of the zoom, and so the scroll position
needs to be forced somehow.
Java compositor accomplished this using a CSS translation transformation, this
accomplishes it by turning off scroll position clamping (a technique that the
Java compositor should also employ, if the patch this relies on passes review).
This reduces the paint rate on things like runfield
so that we only paint at the rate that we're invalidating.
We do so by not requesting render in endTransaction
It looks like endTransaction is only called by endDrawing
on the gecko thread and only on VirtualLayers. We don't
need the extra requestRender call because we've already
done the rendering.
Zooming in caused the right and bottom edges of the page to be clipped. This
was because we would try to scroll to coordinates that, untransformed, would be
invalid. The document has no knowledge of the zoom, and so the scroll position
needs to be forced somehow.
Java compositor accomplished this using a CSS translation transformation, this
accomplishes it by turning off scroll position clamping (a technique that the
Java compositor should also employ, if the patch this relies on passes review).
Realised I made a mistake with the nsIFrameLoaderOwner.clampScrollPosition
patch and I want this to go in as a single commit and not break building of
Maple.
Zooming in caused the right and bottom edges of the page to be clipped. This
was because we would try to scroll to coordinates that, untransformed, would be
invalid. The document has no knowledge of the zoom, and so the scroll position
needs to be forced somehow.
Java compositor accomplished this using a CSS translation transformation, this
accomplishes it by turning off scroll position clamping (a technique that the
Java compositor should also employ, if the patch this relies on passes review).
--HG--
extra : rebase_source : a13403d53fed39e1f042da3611147da1c0420cf0
Window size was being treated as equivalent to screen size, which it isn't.
Make sure to send the size-changed event when either the window size or the
screen size change, and to properly differentiate between the two.
