Backed out changeset b15136f926ca (bug 1272778) for build bustage

Bug 1272778. Use IntRects for clip rects instead of Rects. r=mstange Previously, we took an IntRect converted to Rect and then later wanted ints in the backend. This avoids all of that.

Bug 1272840 - Resurrect the URL to block-and-line.html DONTBUILD (NPOTB) MozReview-Commit-ID: Hqk3kSUftRM

Bug 1272831 - Add AutoRestore::Value() to retrieve the saved value. MozReview-Commit-ID: eZCWmTpvXi

Merge inbound to central, a=merge

Bug 1181055 - video play button does not work if the VIDEO element has onclick handler calling play(). r?gijs MozReview-Commit-ID: c6V9LMIdK0

Bug 1181055 - video play button does not work if the VIDEO element has onclick handler calling play(). r?gijs MozReview-Commit-ID: c6V9LMIdK0

Bug 1272817 - Return early if file is empty + regression test. r=sebastian MozReview-Commit-ID: FPdDr2t1wEy

Bug 1269398: Add visitType, visitId, and fromVisitId fields to history visit query results. r?mak MozReview-Commit-ID: BCsztVsCH98

amend-subprocess MozReview-Commit-ID: KFfQJ6SnLnw

Bug 687787 - Support focusin/focusout events r=smaug Add support for focusin and focusout in DOM. The event sequence is either: (for focuses) - focusin - focus or (for refocuses) - focusout - focusin - blur - focus (for unfocuses) - focusout - blur Additionally, add the necessary attributes to ensure only one focus occurs as the result of a series of events. Also ensure that focusout doesn't recurse if focus() is called in an event callback. Include mochitest. MozReview-Commit-ID: LGPPEC3WH55

Bug 1272768 - Teach `mach resource-usage` to load arbitrary URLs; r?chmanchester Firefox automation now uploads resource usage JSON files as job artifacts (see bug 1272202). Now that the build system writes the same data format and `mach resource-usage` can read this data format, let's teach `mach resource-usage` to load arbitrary URLs. This allows people to view system resource usage for arbitrary jobs in automation. Currently, you have to look at Treeherder to find the URL to the build-resources.json artifact. Perhaps in the future we can make finding the URL easier. Or we could integrate source resource viewing into Treeherder itself (this is probably preferred). This commit continues the tradition of `mach resource-usage` being a hacked up mess. Instead of loading the URL in the browser, we download the URL from Python then serve it from the HTTP server running as part of `mach resource-usage`. This is somewhat horrible. But it was easiest to implement. It also conveniently bypasses any cross origin request restrictions the browser may impose. So it is useful. MozReview-Commit-ID: IR1Cfs7SrRN

Bug 1272768 - Use mozsystemmonitor for writing JSON; r?chmanchester We currently have our own system monitor serialization in building.py. It predates as_dict() from mozsystemmonitor. Let's use the "upstream" data format so we only have a single format to consume. This change required updating the in-tree resource viewer to be compatible with the new data format. This commit stops short of getting rid of the existing data massaging code in building.py. Another day perhaps. MozReview-Commit-ID: 1OJrSiyJjMX

Bug 1211723 follow up - Explicitly delete implicitly deleted copy constructors for VS2013; r=Waldo

Backed out changeset 2ac62de7365d (bug 1271002) for crash in GTest: [@ mozilla::image::RasterImage::UpdateImageContainer]. r=backout

Bug 1272782 - Use mozsystemmonitor 0.3 in mozharness; r=catlee MozReview-Commit-ID: 6XxWnWGkiZn

Bug 1272782 - Bump mozsystemmonitor version to 0.3; r=ahal So we can release the bug fixes we just made. MozReview-Commit-ID: HgfPQkkwd6r

Bug 1272782 - Don't wait forever for child process to exit; r=ahal I believe this is the source of hangs/timeouts in automation. join() waits forever. We add code to wait at most N seconds before force terminating the process. The timeout is a bit high. But it is better than infinite. MozReview-Commit-ID: KwyO4RZ9OqL

Bug 1272782 - Wait longer and stop after "done" message; r=ahal Before, we kept waiting for data in the pipe after receiving the "done" message. This didn't really make much sense because the "done" message should be the final thing sent over the pipe! e9113fd6cdb8 (bug 1239939) recently dropped the poll interval of the pipe from 1.0 to 0.1s. This appears to have introduced an intermittent failure in a test. The race condition was between the child process sending data and the parent process timing out (after only 0.1s) waiting for that data. Increasing the timeout makes the failure reproduce less often. Although technically the race condition is still present! I'm not inclined to fix it at this time, however. The rationale for dropping the pipe timeout was that it was causing lag when terminating short-lived processes. Now that we abort the pipe reading/polling loop as soon as the "done" message is received, we no longer poll the pipe after receiving "done" and no longer have to worry about its timeout impacting shutdown time. MozReview-Commit-ID: EeENQ95RAs1

Bug 1272782 - Send tuple properly; r=ahal Found this bug when auditing the code for issues. We are attempting to send a tuple but were forgetting the trailing comma on a single element tuple. Fortunately, this doesn't appear to impact anything because the receiving end of the pipe doesn't care what data it receives. MozReview-Commit-ID: E34fBqxgUSq