9d792e9c09c0fe2480b24dc22db0764f35621e9f: Bug 1433144 - Update metadata for wpt update, a=testonly
James Graham <james@hoppipolla.co.uk> - Tue, 23 Jan 2018 16:15:55 +0000 - rev 400946
Push 99261 by james@hoppipolla.co.uk at Fri, 26 Jan 2018 11:54:59 +0000
Bug 1433144 - Update metadata for wpt update, a=testonly MozReview-Commit-ID: 7ILmVq1bNRj
b6fab3e4a40817de4acb9b86d2ff7c6ca7efe080: Bug 1433144 - Update web-platform-tests to revision 2e19bfdaee6edb2c1069c07e14037284167284a3, a=testonly
James Graham <james@hoppipolla.co.uk> - Tue, 23 Jan 2018 16:14:20 +0000 - rev 400945
Push 99261 by james@hoppipolla.co.uk at Fri, 26 Jan 2018 11:54:59 +0000
Bug 1433144 - Update web-platform-tests to revision 2e19bfdaee6edb2c1069c07e14037284167284a3, a=testonly MozReview-Commit-ID: 13sFeYHTYGC
933304b9909eaae1eb75a43dd8ea00babcc82ebe: Bug 1432751 - Building with system cairo is no longer supported; make --enable-system-cairo a configure-time error. r=jrmuizel
Jonathan Kew <jkew@mozilla.com> - Fri, 26 Jan 2018 11:08:57 +0000 - rev 400944
Push 99260 by jkew@mozilla.com at Fri, 26 Jan 2018 11:09:17 +0000
Bug 1432751 - Building with system cairo is no longer supported; make --enable-system-cairo a configure-time error. r=jrmuizel
dd66a66c6a94c13a6abf4433d93c60857a29a0a1: Bug 1357788 - Removal of Netscape 4.x Registry reading block from Windows MIME/extension mapping, r=gijs
Ashish <supersonic12910@gmail.com> - Fri, 26 Jan 2018 08:37:16 +0530 - rev 400943
Push 99259 by btara@mozilla.com at Fri, 26 Jan 2018 10:56:26 +0000
Bug 1357788 - Removal of Netscape 4.x Registry reading block from Windows MIME/extension mapping, r=gijs
a473f17fabfea107c5e8f2eb0d30bbe4a6314898: Bug 1433100 - Constify the parameter of HTMLEditor::DoInlineTableEditingAction. r=m_kato
Masatoshi Kimura <VYV03354@nifty.ne.jp> - Thu, 25 Jan 2018 22:16:32 +0900 - rev 400942
Push 99258 by VYV03354@nifty.ne.jp at Fri, 26 Jan 2018 10:32:06 +0000
Bug 1433100 - Constify the parameter of HTMLEditor::DoInlineTableEditingAction. r=m_kato
8c6056b6493042decf2b16486db4dc4c9276b6b7: Merge mozilla-central to mozilla-inbound. a=merge CLOSED TREE
Ciure Andrei <aciure@mozilla.com> - Fri, 26 Jan 2018 12:12:08 +0200 - rev 400941
Push 99257 by aciure@mozilla.com at Fri, 26 Jan 2018 10:12:49 +0000
Merge mozilla-central to mozilla-inbound. a=merge CLOSED TREE
329bfa4b804a69d67cd0018d70bbf4cc970f4a64: Merge inbound to mozilla-central. a=merge
Ciure Andrei <aciure@mozilla.com> - Fri, 26 Jan 2018 12:04:07 +0200 - rev 400940
Push 99257 by aciure@mozilla.com at Fri, 26 Jan 2018 10:12:49 +0000
Merge inbound to mozilla-central. a=merge
2979bdbbc13bfdc89d0e83c04920bac46b2546e6: Merge autoland to mozilla-central. a=merge
Ciure Andrei <aciure@mozilla.com> - Fri, 26 Jan 2018 12:02:33 +0200 - rev 400939
Push 99257 by aciure@mozilla.com at Fri, 26 Jan 2018 10:12:49 +0000
Merge autoland to mozilla-central. a=merge
5058e3e4798eea793e935857eb84a8af0cd8487a: Bug 1426831: don't overwrite MaxMessageSize with default values. r=lennart.grahl+594092
Nils Ohlmeier [:drno] <drno@ohlmeier.org> - Tue, 09 Jan 2018 17:30:19 -0800 - rev 400938
Push 99257 by aciure@mozilla.com at Fri, 26 Jan 2018 10:12:49 +0000
Bug 1426831: don't overwrite MaxMessageSize with default values. r=lennart.grahl+594092 MozReview-Commit-ID: CiqoGUYbPR2
897cb1885507f170858c753d7d92f6d17099a18e: Bug 1430628 - TextInputHandler::HandleCommand() should use native key event when it dispatches a keypress event either initializing with native event or creating fake event r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 24 Jan 2018 19:13:01 +0900 - rev 400937
Push 99257 by aciure@mozilla.com at Fri, 26 Jan 2018 10:12:49 +0000
Bug 1430628 - TextInputHandler::HandleCommand() should use native key event when it dispatches a keypress event either initializing with native event or creating fake event r=m_kato TextInputHandler::HandleCommand() has two bugs. One is, checking whether the key event has caused composition events. Even if it caused composition events, we decided to dispatch keypress event for emulating native behavior. Therefore, this patch removes the check of |currentKeyEvent->CanDispatchKeyPress()|. The other is, for making content handle dispatching keypress event as given command, it needs to dispatch a keypress event whose key combination will cause the command. However, HandleCommand() needs to set native key event since content may not refer key combination for some edit actions, they just refer command which is computed with native key event with NativeKeyBindings. Therefore, even if current native key event has already caused dispatching some events, HandleCommand() needs to set WidgetKeyboardEvent::mNativeKeyEvent to current native key event for NativeKeyBindings. Although it must be rare case, given key could be not related to the command or not key could cause the command. In this case, and perhaps in all cases, we should set all commands of dispatching keypress event before dispatching it. Howevever, this needs more work, so, we shouldn't do it in this bug to making it possible to uplift. Therefore, this patch makes always set mNativeKeyEvent to current native key event. So, just warning it when command is caused without native key event. MozReview-Commit-ID: 2MvDTw4ruAu
35a54155e9662ba7567088769adf592710810197: Bug 1428234 Part 2: Force extensions database rebuild r=kmag
Andrew Swan <aswan@mozilla.com> - Tue, 23 Jan 2018 21:11:38 -0800 - rev 400936
Push 99257 by aciure@mozilla.com at Fri, 26 Jan 2018 10:12:49 +0000
Bug 1428234 Part 2: Force extensions database rebuild r=kmag Prior to the first patch for this bug, users with non-ascii characters in the path to their profile directory got bad data in extensions.json. With that bug fixed, now force a rebuild to rescue those users. MozReview-Commit-ID: F3l87A67Ojc
993f338d5088a1109f85a26c93b1fb4002fc04ec: Bug 1428234 Part 1: Remove incorrect uses of persistentDescriptor in AddonManager r=emk,kmag
Andrew Swan <aswan@mozilla.com> - Mon, 22 Jan 2018 21:52:28 -0800 - rev 400935
Push 99257 by aciure@mozilla.com at Fri, 26 Jan 2018 10:12:49 +0000
Bug 1428234 Part 1: Remove incorrect uses of persistentDescriptor in AddonManager r=emk,kmag MozReview-Commit-ID: 3pyF58rQcoa
8f375ca322a95e686039ee674edf2898c174da75: Bug 1407557 - Add crash pings to Fennec; r=jchen
Gabriele Svelto <gsvelto@mozilla.com> - Thu, 07 Dec 2017 11:40:44 +0100 - rev 400934
Push 99256 by gsvelto@mozilla.com at Fri, 26 Jan 2018 09:45:16 +0000
Bug 1407557 - Add crash pings to Fennec; r=jchen Besides adding a new ping builder for 'crash' type pings this patch modifies part of the Java telemetry to accomodate for it: a new store has been added for holding crash pings and the URL used to submit has been updated to pass the 'v' parameter (crash pings are in the telemetry version 4 format). MozReview-Commit-ID: CZzw7xv6YoS
f8b2a629a26fc83a05683c77a0a72bb4a924850d: Bug 1417358. Make sure that the override dirty rect that we set when a displayport changes gets cleared even if we don't perform a partial display list update. r=mattwoodrow
Timothy Nikkel <tnikkel@gmail.com> - Thu, 25 Jan 2018 23:42:44 -0600 - rev 400933
Push 99255 by tnikkel@gmail.com at Fri, 26 Jan 2018 05:44:28 +0000
Bug 1417358. Make sure that the override dirty rect that we set when a displayport changes gets cleared even if we don't perform a partial display list update. r=mattwoodrow We do this by tracking them as a property on the root frame the same way we do for modified frames. We also set the property in ProcessFrame but that is okay because we are guaranteed to finish the partial update at that point.
7b27e53e1b97c052a82ef29fb2d7f3928b4417c9: Merge mozilla-central to mozilla-inbound r=merge
Dorel Luca <dluca@mozilla.com> - Fri, 26 Jan 2018 05:50:11 +0200 - rev 400932
Push 99254 by dluca@mozilla.com at Fri, 26 Jan 2018 03:51:01 +0000
Merge mozilla-central to mozilla-inbound r=merge
723b25eb3dd83d0bb1ea846814e9d7e1bdc78e1b: Backed out changeset e00fb451089f (bug 1432763) for breaking nightly partial update generation a=backout
Dorel Luca <dluca@mozilla.com> - Fri, 26 Jan 2018 03:53:42 +0200 - rev 400931
Push 99254 by dluca@mozilla.com at Fri, 26 Jan 2018 03:51:01 +0000
Backed out changeset e00fb451089f (bug 1432763) for breaking nightly partial update generation a=backout
bf540cb73978747eb72a5cc7088c9beed75f1205: Backed out changeset 804f26b2c6b8 (bug 1428698) for xpcshell failure on toolkit/mozapps/extensions/test/xpcshell/test_bug397778.js on a CLOSED TREE
Dorel Luca <dluca@mozilla.com> - Fri, 26 Jan 2018 03:43:51 +0200 - rev 400930
Push 99254 by dluca@mozilla.com at Fri, 26 Jan 2018 03:51:01 +0000
Backed out changeset 804f26b2c6b8 (bug 1428698) for xpcshell failure on toolkit/mozapps/extensions/test/xpcshell/test_bug397778.js on a CLOSED TREE
4b04997348874684161a8caec0c3954018eb6302: Bug 1432390 - Allow to derive docker images from other in-tree images. r=dustin
Mike Hommey <mh+mozilla@glandium.org> - Thu, 25 Jan 2018 11:07:54 +0900 - rev 400929
Push 99254 by dluca@mozilla.com at Fri, 26 Jan 2018 03:51:01 +0000
Bug 1432390 - Allow to derive docker images from other in-tree images. r=dustin So far, the best we've been able to do is to upload an image to the docker hub, and point an image's Dockerfile's FROM to the version uploaded onto the hub. That is a cumbersome process, and makes the use of "layered" docker images painful. This change allows to declare a parent docker image in the taskcluster/ci/docker-image/kind.yml definitions, which will be automatically loaded before building the image. The Dockerfile can then reference the image, using the DOCKER_IMAGE_PARENT argument, which will contain the full image name:tag. Some details are left off, for now, such as VOLUMEs. At this point, VOLUMEs should all be defined in leaf docker images.
1316aa94e6bc580cc0e49012722dad2ef12ab6e0: Bug 1432390 - Make `mach taskcluster-build-image` talk directly to the docker socket in the image builder. r=dustin
Mike Hommey <mh+mozilla@glandium.org> - Thu, 25 Jan 2018 13:36:47 +0900 - rev 400928
Push 99254 by dluca@mozilla.com at Fri, 26 Jan 2018 03:51:01 +0000
Bug 1432390 - Make `mach taskcluster-build-image` talk directly to the docker socket in the image builder. r=dustin Now that `mach taskcluster-build-image` can, we can avoid all the manual handling based on curl and jq in the image builder. An additional advantage on relying on `mach taskcluster-build-image` doing more is that less changes to the build-image.sh script will be necessary, and thus less updates of the image builder docker image.
3543eaf9b9c439da00629805aa5fe081823fa488: Bug 1432390 - Directly call the docker API over its unix socket instead of calling `docker build`. r=dustin
Mike Hommey <mh+mozilla@glandium.org> - Wed, 24 Jan 2018 15:55:31 +0900 - rev 400927
Push 99254 by dluca@mozilla.com at Fri, 26 Jan 2018 03:51:01 +0000
Bug 1432390 - Directly call the docker API over its unix socket instead of calling `docker build`. r=dustin This allows to avoid writing out a tar file to then extract it to feed it to `docker build`. This is essentially what the image-builder docker image does, except it uses a temporary file for the tar.
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip