0d8eab05c652fa854c4eaa508657f404e433ab0f: Bug 1273468 - Revert video controls to use prefixed Fullscreen API again. r?dolske draft
Xidorn Quan <me@upsuper.org> - Thu, 19 May 2016 10:30:54 +1000 - rev 368545
Push 18576 by xquan@mozilla.com at Thu, 19 May 2016 00:35:18 +0000
Bug 1273468 - Revert video controls to use prefixed Fullscreen API again. r?dolske MozReview-Commit-ID: IlxS0MFTxIk
e64dc989d8f29cf8fbf50f3a69642f039dc1fd5d: Bug 810981 - Part 4 - Test session store scroll position and zoom level handling. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Fri, 06 May 2016 18:44:42 +0200 - rev 368544
Push 18575 by mozilla@buttercookie.de at Thu, 19 May 2016 00:26:17 +0000
Bug 810981 - Part 4 - Test session store scroll position and zoom level handling. r=margaret MozReview-Commit-ID: 4jZ0ixoJmOO
264a90c507e5764dc3a1327906addbad5a44a30f: Bug 810981 - Part 4 - Test session store scroll position and zoom level handling. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Fri, 06 May 2016 18:44:42 +0200 - rev 368543
Push 18574 by mozilla@buttercookie.de at Thu, 19 May 2016 00:23:12 +0000
Bug 810981 - Part 4 - Test session store scroll position and zoom level handling. r=margaret MozReview-Commit-ID: 4jZ0ixoJmOO
afe7dc9f1fd189484b2c7b9dd6685ea972ebb641: Bug 810981 - Part 3 - Recalculate zoom level before restoring to a different screen orientation. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 18 May 2016 22:53:34 +0200 - rev 368542
Push 18574 by mozilla@buttercookie.de at Thu, 19 May 2016 00:23:12 +0000
Bug 810981 - Part 3 - Recalculate zoom level before restoring to a different screen orientation. r=margaret On pages that aren't "width=device-width" or similar, Gecko adjusts the resolution when the display dimensions change, e.g. because the device has been rotated. The session store needs to do something similar when restoring a page if the device orientation has changed since the moment the tab state was captured. Therefore, we now include the width of the browser window in the saved zoom data and use it to scale the zoom level as necessary when restoring a tab. MozReview-Commit-ID: LBbEquO1bZ9
d837e8012f321fe350f1a81023a49517e8dbd3de: Bug 810981 - Part 2 - Save the current zoom level when scrolling. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 18 May 2016 22:58:46 +0200 - rev 368541
Push 18574 by mozilla@buttercookie.de at Thu, 19 May 2016 00:23:12 +0000
Bug 810981 - Part 2 - Save the current zoom level when scrolling. r=margaret Since we're now recording the scroll position in the session data, it makes sense to store the zoom level as well. To do this, we make use of the new facility introduced in bug 1270019, which allows us to provide a desired initial resolution to the MobileViewportManager. For this to work, we need to send our desired zoom level before the MVM calculates the initial page resolution, i.e. before first paint/page load. Therefore, we now have browser.js notify us of location change events, so we can set the zoom level to restore early enough. This also means that we can no longer restore the scroll position on load, because the MobileViewportManager applies the resolution we provide it via utils.setRestoreResolution() only after the first paint or page load ( whichever happens earlier). In the latter case, our JS load event handler will run shortly before the MVM has applied the desired zoom level in its own event handling code, which means that any scroll attempt which depends on the page already being zoomed in will fail to apply. Therefore, the scroll position restoring needs to be moved to a later point in time, i.e. in this case the "pageshow" event. MozReview-Commit-ID: 6NtYqc8pm3N
66d408e96c2000fdff193f8960978b616cf8c361: Bug 1272831 - Add AutoRestore::SavedValue() to retrieve the saved value. draft
Ting-Yu Lin <tlin@mozilla.com> - Sat, 14 May 2016 09:47:14 +0800 - rev 368540
Push 18573 by bmo:tlin@mozilla.com at Thu, 19 May 2016 00:05:09 +0000
Bug 1272831 - Add AutoRestore::SavedValue() to retrieve the saved value. MozReview-Commit-ID: eZCWmTpvXi
0c1dc950b3ab1e0b5ce4c449ed2056ac2b65cbf9: Bug 1274092 - Use "branch" instead of "revision" with hg tool; r?jlund draft
Gregory Szorc <gps@mozilla.com> - Wed, 18 May 2016 16:46:24 -0700 - rev 368539
Push 18572 by bmo:gps@mozilla.com at Thu, 19 May 2016 00:03:05 +0000
Bug 1274092 - Use "branch" instead of "revision" with hg tool; r?jlund The new tool has different behavior for "revision" and "branch:" if you pass a name to "revision" and it already resolves, it won't attempt a pull because it thinks it already has the revision. That would be bad. So convert consumers using the "hg" tool to pass "branch" when using symbol names. MozReview-Commit-ID: Ix2jt3XabW2
1ed6e95158847d04a61e7a3b709693a9522963a7: Bug 1274088 - [e10s] Remove release=0% in the e10s rollout add-on for 47. r=mconley draft
Felipe Gomes <felipc@gmail.com> - Wed, 18 May 2016 20:53:42 -0300 - rev 368538
Push 18571 by felipc@gmail.com at Wed, 18 May 2016 23:54:20 +0000
Bug 1274088 - [e10s] Remove release=0% in the e10s rollout add-on for 47. r=mconley MozReview-Commit-ID: JD4m11hJboU
ac557b824cf378a638a4b2a9f343fa00c9356e95: Bug 810981 - Part 4 - Test session store scroll position and zoom level handling. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Fri, 06 May 2016 18:44:42 +0200 - rev 368537
Push 18570 by mozilla@buttercookie.de at Wed, 18 May 2016 23:48:42 +0000
Bug 810981 - Part 4 - Test session store scroll position and zoom level handling. r=margaret MozReview-Commit-ID: 4jZ0ixoJmOO
fdd2ba815072a68d2b824328cb4bd5b102d03113: Bug 810981 - Part 3 - Recalculate zoom level before restoring to a different screen orientation. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 18 May 2016 22:53:34 +0200 - rev 368536
Push 18570 by mozilla@buttercookie.de at Wed, 18 May 2016 23:48:42 +0000
Bug 810981 - Part 3 - Recalculate zoom level before restoring to a different screen orientation. r=margaret On pages that aren't "width=device-width" or similar, Gecko adjusts the resolution when the display dimensions change, e.g. because the device has been rotated. The session store needs to do something similar when restoring a page if the device orientation has changed since the moment the tab state was captured. Therefore, we now include the width of the browser window in the saved zoom data and use it to scale the zoom level as necessary when restoring a tab. MozReview-Commit-ID: LBbEquO1bZ9
84eb8e0f59a6257808874bd64cebe1ea43357046: Bug 810981 - Part 2 - Save the current zoom level when scrolling. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 18 May 2016 22:58:46 +0200 - rev 368535
Push 18570 by mozilla@buttercookie.de at Wed, 18 May 2016 23:48:42 +0000
Bug 810981 - Part 2 - Save the current zoom level when scrolling. r=margaret Since we're now recording the scroll position in the session data, it makes sense to store the zoom level as well. To do this, we make use of the new facility introduced in bug 1270019, which allows us to provide a desired initial resolution to the MobileViewportManager. For this to work, we need to send our desired zoom level before the MVM calculates the initial page resolution, i.e. before first paint/page load. Therefore, we now have browser.js notify us of location change events, so we can set the zoom level early enough. This also means that we can no longer restore the scroll position on load, because the MobileViewportManager applies the resolution we provide it via utils.setRestoreResolution() only after the first paint or page load ( whichever happens earlier). In the latter case, our JS load event handler will run shortly before the MVM has applied the desired zoom level in its own event handling code, which means that any scroll attempt which depends on the page already being zoomed in will fail to apply. Therefore, the scroll position restoring needs to be moved to a later point in time, i.e. in this case the "pageshow" event. MozReview-Commit-ID: 6NtYqc8pm3N
36d5214b1f8f6bbdca51cc080c21ccf68140784a: Bug 810981 - Part 1 - Record current scroll position in mobile session store. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 18 May 2016 22:24:16 +0200 - rev 368534
Push 18570 by mozilla@buttercookie.de at Wed, 18 May 2016 23:48:42 +0000
Bug 810981 - Part 1 - Record current scroll position in mobile session store. r=margaret This copies the approach we've taken for form data saving and applies it to recording the current scroll position of the page, too. This means that after receiving a scroll event, we capture the scroll position for the top level document and all direct child frames and include it in the session store data. Because compared to the form data input events the scroll event can fire at a relatively high rate, we throttle the scroll position capturing using timeouts to run at most twice per second. MozReview-Commit-ID: C0lBxzHav7Z
74f58ed96b69adeba4b61ff59474fd70d0e74c40: Bug 810981 - Part 4 - Test session store scroll position and zoom level handling. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Fri, 06 May 2016 18:44:42 +0200 - rev 368533
Push 18569 by mozilla@buttercookie.de at Wed, 18 May 2016 23:45:40 +0000
Bug 810981 - Part 4 - Test session store scroll position and zoom level handling. r=margaret MozReview-Commit-ID: 4jZ0ixoJmOO
f4f6fd101ee83025ce44144d4f46ffae6b65b476: Bug 810981 - Part 3 - Recalculate zoom level before restoring to a different screen orientation. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 18 May 2016 22:53:34 +0200 - rev 368532
Push 18569 by mozilla@buttercookie.de at Wed, 18 May 2016 23:45:40 +0000
Bug 810981 - Part 3 - Recalculate zoom level before restoring to a different screen orientation. r=margaret On pages that aren't "width=device-width" or similar, Gecko adjusts the resolution when the display dimensions change, e.g. because the device has been rotated. The session store needs to do something similar when restoring a page if the device orientation has changed since the moment the tab state was captured. Therefore, we now include the width of the browser window in the saved zoom data and use it to scale the zoom level as necessary when restoring a tab. MozReview-Commit-ID: LBbEquO1bZ9
b1cd04ed0ea25fd868a83126ce56c05a3f5cca22: Bug 810981 - Part 2 - Save the current zoom level when scrolling. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 18 May 2016 22:58:46 +0200 - rev 368531
Push 18569 by mozilla@buttercookie.de at Wed, 18 May 2016 23:45:40 +0000
Bug 810981 - Part 2 - Save the current zoom level when scrolling. r=margaret Since we're now recording the scroll position in the session data, it makes sense to store the zoom level as well. To do this, we make use of the new facility introduced in bug 1270019, which allows us to provide a desired initial resolution to the MobileViewportManager. For this to work, we need to send our desired zoom level before the MVM calculates the initial page resolution, i.e. before first paint/page load. Therefore, we now have browser.js notify us of location change events, so we can set the zoom level early enough. This also means that we can no longer restore the scroll position on load, because the MobileViewportManager applies the resolution we provide it via utils.setRestoreResolution() only after the first paint or page load ( whichever happens earlier). In the latter case, our JS load event handler will run shortly before the MVM has applied the desired zoom level in its own event handling code, which means that any scroll attempt which depends on the page already being zoomed in will fail to apply. Therefore, the scroll position restoring needs to be moved to a later point in time, i.e. in this case the "pageshow" event. MozReview-Commit-ID: 6NtYqc8pm3N
17beab7ff8835730c5199473a0ab63d4b3269d24: Bug 810981 - Part 1 - Record current scroll position in mobile session store. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 18 May 2016 22:24:16 +0200 - rev 368530
Push 18569 by mozilla@buttercookie.de at Wed, 18 May 2016 23:45:40 +0000
Bug 810981 - Part 1 - Record current scroll position in mobile session store. r=margaret This copies the approach we've taken for form data saving and applies it to recording the current scroll position of the page, too. This means that after receiving a scroll event, we capture the scroll position for the top level document and all direct child frames and include it in the session store data. Because compared to the form data input events the scroll event can fire at a relatively high rate, we throttle the scroll position capturing using timeouts to run at most twice per second. MozReview-Commit-ID: C0lBxzHav7Z
2aab5cc2788b2b650b79120e45685a3a6b3452cf: Bug 810981 - Part 4 - Test session store scroll position and zoom level handling. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Fri, 06 May 2016 18:44:42 +0200 - rev 368529
Push 18568 by mozilla@buttercookie.de at Wed, 18 May 2016 23:40:55 +0000
Bug 810981 - Part 4 - Test session store scroll position and zoom level handling. r=margaret MozReview-Commit-ID: 4jZ0ixoJmOO
e7228d77e9fe34a082c3205980c31d6ba8fa7d56: Bug 810981 - Part 3 - Recalculate zoom level before restoring to a different screen orientation. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 18 May 2016 22:53:34 +0200 - rev 368528
Push 18568 by mozilla@buttercookie.de at Wed, 18 May 2016 23:40:55 +0000
Bug 810981 - Part 3 - Recalculate zoom level before restoring to a different screen orientation. r=margaret On pages that aren't "width=device-width" or similar, Gecko adjusts the resolution when the display dimensions change, e.g. because the device has been rotated. The session store needs to do something similar when restoring a page if the device orientation has changed since the moment the tab state was captured. Therefore, we now include the width of the browser window in the saved zoom data and use it to scale the zoom level as necessary when restoring a tab. MozReview-Commit-ID: LBbEquO1bZ9
3591df4765dc7ad71bfcd2476505deb649ac774d: Bug 810981 - Part 2 - Save the current zoom level when scrolling. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 18 May 2016 22:58:46 +0200 - rev 368527
Push 18568 by mozilla@buttercookie.de at Wed, 18 May 2016 23:40:55 +0000
Bug 810981 - Part 2 - Save the current zoom level when scrolling. r=margaret Since we're now recording the scroll position in the session data, it makes sense to store the zoom level as well. To do this, we make use of the new facility introduced in bug 1270019, which allows us to provide a desired initial resolution to the MobileViewportManager. For this to work, we need to send our desired zoom level before the MVM calculates the initial page resolution, i.e. before first paint/page load. Therefore, we now have browser.js notify us of location change events, so we can set the zoom level early enough. This also means that we can no longer restore the scroll position on load, because the MobileViewportManager applies the resolution we provide it via utils.setRestoreResolution() only after the first paint or page load ( whichever happens earlier). In the latter case, our JS load event handler will run shortly before the MVM has applied the desired zoom level in its own event handling code, which means that any scroll attempt which depends on the page already being zoomed in will fail to apply. Therefore, the scroll position restoring needs to be moved to a later point in time, i.e. in this case the "pageshow" event. MozReview-Commit-ID: 6NtYqc8pm3N
9a81c54e9f8b19655701fe94d3109a710fcf2c43: Bug 810981 - Part 1 - Record current scroll position in mobile session store. r=margaret draft
Jan Henning <jh+bugzilla@buttercookie.de> - Wed, 18 May 2016 22:24:16 +0200 - rev 368526
Push 18568 by mozilla@buttercookie.de at Wed, 18 May 2016 23:40:55 +0000
Bug 810981 - Part 1 - Record current scroll position in mobile session store. r=margaret This copies the approach we've taken for form data saving and applies it to recording the current scroll position of the page, too. This means that after receiving a scroll event, we capture the scroll position for the top level document and all direct child frames and include it in the session store data. Because compared to the form data input events the scroll event can fire at a relatively high rate, we throttle the scroll position capturing using timeouts to run at most twice per second. MozReview-Commit-ID: C0lBxzHav7Z
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip