efa1ee67e2f18bf17d73af8a45b56f17910f0cf7: Bug 1339250 - Fix error caused by ending an input session immediately after the session is started r=robwu
Matthew Wein <mwein@mozilla.com> - Tue, 14 Feb 2017 12:02:40 +0000 - rev 566976
Push 55398 by hikezoe@mozilla.com at Mon, 24 Apr 2017 08:28:01 +0000
Bug 1339250 - Fix error caused by ending an input session immediately after the session is started r=robwu MozReview-Commit-ID: Gz9B468NTI1
e08459e83d3f3bec47074e88df2ed153aa200f5b: Bug 1299371 - Show context menu in WebExtension popups; r=mixedpuppy
Martin Giger <martin@humanoids.be> - Sun, 19 Feb 2017 11:02:14 +0100 - rev 566975
Push 55398 by hikezoe@mozilla.com at Mon, 24 Apr 2017 08:28:01 +0000
Bug 1299371 - Show context menu in WebExtension popups; r=mixedpuppy MozReview-Commit-ID: 5bty8uurFns
0f8ae1c5e282e0c823262f85d5a9d4bb6c400dc1: Bug 1074642 - When multiple HSTS headers are received, only consider the first. r=keeler,mcmanus
Alex Gaynor <agaynor@mozilla.com> - Thu, 20 Apr 2017 10:03:53 -0400 - rev 566974
Push 55398 by hikezoe@mozilla.com at Mon, 24 Apr 2017 08:28:01 +0000
Bug 1074642 - When multiple HSTS headers are received, only consider the first. r=keeler,mcmanus This implements a plaintext reading of RFC 6797, which says to only consider the first, however it slightly conflicts with RFC 7230, which says that sending multiple headers which can't be merged is illegal (except for a specific whitelist which HSTS isn't in). Chrome also implements HSTS using RFC 6797's description of the parsing algorithm. r=mcmanus,keeler MozReview-Commit-ID: E06uIk2IcEK
d2a6304ad598d45fe8624ba5e48ac951337f098f: Bug 1357869 - Don't assert when we restyle a child provider frame when an ancestor already handled nsChangeHint_ReconstructFrame. r=dbaron
Cameron McCormack <cam@mcc.id.au> - Thu, 20 Apr 2017 17:51:41 +1000 - rev 566973
Push 55398 by hikezoe@mozilla.com at Mon, 24 Apr 2017 08:28:01 +0000
Bug 1357869 - Don't assert when we restyle a child provider frame when an ancestor already handled nsChangeHint_ReconstructFrame. r=dbaron MozReview-Commit-ID: D6mQeyo9zNl
d62218969e313514a266faefd85130eac095c954: Bug 1358726 - fix the assertion failure in AllocateAndWriteBlock(). r=gerald
JW Wang <jwwang@mozilla.com> - Sun, 23 Apr 2017 21:18:07 +0800 - rev 566972
Push 55398 by hikezoe@mozilla.com at Mon, 24 Apr 2017 08:28:01 +0000
Bug 1358726 - fix the assertion failure in AllocateAndWriteBlock(). r=gerald block->mOwners might be empty if all streams for the resource id are closed. We don't bother write the data to the cache since there is no stream to use it. MozReview-Commit-ID: KKiyZqLBjim
1cf690d4c3984aa8ff625bde0db23575e843917c: Bug 1357690 - Increase content density of autofill autocomplte results. r=MattN
Ray Lin <ralin@mozilla.com> - Thu, 20 Apr 2017 10:39:44 +0800 - rev 566971
Push 55398 by hikezoe@mozilla.com at Mon, 24 Apr 2017 08:28:01 +0000
Bug 1357690 - Increase content density of autofill autocomplte results. r=MattN MozReview-Commit-ID: EpV7ZSbq0Ia
402194d128e3ba3315225e7053af77be728065d9: servo: Merge #16555 - Make clip property animatable (from mantaroh:animate_clip); r=hiro
Mantaroh Yoshinaga <mantaroh@gmail.com> - Sun, 23 Apr 2017 18:59:20 -0500 - rev 566970
Push 55398 by hikezoe@mozilla.com at Mon, 24 Apr 2017 08:28:01 +0000
servo: Merge #16555 - Make clip property animatable (from mantaroh:animate_clip); r=hiro <!-- Please describe your changes on the following line: --> This is a PR for https://bugzilla.mozilla.org/show_bug.cgi?id=1356162. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors <!-- Either: --> - [X] There are tests for these changes, a test case will be landed in web-platform-tests in https://bugzilla.mozilla.org/show_bug.cgi?id=1356162 <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. --> Source-Repo: https://github.com/servo/servo Source-Revision: e357ea44bb5bfe657646bcfd19d9585fffb22401
8aec8be61bf23e2ca72776acbeec76861310db16: servo: Merge #16551 - Update WR (improved double border quality, minor API changes) (from glennw:update-wr-mostly-borders); r=jdm
Glenn Watson <github@intuitionlibrary.com> - Sun, 23 Apr 2017 17:50:08 -0500 - rev 566969
Push 55398 by hikezoe@mozilla.com at Mon, 24 Apr 2017 08:28:01 +0000
servo: Merge #16551 - Update WR (improved double border quality, minor API changes) (from glennw:update-wr-mostly-borders); r=jdm Source-Repo: https://github.com/servo/servo Source-Revision: 0f6c883658930006994b2738f059d050c037ffb9
58f94f305112e3e38d1d702700965d39b5678d33: Bug 1241623: Represent legacy -webkit-gradient(linear,...) expressions as an approximately-equivalent linear-gradient() (instead of -moz-linear-gradient()). r=heycam
Daniel Holbert <dholbert@cs.stanford.edu> - Sun, 23 Apr 2017 16:11:10 -0700 - rev 566968
Push 55398 by hikezoe@mozilla.com at Mon, 24 Apr 2017 08:28:01 +0000
Bug 1241623: Represent legacy -webkit-gradient(linear,...) expressions as an approximately-equivalent linear-gradient() (instead of -moz-linear-gradient()). r=heycam Note: Instead of exactly honoring the legacy -webkit-gradient(linear,...) syntax, we aim to simply parse it into something that's approximately equivalent for common use cases. In the legacy -webkit-gradient(linear,...) syntax, authors provide *two arbitrary points* to establish the direction of the gradient, whereas modern linear-gradient() is simpler: it just takes a single "<side-or-corner>" point and fills the box with a gradient in the direction of that side or corner. Before this changeset, we parsed -webkit-gradient(linear,...) into a slightly-less-legacy "-moz-linear-gradient" representation, so that we could honor at least one of the author's specified points (since -moz-linear-gradient accepts a single arbitrary point as the start of the gradient). But that prevents us from deprecating -moz-linear-gradient, and it makes it impossible to spec our emulation behavior in terms of modern standards. So, this changeset is just changing our approximate representation so that it can always be serializeable as a modern linear-gradient() expression. In addition, I'm removing the reftest "webkit-gradient-approx-linear-1.html" (whose behavior this patch is changing slightly) and I'm replacing it with a new chunk in test_computed_style.html to more directly test this parsing behaivor. MozReview-Commit-ID: 6N1oKaGeOuE
544a262032da88c7dd9a244170c4805af1f3f023: Bug 1358972. P2 - remove MediaDecoder::mEstimatedDuration and its friends which is never modified. draft
JW Wang <jwwang@mozilla.com> - Mon, 17 Apr 2017 17:20:06 +0800 - rev 566967
Push 55397 by jwwang@mozilla.com at Mon, 24 Apr 2017 08:20:24 +0000
Bug 1358972. P2 - remove MediaDecoder::mEstimatedDuration and its friends which is never modified. MozReview-Commit-ID: 7W331tookXV
c460de7e79cce1b04b9fc2d408de1d63aa0c8b82: Bug 1358972. P1 - remove unused code. draft
JW Wang <jwwang@mozilla.com> - Mon, 17 Apr 2017 17:10:09 +0800 - rev 566966
Push 55397 by jwwang@mozilla.com at Mon, 24 Apr 2017 08:20:24 +0000
Bug 1358972. P1 - remove unused code. We can remove AbstractMediaDecoder::UpdateEstimatedMediaDuration() which has no callers at all. MozReview-Commit-ID: Eub12jQ25KK
910ae3e72ec08a53a7714aa02450ad3b8f02ca1f: Bug 1358969 - let MediaDecoder::CurrentPosition() return a TimeUnit. draft
JW Wang <jwwang@mozilla.com> - Mon, 17 Apr 2017 17:04:39 +0800 - rev 566965
Push 55396 by jwwang@mozilla.com at Mon, 24 Apr 2017 08:11:33 +0000
Bug 1358969 - let MediaDecoder::CurrentPosition() return a TimeUnit. We want to replace the use of int64_t for microseconds by TimeUnit whenever possible since int64_t is ambiguous which could be microseconds or milliseconds. MozReview-Commit-ID: K3Bz3uEXLDK
2b0dcc4a421fc18e6124bb0400d98d0a7e9ffad0: Bug 1351146 - P2 - Update test case and usage of nsIRedirectHistoryEntry interface draft
Thomas Nguyen <tnguyen@mozilla.com> - Mon, 24 Apr 2017 16:08:22 +0800 - rev 566964
Push 55395 by bmo:tnguyen@mozilla.com at Mon, 24 Apr 2017 08:08:38 +0000
Bug 1351146 - P2 - Update test case and usage of nsIRedirectHistoryEntry interface MozReview-Commit-ID: s61VV5CLx8
1af6212e31eec52bfbceae2c9c445db0ccaeb93d: Bug 1351146 - P1 - Add more information to redirect chains draft
Thomas Nguyen <tnguyen@mozilla.com> - Mon, 24 Apr 2017 15:59:48 +0800 - rev 566963
Push 55395 by bmo:tnguyen@mozilla.com at Mon, 24 Apr 2017 08:08:38 +0000
Bug 1351146 - P1 - Add more information to redirect chains In order to provide more details context of how client arrived at the unsafe page, particularly in redirect case, we may have to add more information to redirect chains including: - referrer (if any) - remote address. - URL We may want to use an idl interface instead of nsIPrincipal to store these information MozReview-Commit-ID: 3Uh4r06w60C
bc3d0efe7b04bfaa5839016d2526fad6ec4bc4d4: Bug 1355548 - Using cached perference values in WheelTransaction. r?masayuki draft
Stone Shih <sshih@mozilla.com> - Thu, 13 Apr 2017 10:41:23 +0800 - rev 566962
Push 55394 by sshih@mozilla.com at Mon, 24 Apr 2017 08:07:50 +0000
Bug 1355548 - Using cached perference values in WheelTransaction. r?masayuki MozReview-Commit-ID: GpKgMpDwi3w
20c7aae2f19f742f570cdc7c3881b2f91d7b0798: Bug 1356957 - call updateRequest once when update request in netmonitor-controller;r=rickychien draft
Fred Lin <gasolin@mozilla.com> - Mon, 17 Apr 2017 14:21:59 +0800 - rev 566961
Push 55393 by bmo:gasolin@mozilla.com at Mon, 24 Apr 2017 08:04:31 +0000
Bug 1356957 - call updateRequest once when update request in netmonitor-controller;r=rickychien MozReview-Commit-ID: J6lLXNlnJnM
6a58d7169684bc6892137702570bcc09812b7760: Bug 1301310 - Hide input date/time picker only when input element blurs. r?mossop draft
Jessica Jong <jjong@mozilla.com> - Thu, 20 Apr 2017 15:04:10 +0800 - rev 566960
Push 55392 by jjong@mozilla.com at Mon, 24 Apr 2017 07:46:15 +0000
Bug 1301310 - Hide input date/time picker only when input element blurs. r?mossop If we rely on XUL panel's default behavior, the picker is hidden and opened again when we jump from one inner field to another with a mouse click, this is because XUL pannel gets hidden when user clicks outside it with noautohide=false. In order to avoid this, we should close it explicitly only when input element blurs. MozReview-Commit-ID: GxPxd0wPWgM
115bd931e18cbdc1abb3334d69f84e1b18592c5b: Bug 1354507 - Add cookie-related filter options for network requests. r?Honza draft
Vangelis Katsikaros <vkatsikaros@gmail.com> - Fri, 14 Apr 2017 12:34:04 +0300 - rev 566959
Push 55391 by vkatsikaros@gmail.com at Mon, 24 Apr 2017 07:39:43 +0000
Bug 1354507 - Add cookie-related filter options for network requests. r?Honza MozReview-Commit-ID: 48zc0qcasvK
816335f354452b78814193bc86fbd59d4fda841c: Bug 1325538 - Add mochitest for form autofill feature. r?MattN draft
steveck-chung <schung@mozilla.com> - Mon, 17 Apr 2017 18:14:14 +0800 - rev 566958
Push 55390 by bmo:schung@mozilla.com at Mon, 24 Apr 2017 07:21:49 +0000
Bug 1325538 - Add mochitest for form autofill feature. r?MattN MozReview-Commit-ID: HK6dmI4m3co
3983a2ce4f6145f091112db33275aaa315e810f6: Revert "Bug 1351146 - Add more information to redirect chains" draft
Thomas Nguyen <tnguyen@mozilla.com> - Mon, 24 Apr 2017 15:12:38 +0800 - rev 566957
Push 55389 by bmo:tnguyen@mozilla.com at Mon, 24 Apr 2017 07:14:37 +0000
Revert "Bug 1351146 - Add more information to redirect chains" This reverts commit b266610761eceae58ab8758af4e8561cf3326ee6.
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip