mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
Gecko engine for Wine
5c62ce11f2
When asked to scroll a 1,1 appunit rectangle into view, ScrollFrameRectIntoView will now actually succeed! For example if the window is 6000 appunits high and we ask to scroll a 1x1 rect at 0,6000 into view, before bug 681192 was fixed we'd actually fail to do so. We'd compute a desired scroll destination of 0,1, and ScrollTo would round that to 0,0 and we wouldn't scroll at all. Now, we compute a desired scroll destination of 0,1 but also an allowed scroll range for y of "1 to <someting large>", so ScrollFrameRectIntoView will scroll down by a full pixel to 0,60. This is correct --- it gets the subpixel area into view, which the previous code didn't --- but it's not really what DoAutoScroll wants, at least the way test_mousecapture.xul is written. test_mousecapture.xul expects DoAutoScroll to scroll windowheight+N into view by scrolling down by exactly N pixels, so the desired point is exactly at the bottom edge of the window rect. Using a zero-sized rect achieves this. --HG-- extra : rebase_source : 5d3d8cc4417c35dc88ad296a4f13e01d2c1c9233 |
||
---|---|---|
accessible | ||
b2g | ||
browser | ||
build | ||
caps | ||
chrome | ||
config | ||
content | ||
db/sqlite3 | ||
dbm | ||
docshell | ||
dom | ||
editor | ||
embedding | ||
extensions | ||
gfx | ||
hal | ||
image | ||
intl | ||
ipc | ||
js | ||
layout | ||
media | ||
memory | ||
mfbt | ||
mobile | ||
modules | ||
mozglue | ||
netwerk | ||
nsprpub | ||
other-licenses | ||
parser | ||
probes | ||
profile | ||
rdf | ||
security | ||
services | ||
startupcache | ||
storage | ||
testing | ||
toolkit | ||
tools | ||
uriloader | ||
view | ||
webapprt | ||
widget | ||
xpcom | ||
xpfe | ||
xulrunner | ||
.gdbinit | ||
.gitignore | ||
.hgignore | ||
.hgtags | ||
aclocal.m4 | ||
allmakefiles.sh | ||
client.mk | ||
client.py | ||
configure.in | ||
LEGAL | ||
LICENSE | ||
Makefile.in | ||
README.txt |
An explanation of the Mozilla Source Code Directory Structure and links to project pages with documentation can be found at: https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure For information on how to build Mozilla from the source code, see: http://developer.mozilla.org/en/docs/Build_Documentation To have your bug fix / feature added to Mozilla, you should create a patch and submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at: http://developer.mozilla.org/en/docs/Creating_a_patch http://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree If you have a question about developing Mozilla, and can't find the solution on http://developer.mozilla.org, you can try asking your question in a mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups are accessible on Google Groups, or news.mozilla.org with a NNTP reader.] You can download nightly development builds from the Mozilla FTP server. Keep in mind that nightly builds, which are used by Mozilla developers for testing, may be buggy. Firefox nightlies, for example, can be found at: ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/ - or - http://nightly.mozilla.org/