1c0b16d1747c0964577a8ec21fa2b0a17b44ea4e: Bug 1328868 - Part 10 - Make about:config handle text zoom changes a bit more gracefully. r=sebastian
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 18 Feb 2017 15:50:08 +0100 - rev 349682
Bug 1328868 - Part 10 - Make about:config handle text zoom changes a bit more gracefully. r=sebastian This means scaling the the size of the images used for buttons and making sure that at large magnifications, the toolbar's text input properly moves into its own line instead of simply overlapping the preference immediately below. We also want to make sure that the text on any buttons remains vertically centred. MozReview-Commit-ID: 7rUf1tucAzL
3e9fce8066be062e5b9fd9b803405c5b45bb316d: Bug 1328868 - Part 9 - Check that zooming via "font.size.systemFontScale" actually has any effect. r=sebastian
Jan Henning <jh+bugzilla@buttercookie.de> - Fri, 10 Feb 2017 19:21:32 +0100 - rev 349681
Bug 1328868 - Part 9 - Check that zooming via "font.size.systemFontScale" actually has any effect. r=sebastian MozReview-Commit-ID: F2YtTER17xQ
e74b4860339d3b7e681187e178665b88961f4bbc: Bug 1328868 - Part 8 - Add a test to check that flipping the Android pref enables/disables font inflation. r=esawin,sebastian
Jan Henning <jh+bugzilla@buttercookie.de> - Fri, 24 Mar 2017 18:24:52 +0100 - rev 349680
Bug 1328868 - Part 8 - Add a test to check that flipping the Android pref enables/disables font inflation. r=esawin,sebastian A basic check that the listener is indeed operational. MozReview-Commit-ID: 6KijcsRaScI
0fac2d0c6f34ca13d1855e5127a02c8143e374a0: Bug 1328868 - Part 7 - Move MakeObserver() into head.js r=esawin
Jan Henning <jh+bugzilla@buttercookie.de> - Sun, 05 Feb 2017 17:11:02 +0100 - rev 349679
Bug 1328868 - Part 7 - Move MakeObserver() into head.js r=esawin We can use this function for our upcoming test as well, so we should move it into the common header. MozReview-Commit-ID: H5ANDAlnpmm
a20ab74f5f7acf724c42e1bf2b0b6b876680ae42: Bug 1328868 - Part 6 - Remove the old font size preference and its associated code and resources. r=sebastian
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 04 Feb 2017 23:57:57 +0100 - rev 349678
Bug 1328868 - Part 6 - Remove the old font size preference and its associated code and resources. r=sebastian MozReview-Commit-ID: EgL3WFo6mdo
96ad7f172a08dce4e59f0e7c5cb90c8274b0bcd3: Bug 1328868 - Part 5 - Add a Java-side listener watching the new pref and the Android system font scale. r=sebastian
Jan Henning <jh+bugzilla@buttercookie.de> - Sun, 05 Feb 2017 13:22:49 +0100 - rev 349677
Bug 1328868 - Part 5 - Add a Java-side listener watching the new pref and the Android system font scale. r=sebastian The state of the switch added in Part 4 is stored in our Android-side shared preferences. For this to have any actual effect on rendering, we now add a class that is initialised when Gecko starts up and listens to changes of that particular pref. When it is turned on, we enable font inflation and add another listener for the system font scale, which then forwards the current font scale as well as any changes to Gecko, so mobile mode pages can be scaled correspondingly as well. When the setting is turned back off again, the system font scale listener is stopped again and the Gecko font size settings reverted back to their default values. MozReview-Commit-ID: GyffpZTQQX8
505a6c976a0bdfe4bf0bb06fd494812eafd90032: Bug 1328868 - Part 4 - Add a new switch offering to honour the system font size to Fennec's preferences. r=sebastian
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 04 Feb 2017 23:54:17 +0100 - rev 349676
Bug 1328868 - Part 4 - Add a new switch offering to honour the system font size to Fennec's preferences. r=sebastian MozReview-Commit-ID: HZqxl6T90mZ
68a4a734f6e1ae1a8c7e299048f7f31c40c97e3b: Bug 1328868 - Part 3 - Make the effective text zoom retrievable from JS. r=tnikkel
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 25 Feb 2017 19:27:15 +0100 - rev 349675
Bug 1328868 - Part 3 - Make the effective text zoom retrievable from JS. r=tnikkel We want to read this value during testing. MozReview-Commit-ID: FVA7VdvSTEt
345ec75c89d620eff01f00ff4de6ab34a87d70e4: Bug 1328868 - Part 2 - Apply the system font scale as an additional text zoom factor to all pages that are not font inflated. r=tnikkel
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 25 Feb 2017 13:22:52 +0100 - rev 349674
Bug 1328868 - Part 2 - Apply the system font scale as an additional text zoom factor to all pages that are not font inflated. r=tnikkel We want to use a similar model as Chrome on Android does for scaling our display of web content, that is use font inflation for desktop pages and plain text zooming for everything else. Since we don't want to simply clobber any text zoom that might have been set by the user/front-end code, we allow setting and storing the system font scale separately on the PresContext. We then calculate the effective text zoom value as the product of the system font scale and the current text zoom value. Any function that is using the PresContext's TextZoom value for layouting/rendering is switched over to this new EffectiveTextZoom value, whereas functions that are interested in the text zoom as actually set by the user/front-end (e.g. the nsDocumentViewer, or the code responsible for copying text and full zoom settings into the new PresContext on page navigation) continue using the plain TextZoom value. As long as font inflation is enabled in principle (e.g. font.size.inflation.minTwips != 0), every page starts out as eligible for font inflation until the relevant meta viewport tags marking the page as "mobile friendly" have been detected. Since the PresShell caches the font inflation state and only recalculates it when necessary, we make use of that and set the PresContext's system font scale as necessary whenever the font inflation state has been refreshed. MozReview-Commit-ID: 2InyE04wKAW
52d7e9ce0dfb1b09a91a8cac82c9d1309ea0c48f: Bug 1328868 - Part 1 - Allow setting a global zoom factor via nsLayoutUtils. r=tnikkel
Jan Henning <jh+bugzilla@buttercookie.de> - Sat, 25 Feb 2017 13:22:45 +0100 - rev 349673
Bug 1328868 - Part 1 - Allow setting a global zoom factor via nsLayoutUtils. r=tnikkel For Android we want to be able to set a global zoom factor that will scale any page where font inflation is not turned on. Android makes the system font scale available as a float factor. For our purposes, converting this to a percentage based value and rounding to an integer is accurate enough and enables us to pass this value as a standard Gecko int preference. This means we can make use of the standard infrastructure for setting and retrieving Gecko-side preferences both from Java and JS (the latter during testing), as opposed to having to write custom JNI and C++/IDL helper functions. To that effect, we implement a method for retrieving that setting via nsLayoutUtils, analogous to the current font inflation settings. Since we later want to clamp the effective text zoom resulting from that setting by zoom.minPercent and maxPercent, we add var caches for them in nsLayoutUtils as well. MozReview-Commit-ID: Ler2YmwzImE
77ec4c9d23c77e1299c5bfa3b2234e8ab7dcca4c: Bug 1328868 - Part 0 - Remove unneeded imports. r=esawin
Jan Henning <jh+bugzilla@buttercookie.de> - Fri, 03 Feb 2017 22:50:30 +0100 - rev 349672
Bug 1328868 - Part 0 - Remove unneeded imports. r=esawin MozReview-Commit-ID: 5mCrZ8aOAiw
a1d828bcc8453dce26b8476d0cf85d28ae1219c5: Bug 1350401: Cleanup outline-painting-related logic. r=mats
Emilio Cobos Álvarez <emilio@crisal.io> - Fri, 24 Mar 2017 19:38:15 +0100 - rev 349671
Bug 1350401: Cleanup outline-painting-related logic. r=mats MozReview-Commit-ID: ggDzDRrPIm
32f2f1e79d9fafc962f78fa85aae884fa561fd25: Bug 1096013 - Add a test that ensures that we don't lose the favicon for background tabs that crash. r=mikedeboer
Mike Conley <mconley@mozilla.com> - Fri, 24 Mar 2017 10:26:49 -0400 - rev 349670
Bug 1096013 - Add a test that ensures that we don't lose the favicon for background tabs that crash. r=mikedeboer MozReview-Commit-ID: BoF62uPSfUC
931854986f7587d59663d9e0c377685d610ec268: Bug 1096013 - Give selected tabs highest priority during restoration. r=mikedeboer
Mike Conley <mconley@mozilla.com> - Thu, 23 Mar 2017 01:59:51 -0400 - rev 349669
Bug 1096013 - Give selected tabs highest priority during restoration. r=mikedeboer MozReview-Commit-ID: EtApFsDyB50
a95b45f37b1386402345b39e23c55ebeaa7aad8b: Bug 1096013 - Show tab icons and titles as soon as possible instead of waiting for history restoration to complete. r=mikedeboer
Mike Conley <mconley@mozilla.com> - Wed, 20 Apr 2016 17:24:24 -0400 - rev 349668
Bug 1096013 - Show tab icons and titles as soon as possible instead of waiting for history restoration to complete. r=mikedeboer MozReview-Commit-ID: EL8IcreTte2
f5e214144799889e2408c4841351f4053f00544e: Merge m-i to m-c, a=merge
Phil Ringnalda <philringnalda@gmail.com> - Sat, 25 Mar 2017 18:39:56 -0700 - rev 349667
Merge m-i to m-c, a=merge
23d64298e8c60a65870ed67266588314dc4bafe0: Bug 1345119 - Part 5: Test browser_boxmodel_offsetparent.js to test front end box model. r=gl
Stanford Lockhart <lockhart@cs.dal.ca> - Sat, 25 Mar 2017 13:43:49 -0300 - rev 349666
Bug 1345119 - Part 5: Test browser_boxmodel_offsetparent.js to test front end box model. r=gl MozReview-Commit-ID: E2PtkTEvqQo
37dac6a2af160d4b9f8497e396355a0ac11108bd: Bug 1345119 - Part 4: Test test_inspector_getOffsetParent for new actor methods. r=pbro
Stanford Lockhart <lockhart@cs.dal.ca> - Tue, 21 Mar 2017 21:59:22 -0300 - rev 349665
Bug 1345119 - Part 4: Test test_inspector_getOffsetParent for new actor methods. r=pbro MozReview-Commit-ID: AqSOEdEZKIy
130016ad042501c81fa95961995dd4def0a9444f: Bug 1345119 - Part 3: Display offset parent of absolutely positioned node in box model. r=gl
Stanford Lockhart <lockhart@cs.dal.ca> - Fri, 17 Mar 2017 23:07:06 -0300 - rev 349664
Bug 1345119 - Part 3: Display offset parent of absolutely positioned node in box model. r=gl MozReview-Commit-ID: 102vRTuIhEh
03e81669e18c97cb1fb7d31890cbaa8076f1ad16: Bug 1345119 - Part 2: Server side for retrieving offset parent of DOM node. r=pbro
Stanford Lockhart <lockhart@cs.dal.ca> - Fri, 17 Mar 2017 23:05:27 -0300 - rev 349663
Bug 1345119 - Part 2: Server side for retrieving offset parent of DOM node. r=pbro MozReview-Commit-ID: I51NHlxv6Mp
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip