c942aa1b5fe9ece9583fc4eeb5ef4599edf1b60f: removing support of @worker_setup draft
Hammad Akhtar <hammad13060@iiitd.ac.in> - Wed, 18 Jan 2017 16:55:53 +0530 - rev 465623
Push 42650 by hammad13060@iiitd.ac.in at Tue, 24 Jan 2017 14:08:57 +0000
removing support of @worker_setup MozReview-Commit-ID: BzyGOP3zcUn
7b33131fed2074be7897b277335f3aa8fa198ca5: Bug 1333397 - Rename WRGlyphInstance to WrGlyphInstance for naming consistency. r=gfx?
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 24 Jan 2017 08:44:23 -0500 - rev 465622
Push 42649 by kgupta@mozilla.com at Tue, 24 Jan 2017 13:58:14 +0000
Bug 1333397 - Rename WRGlyphInstance to WrGlyphInstance for naming consistency. r=gfx? MozReview-Commit-ID: K6Y5H7WOe87
b86ff4066687c7f880598820360b3c564b4f60d6: Merge m-c to graphics
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 24 Jan 2017 08:05:30 -0500 - rev 465621
Push 42649 by kgupta@mozilla.com at Tue, 24 Jan 2017 13:58:14 +0000
Merge m-c to graphics MozReview-Commit-ID: bxs3Qj28c5
6c0b2aee81443c80a0457f4c579a0b28408dd427: Bug 1333122 - Condition disabling of buffer-rotation on the layer tree rather than a compile-time flag. r=ethlin
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 24 Jan 2017 08:03:08 -0500 - rev 465620
Push 42649 by kgupta@mozilla.com at Tue, 24 Jan 2017 13:58:14 +0000
Bug 1333122 - Condition disabling of buffer-rotation on the layer tree rather than a compile-time flag. r=ethlin MozReview-Commit-ID: LJjRpcxxPsy
e9d5bf60fd9fdf56a5951a5b103d6d62763f3b44: Bug 1333122 - Remove gfxPrefs::WebRenderEnabled() to avoid it being used inappopriately; do WR and APZ decision-making during compositor creation. r=dvander?
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 24 Jan 2017 08:03:08 -0500 - rev 465619
Push 42649 by kgupta@mozilla.com at Tue, 24 Jan 2017 13:58:14 +0000
Bug 1333122 - Remove gfxPrefs::WebRenderEnabled() to avoid it being used inappopriately; do WR and APZ decision-making during compositor creation. r=dvander? MozReview-Commit-ID: Fkv6G35BcFw
e71e873893d92ae64e6d6d8e930658b4cb449715: Bug 1333122 - Start and stop the RenderThread in any webrender-enabled builds. r=nical
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 24 Jan 2017 08:03:08 -0500 - rev 465618
Push 42649 by kgupta@mozilla.com at Tue, 24 Jan 2017 13:58:14 +0000
Bug 1333122 - Start and stop the RenderThread in any webrender-enabled builds. r=nical MozReview-Commit-ID: BzjJbnl58xw
5facc8050cc13d3bb8c3208a7af288815203d2a9: Bug 1333122 - Remove some uses of gfxPrefs::WebRenderEnabled from gfx code. r=sotaro
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 24 Jan 2017 08:03:08 -0500 - rev 465617
Push 42649 by kgupta@mozilla.com at Tue, 24 Jan 2017 13:58:14 +0000
Bug 1333122 - Remove some uses of gfxPrefs::WebRenderEnabled from gfx code. r=sotaro MozReview-Commit-ID: FNiSGVC5B0e
b7619d5557e00c8ef4fc8e20f23172353d525a3a: Bug 1333122 - Use the CompositorOptions to determine the appropriate LayerManager to create for content-process tabs. r=dvander
Kartikaya Gupta <kgupta@mozilla.com> - Tue, 24 Jan 2017 08:03:08 -0500 - rev 465616
Push 42649 by kgupta@mozilla.com at Tue, 24 Jan 2017 13:58:14 +0000
Bug 1333122 - Use the CompositorOptions to determine the appropriate LayerManager to create for content-process tabs. r=dvander MozReview-Commit-ID: AhEpuPa2heV
f5f86abd40d7ff4b9e7afe260973c0d784813f02: Bug 1299117 - Measure time to first meaningful paint and report it to Telemetry. draft
Markus Stange <mstange@themasta.com> - Tue, 24 Jan 2017 14:48:04 +0100 - rev 465615
Push 42648 by bmo:mstange@themasta.com at Tue, 24 Jan 2017 13:48:46 +0000
Bug 1299117 - Measure time to first meaningful paint and report it to Telemetry. This implements the detection of the first "meaningful" paint as described in the definition in FirstMeaningfulPaintDetector.h. What's implemented here closely matches Chrome's code at https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/paint/FirstMeaningfulPaintDetector.cpp except for the following differences: - We don't check for "blank characters" (i.e. pending web fonts). - We compute "layout significance" per paint, and not per layout, using the page height at the time of the paint. Chrome respects the page height in each layout's significance computation individually. These differences are not intentional; I just haven't implemented the missing pieces yet. This patch does not add any profiler markers. The value reported via telemetry is the time between non-blank paint and first meaningful paint, in milliseconds. MozReview-Commit-ID: GJyeCesguvy
9a07e391cfdbb6c6d8a8f113cccec98cdc1e0dc0: Bug 1268020 - Implement "main_menu" context draft
Tomislav Jovanovic <tomica@gmail.com> - Sun, 22 Jan 2017 19:05:30 +0100 - rev 465614
Push 42647 by bmo:tomica@gmail.com at Tue, 24 Jan 2017 13:47:15 +0000
Bug 1268020 - Implement "main_menu" context MozReview-Commit-ID: JRJSIYDR0JM
17e5a052898c9a45949f5b645010f859bacbe3e5: Bug 1300588 - Implements the devtools.network.onNavigated API event, r?kmag draft
Bob Silverberg <bsilverberg@mozilla.com> - Fri, 20 Jan 2017 14:50:20 -0500 - rev 465613
Push 42646 by bmo:bob.silverberg@gmail.com at Tue, 24 Jan 2017 13:45:42 +0000
Bug 1300588 - Implements the devtools.network.onNavigated API event, r?kmag MozReview-Commit-ID: 3P2KTzuzbWn
09e828967188990ecc6c9adf6e1d86c73b993a56: Bug 1322277 - Default socket timeout has to be larger than the default page load timeout. draft
Henrik Skupin <mail@hskupin.info> - Tue, 24 Jan 2017 14:17:19 +0100 - rev 465612
Push 42645 by bmo:hskupin@gmail.com at Tue, 24 Jan 2017 13:21:35 +0000
Bug 1322277 - Default socket timeout has to be larger than the default page load timeout. To not run into socket failures and forced application shutdown scenarios, the socket timeout should always be larger then the page load timeout. MozReview-Commit-ID: EOBW4mozDT1
50fac8ef53fa4de60150d79e5d2feac433370948: Bug 1322277 - Marionette client should be able to set default capabilities. draft
Henrik Skupin <mail@hskupin.info> - Tue, 24 Jan 2017 13:50:07 +0100 - rev 465611
Push 42645 by bmo:hskupin@gmail.com at Tue, 24 Jan 2017 13:21:35 +0000
Bug 1322277 - Marionette client should be able to set default capabilities. Some default values for capabilities as defined by the Webdriver spec do not match the expectations for Marionette client. Therefore we should add the possibility to override those defaults in start_session(), but also still allow consumers to set their own values. MozReview-Commit-ID: CTUycCRV5kg
e1557c413b709dcc39bd3ef40a670493f4a45be8: Bug 1322277 - Fix usage of capabilities in start_session draft
Henrik Skupin <mail@hskupin.info> - Mon, 23 Jan 2017 20:35:15 +0100 - rev 465610
Push 42645 by bmo:hskupin@gmail.com at Tue, 24 Jan 2017 13:21:35 +0000
Bug 1322277 - Fix usage of capabilities in start_session Capabilities as passed into start_session() can be desiredCapabilities and requiredCapabilities. As such the parameter name should be clear. MozReview-Commit-ID: GPNv4g9HMO2
73f15ec0f440287d1c2be25c7c4b0efe4eb6143f: Bug 1322277 - Default socket timeout has to be larger than the default page load timeout. draft
Henrik Skupin <mail@hskupin.info> - Tue, 24 Jan 2017 14:17:19 +0100 - rev 465609
Push 42644 by bmo:hskupin@gmail.com at Tue, 24 Jan 2017 13:18:10 +0000
Bug 1322277 - Default socket timeout has to be larger than the default page load timeout. To not run into socket failures and forced application shutdown scenarios, the socket timeout should always be larger then the page load timeout. MozReview-Commit-ID: EOBW4mozDT1
1a907d012f556617139c1d2736e238569524b555: Bug 1322277 - Marionette client should be able to set default capabilities. draft
Henrik Skupin <mail@hskupin.info> - Tue, 24 Jan 2017 13:50:07 +0100 - rev 465608
Push 42644 by bmo:hskupin@gmail.com at Tue, 24 Jan 2017 13:18:10 +0000
Bug 1322277 - Marionette client should be able to set default capabilities. Some default values for capabilities as defined by the Webdriver spec do not match the expectations for Marionette client. Therefore we should add the possibility to override those defaults in start_session(), but also still allow consumers to set their own values. MozReview-Commit-ID: CTUycCRV5kg
cf21497a86e0a5b5211525a7f6e5f4e34b3b90b9: Bug 1322277 - Fix usage of capabilities in start_session draft
Henrik Skupin <mail@hskupin.info> - Mon, 23 Jan 2017 20:35:15 +0100 - rev 465607
Push 42644 by bmo:hskupin@gmail.com at Tue, 24 Jan 2017 13:18:10 +0000
Bug 1322277 - Fix usage of capabilities in start_session MozReview-Commit-ID: GPNv4g9HMO2
f33d597a4e0aa227f83115d5e69e9f1fff6b0445: Bug 1319987: P5. WIP. f?gerald draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Mon, 23 Jan 2017 23:09:15 +0100 - rev 465606
Push 42643 by bmo:jyavenard@mozilla.com at Tue, 24 Jan 2017 13:14:41 +0000
Bug 1319987: P5. WIP. f?gerald MozReview-Commit-ID: DpiZucGofJT
ad19ea965f25ece807c23055438c970963703f68: Bug 1307906 - add newline and spaces in console msg for clipboard;r=nchevobbe draft
Julian Descottes <jdescottes@mozilla.com> - Mon, 23 Jan 2017 19:41:44 +0100 - rev 465605
Push 42642 by jdescottes@mozilla.com at Tue, 24 Jan 2017 13:02:34 +0000
Bug 1307906 - add newline and spaces in console msg for clipboard;r=nchevobbe MozReview-Commit-ID: 51djydkJx4R
7f0a07b1aa73d4c6e53dfcff57ce9b1666cb1c36: Bug 1299117 - Measure time to first meaningful paint and report it to Telemetry. draft
Markus Stange <mstange@themasta.com> - Tue, 24 Jan 2017 13:41:09 +0100 - rev 465604
Push 42641 by bmo:mstange@themasta.com at Tue, 24 Jan 2017 12:50:04 +0000
Bug 1299117 - Measure time to first meaningful paint and report it to Telemetry. This implements the detection of the first "meaningful" paint as described in the definition in FirstMeaningfulPaintDetector.h. What's implemented here closely matches Chrome's code at https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/paint/FirstMeaningfulPaintDetector.cpp except for the following differences: - We don't check for "blank characters" (i.e. pending web fonts). - We compute "layout significance" per paint, and not per layout, using the page height at the time of the paint. Chrome respects the page height in each layout's significance computation individually. These differences are not intentional; I just haven't implemented the missing pieces yet. This patch does not add any profiler markers. The value reported via telemetry is the time between non-blank paint and first meaningful paint, in milliseconds. MozReview-Commit-ID: GJyeCesguvy
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip