d5cf90154e6710b1fcb748c9f934bbdf9dc93a0a: Bug 1286730 IMEStateManager::NotifyIME() should treat NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED same as the other notifications because all of them are notified by IMEContentObserver asynchronously r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 14 Jul 2016 12:11:56 +0900 - rev 330019
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1286730 IMEStateManager::NotifyIME() should treat NOTIFY_IME_OF_COMPOSITION_EVENT_HANDLED same as the other notifications because all of them are notified by IMEContentObserver asynchronously r=smaug MozReview-Commit-ID: 1GJk9bfOqjS
4d4c09eae59ca000cb7a8be79c516527223e306c: Bug 1284844 - Reps: use quotes around text in ObjectWithText. r=me
Hemanth Kumar Veeranki <hems.india1997@gmail.com> - Mon, 11 Jul 2016 14:09:10 -0400 - rev 330018
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1284844 - Reps: use quotes around text in ObjectWithText. r=me MozReview-Commit-ID: ECn7bF3jnzK
5e1db3f6c7527e2b6e9a4cce14ecee5873f7da7b: Bug 1283522 - Reps: support -0 grip in number rep. r=linclark
Steve Chung <schung@mozilla.com> - Wed, 13 Jul 2016 11:37:27 +0800 - rev 330017
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1283522 - Reps: support -0 grip in number rep. r=linclark MozReview-Commit-ID: BWvMlbNdckG
9f1fccf586fb87ab5553a0c4c0f501ad3b7b5c71: Bug 1286444 - Fix types when using VideoPlaybackQuality values - r=kinetik
Gerald Squelart <gsquelart@mozilla.com> - Thu, 14 Jul 2016 15:25:40 +1000 - rev 330016
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1286444 - Fix types when using VideoPlaybackQuality values - r=kinetik These numbers are only used to calculate a percentage, so they don't really need to be 64-bit long. MozReview-Commit-ID: FfdyStjGITL
4667487b0da2abde2e6960fca75fcbde9d114812: Bug 1286444 - Use correct types to construct VideoPlaybackQuality - r=kinetik
Gerald Squelart <gsquelart@mozilla.com> - Thu, 14 Jul 2016 15:18:36 +1000 - rev 330015
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1286444 - Use correct types to construct VideoPlaybackQuality - r=kinetik VideoPlaybackQuality was fed uint64_t's, now it should be given uint32_t's. Note that FrameStatistics currently provide uint32_t's, so we are fine now; nevertheless I added a static_assert to verify that and ensure it stays true. MozReview-Commit-ID: I0dgP1K4lg3
63c2807a44393a652c63953909d96ecfa87811ad: Bug 1286444 - Store uint32_t's in VideoPlaybackQuality - r=kinetik
Gerald Squelart <gsquelart@mozilla.com> - Thu, 14 Jul 2016 14:31:12 +1000 - rev 330014
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1286444 - Store uint32_t's in VideoPlaybackQuality - r=kinetik Because VideoPlaybackQuality attributes are exposed as 'unsigned long' (aka uint32_t) in the webidl interface, it would be dangerous to accept and store them as uint64_t in the class. MozReview-Commit-ID: EhX4lhTbA3c
29c9b171623423acdf3aa228be457c56eee42839: Merge mozilla-central to autoland
Carsten "Tomcat" Book <cbook@mozilla.com> - Thu, 14 Jul 2016 13:49:32 +0200 - rev 330013
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Merge mozilla-central to autoland
cb1812acfcd1ed05706e0bd9405668d11516cfd4: Bug 1286760 - use macro to simplify the code. r=gerald
JW Wang <jwwang@mozilla.com> - Thu, 14 Jul 2016 15:09:06 +0800 - rev 330012
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1286760 - use macro to simplify the code. r=gerald MozReview-Commit-ID: HsAOgQoGuQ5
1a36367af6519b05af0ef0eff184d6951a2274ac: Bug 1286755 - remove duplicate check. r=bechen.
JW Wang <jwwang@mozilla.com> - Thu, 14 Jul 2016 14:21:43 +0800 - rev 330011
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1286755 - remove duplicate check. r=bechen. MozReview-Commit-ID: FhTfHMERpLC
08f8a5aacd8308a73f6040fe522be7ba38497561: merge mozilla-inbound to mozilla-central a=merge
Carsten "Tomcat" Book <cbook@mozilla.com> - Thu, 14 Jul 2016 11:45:54 +0200 - rev 330010
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
merge mozilla-inbound to mozilla-central a=merge
77bd53db031e18f025a25b95d44bc18db26983bd: Bug 1271714. Limit asserts annotations for crashtest to e10s only, cause that's where they happen.
Timothy Nikkel <tnikkel@gmail.com> - Wed, 13 Jul 2016 23:37:13 -0500 - rev 330009
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1271714. Limit asserts annotations for crashtest to e10s only, cause that's where they happen.
0948b9cc4d82c3bf94abff04fecfaf06217fbeda: Bug 1278439 - Adding a missing prefs service null check in url-classifier/. r=gcp.
Nicholas Nethercote <nnethercote@mozilla.com> - Thu, 14 Jul 2016 13:47:54 +1000 - rev 330008
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1278439 - Adding a missing prefs service null check in url-classifier/. r=gcp.
00e10deea23befbf32097b0df836e11b42170f19: Bug 1278439 - Adding a missing prefs service null check in startupcache/. r=froydnj.
Nicholas Nethercote <nnethercote@mozilla.com> - Thu, 14 Jul 2016 13:47:50 +1000 - rev 330007
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1278439 - Adding a missing prefs service null check in startupcache/. r=froydnj.
d31ab2eab0a85b09b80f6726d847619ec2b9d846: Bug 1278439 - Adding a missing prefs service null check in chrome/. r=froydnj.
Nicholas Nethercote <nnethercote@mozilla.com> - Thu, 14 Jul 2016 13:47:49 +1000 - rev 330006
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1278439 - Adding a missing prefs service null check in chrome/. r=froydnj.
a8e5e8ecc28e1d7f7645652788709e07356a37ac: Bug 1278439 - Adding missing prefs service null checks in netwerk/. r=valentin.
Nicholas Nethercote <nnethercote@mozilla.com> - Thu, 14 Jul 2016 13:47:44 +1000 - rev 330005
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1278439 - Adding missing prefs service null checks in netwerk/. r=valentin.
8e3acbc708b62db2a091a587c40953e9ed41c786: Bug 1271714. Annotate expected asserts in layout/printing/crashtests/576878.xhtml. r=mstange
Timothy Nikkel <tnikkel@gmail.com> - Wed, 13 Jul 2016 01:08:17 -0500 - rev 330004
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1271714. Annotate expected asserts in layout/printing/crashtests/576878.xhtml. r=mstange The asserts are: ###!!! ASSERTION: Bounds computation mismatch: 'mContainerBounds.IsEqualInterior(mAccumulatedChildBounds)', /layout/base/FrameLayerBuilder.cpp, line 4887 ###!!! ASSERTION: bad aListVisibleBounds: 'r.GetBounds().IsEqualInterior(aListVisibleBounds)', /layout/base/nsDisplayList.cpp, line 1637 They happen because we have a wrap list item that contains an out of flow frame with no saved clip data. So the patch for this bug changes the scroll clip of the wrap list item from the scroll clip induced by the root scroll frame to the null scroll clip. All of the display items that the wrap list contains have the root scroll frame scroll clip, so this causes the scroll clipped bounds for the wrap list item to expand to the whole content area. These expanded bounds of the wrap list item get incorporated into the bounds of a parent transform item. Later the wrap list item is flattened away, and so it's no longer around to provide the expanded bounds, leading to the assertions. I've thought through options like changing how scroll clipped bounds work for wrap list items, but I can't seem to find any solution that would be consistent. The best thing would be to get the proper clip on out of flows we are going to descend into, but I can't think of a good way to do that either in this case (or in general).
2f8d5f889b47589b79a8ad95456f863c1b83cfb4: Bug 1282185 (part 2) - Fix an assertion failure in DMD. r=erahm.
Nicholas Nethercote <nnethercote@mozilla.com> - Wed, 13 Jul 2016 19:32:27 +1000 - rev 330003
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1282185 (part 2) - Fix an assertion failure in DMD. r=erahm.
d8e2cf1f7079f756f65654dca128245ddc3d4a6f: Bug 1282185 (part 1) - Remove a bogus assertion in DMD. r=erahm.
Nicholas Nethercote <nnethercote@mozilla.com> - Wed, 13 Jul 2016 18:10:56 +1000 - rev 330002
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1282185 (part 1) - Remove a bogus assertion in DMD. r=erahm. Since bug 1253512 landed, it's possible for DeadBlocks to lack an allocation stack.
bf190e326bfd7e7f944164d2ef2b577eaca12d87: Bug 790997. Align our tokenization of CSS bad-url-token with the CSS Syntax Level 3 CR. r=heycam,tromey
Boris Zbarsky <bzbarsky@mit.edu> - Wed, 13 Jul 2016 22:54:20 -0400 - rev 330001
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 790997. Align our tokenization of CSS bad-url-token with the CSS Syntax Level 3 CR. r=heycam,tromey The main change is that once we discover we have a bad-url-token we consume everything up to, but not including, the next ')' character. While we do this we can cross line boundaries and don't bother about matching braces or quotes. We just keep going until we find the ')' or hit EOF.
c3792b13e44350100962143db01c7ff6e15a7ee1: Bug 1271714. When creating the wrap list item that contains the display list for a frame make sure to use a scroll clip that includes content in the display list. r=mstange
Timothy Nikkel <tnikkel@gmail.com> - Wed, 13 Jul 2016 01:08:18 -0500 - rev 330000
Push 9858 by jlund@mozilla.com at Mon, 01 Aug 2016 14:37:10 +0000
Bug 1271714. When creating the wrap list item that contains the display list for a frame make sure to use a scroll clip that includes content in the display list. r=mstange In nsIFrame::BuildDisplayListForChild for certain types of frames we create wrap list items to wrap the constructed display list to make those items inseperable. We were using the current scroll clip by default when creating these items, but that scroll clip may not contain all the content in the display list if we traversed into an out of flow frame whose containing block is an ancestor of the current frame. The CurrentAncestorScrollClipForStackingContextContents keeps track of exactly this. (Its name might be a little misleading as we may not be dealing with a true stacking context here. Nevertheless it does contain the correct clip.) We also need to initialize the value of mStackingContextAncestorSC when we create an AutoSaveRestore because we are now using that value sometimes without calling Enter/ExitStackingContext (which initializes mStackingContextAncestorSC).
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip