6ae7f5b4e31cd4dc64edb9fc42f1f7defb8f82d0: Bug 1294171 - Part 2. Create a reftest. draft
cku <cku@mozilla.com> - Thu, 18 Aug 2016 12:14:19 +0800 - rev 402399
Push 26630 by bmo:cku@mozilla.com at Thu, 18 Aug 2016 04:20:52 +0000
Bug 1294171 - Part 2. Create a reftest. MozReview-Commit-ID: IcXmbVd9nUA
fcec3bfd61b6dc9438f5a4e7b736e118bd1f7574: Bug 1294171 - Part 1. Treat unresolvable mask as no mask before suppport image mask. draft
cku <cku@mozilla.com> - Thu, 18 Aug 2016 11:24:28 +0800 - rev 402398
Push 26630 by bmo:cku@mozilla.com at Thu, 18 Aug 2016 04:20:52 +0000
Bug 1294171 - Part 1. Treat unresolvable mask as no mask before suppport image mask. MozReview-Commit-ID: 9f2k7NtpYuR
cb16d527b3d25f24672aaea68db815dbae219d18: Bug 1294171 - Part 2. Create a reftest. draft
cku <cku@mozilla.com> - Thu, 18 Aug 2016 12:14:19 +0800 - rev 402397
Push 26629 by bmo:cku@mozilla.com at Thu, 18 Aug 2016 04:17:23 +0000
Bug 1294171 - Part 2. Create a reftest. MozReview-Commit-ID: IcXmbVd9nUA
bc899471411dba7a75469fd564339d0cb301d784: Bug 1294171 - Part 1. Treat unresolvable mask as no mask before turning on image mask mask support. draft
cku <cku@mozilla.com> - Thu, 18 Aug 2016 11:24:28 +0800 - rev 402396
Push 26629 by bmo:cku@mozilla.com at Thu, 18 Aug 2016 04:17:23 +0000
Bug 1294171 - Part 1. Treat unresolvable mask as no mask before turning on image mask mask support. MozReview-Commit-ID: 9f2k7NtpYuR
572fcb07bcb4ee10c950a18f73c4e2f5b7ce7498: Bug 1294171 - Part 2. Create a reftest. draft
cku <cku@mozilla.com> - Thu, 18 Aug 2016 12:14:19 +0800 - rev 402395
Push 26628 by bmo:cku@mozilla.com at Thu, 18 Aug 2016 04:15:25 +0000
Bug 1294171 - Part 2. Create a reftest. MozReview-Commit-ID: IcXmbVd9nUA
e5e8c41c4bfd04c41c79e02614f45da387a3722b: Bug 1295390 - Don't hold search result after clearing inspector-searchbox by inspector-searchinput-clear. r=ntim draft
Steve Chung <schung@mozilla.com> - Tue, 16 Aug 2016 18:18:48 +0800 - rev 402394
Push 26627 by schung@mozilla.com at Thu, 18 Aug 2016 04:08:33 +0000
Bug 1295390 - Don't hold search result after clearing inspector-searchbox by inspector-searchinput-clear. r=ntim MozReview-Commit-ID: xmLhuQBgaV
466167dd95e44def9fbc0f8c96068ef7fbaa3f82: Remove unused ExtensionContext and GlobalManager globals draft
Rob Wu <rob@robwu.nl> - Tue, 16 Aug 2016 22:05:05 -0700 - rev 402393
Push 26626 by bmo:rob@robwu.nl at Thu, 18 Aug 2016 04:04:28 +0000
Remove unused ExtensionContext and GlobalManager globals The presence of these globals interfere with the attempt to get ext-*.js scripts to load in a content process because these globals are only available in the main process. MozReview-Commit-ID: 7syjAGcuUnu
8fe04a3c5dcb21b2175414aa2661b705582be56c: Bug 1286712 - Validate runtime.sendMessage parameters draft
Rob Wu <rob@robwu.nl> - Tue, 16 Aug 2016 21:36:42 -0700 - rev 402392
Push 26626 by bmo:rob@robwu.nl at Thu, 18 Aug 2016 04:04:28 +0000
Bug 1286712 - Validate runtime.sendMessage parameters The main motive for this patch is to remove the use of the GlobalManager global (which was used to see if an extension ID is valid, which was specifically added in order to create thebrowser_ext_lastError.js test). To preserve test coverage I implemented a full validation of the runtime.sendMessage method. Now the error for a non-existent extension is identical in both the content script and background pages. Note that this also fixes a minor privacy leak: Previously extensions could see whether another extension is installed by sending a message to the specified extension and using the different responses to see whether another extension is installed. MozReview-Commit-ID: 82R97Ei25Xr
31c1ea21cf64d2c6bcca7d153b483b28e36bb97b: Bug 1295473 - Fix return type of {tabs,runtime}.sendMessage draft
Rob Wu <rob@robwu.nl> - Mon, 15 Aug 2016 23:53:24 -0700 - rev 402391
Push 26626 by bmo:rob@robwu.nl at Thu, 18 Aug 2016 04:04:28 +0000
Bug 1295473 - Fix return type of {tabs,runtime}.sendMessage The tabs.sendMessage and runtime.sendMessage implementations behave like an async function: They take a callback parameter and return a promise. So they should be handled by |callAsyncFunction|, not |callFunctionNoReturn|. This fixes the issue for background pages, but not for content scripts because sendMessage is not implemented as a schema at the moment. This will also be fixed once content script APIs are generated via Schemas. MozReview-Commit-ID: 9p1hvOP0KSm
42474458e508a875531399ceffb5445ac3396096: Bug 1295853 - Only enable Widevine on whitelisted Tier-1 build targets. r?glandium draft
Chris Pearce <cpearce@mozilla.com> - Wed, 17 Aug 2016 21:40:43 +1200 - rev 402390
Push 26625 by cpearce@mozilla.com at Thu, 18 Aug 2016 03:57:37 +0000
Bug 1295853 - Only enable Widevine on whitelisted Tier-1 build targets. r?glandium MozReview-Commit-ID: 52lrV3aEEVe
e6ecb961ff60061d56f89b11a47201e911e62d35: Bug 1258127 - Sync bookmark engine updates to support tracking changes in Places. draft
Kit Cambridge <kcambridge@mozilla.com> - Tue, 16 Aug 2016 18:21:19 -0700 - rev 402389
Push 26624 by bmo:kcambridge@mozilla.com at Thu, 18 Aug 2016 03:56:29 +0000
Bug 1258127 - Sync bookmark engine updates to support tracking changes in Places. MozReview-Commit-ID: 4YESuxP2rRf
179777db83e07ce29fa9fc20f395fa3d048253e5: Bug 1258127 - Track bookmark sync changes in Places. draft
Kit Cambridge <kcambridge@mozilla.com> - Wed, 17 Aug 2016 20:53:36 -0700 - rev 402388
Push 26624 by bmo:kcambridge@mozilla.com at Thu, 18 Aug 2016 03:56:29 +0000
Bug 1258127 - Track bookmark sync changes in Places. MozReview-Commit-ID: JsCRwnmgw09
81a353f89e7679b228958c24b7edc85473daba56: Bug 1295082 - Minor fixups for experimental WebExtensions APIs draft
Rob Wu <rob@robwu.nl> - Tue, 16 Aug 2016 14:31:28 -0700 - rev 402387
Push 26623 by bmo:rob@robwu.nl at Thu, 18 Aug 2016 03:54:13 +0000
Bug 1295082 - Minor fixups for experimental WebExtensions APIs - Remove unused registerAPI and registerPrivilegedAPI - Generate the APIs just once. - Fix typo in addon ID. MozReview-Commit-ID: rdiiIxHMsm
e2baa3c4b9bb46e54251c67c8b249f108b072776: Bug 1295082 - BaseContext.extensionId -> BaseContext.extension.id draft
Rob Wu <rob@robwu.nl> - Tue, 16 Aug 2016 14:29:52 -0700 - rev 402386
Push 26623 by bmo:rob@robwu.nl at Thu, 18 Aug 2016 03:54:13 +0000
Bug 1295082 - BaseContext.extensionId -> BaseContext.extension.id MozReview-Commit-ID: 2tFVUwjyJQu
3168ab980d799c83582242942dd7f2ede3efa0e5: Bug 1295082 - Put Extension in BaseContext draft
Rob Wu <rob@robwu.nl> - Mon, 15 Aug 2016 01:04:58 -0700 - rev 402385
Push 26623 by bmo:rob@robwu.nl at Thu, 18 Aug 2016 03:54:13 +0000
Bug 1295082 - Put Extension in BaseContext ExtensionContext in Extension.jsm has |extension| as an instance member, so use it instead of passing |extension| to registerSchemaAPI's callback. And to make sure that this pattern also works in content processes, move the |extension| member to BaseContext. MozReview-Commit-ID: BgsGGCPQxJR
1a1747854d1bc68a43700328d716b5f4f6b202f7: Bug 1295852 - Part 5: Check for generated content containers more precisely in nsTransitionManager assertion. r?boris draft
Cameron McCormack <cam@mcc.id.au> - Thu, 18 Aug 2016 11:27:55 +0800 - rev 402384
Push 26622 by bmo:cam@mcc.id.au at Thu, 18 Aug 2016 03:28:48 +0000
Bug 1295852 - Part 5: Check for generated content containers more precisely in nsTransitionManager assertion. r?boris MozReview-Commit-ID: Gbu7cH003Jr
82ef8f0966d65736b11f52e1bafe5ff01efcceab: Bug 1295852 - Part 4: Check for generated content containers more precisely when reflowing grid containers. r?mats draft
Cameron McCormack <cam@mcc.id.au> - Thu, 18 Aug 2016 11:27:53 +0800 - rev 402383
Push 26622 by bmo:cam@mcc.id.au at Thu, 18 Aug 2016 03:28:48 +0000
Bug 1295852 - Part 4: Check for generated content containers more precisely when reflowing grid containers. r?mats I'm not convinced that we can actually get regular content <_moz_generated_content_before> elements in here, since it's only if CompareTreePosition returned 0 that we look at the element name, but might be best to make this test stronger in any case. MozReview-Commit-ID: 8CgxcU9AbDA
df4003625b2a8e1a95ed0dcde5c627760f0bbf08: Bug 1295852 - Part 3: Check for generated content containers correctly when generating DOM ranges from a11y selections. r?masayuki draft
Cameron McCormack <cam@mcc.id.au> - Thu, 18 Aug 2016 11:25:44 +0800 - rev 402382
Push 26622 by bmo:cam@mcc.id.au at Thu, 18 Aug 2016 03:28:48 +0000
Bug 1295852 - Part 3: Check for generated content containers correctly when generating DOM ranges from a11y selections. r?masayuki MozReview-Commit-ID: 7Ng1fGWyE4d
54fdde457c46236d399a2a319c9ba1697114a58b: Bug 1295852 - Part 2: Check for generated content containers correctly in Element.getAnimations(). r?boris draft
Cameron McCormack <cam@mcc.id.au> - Thu, 18 Aug 2016 11:24:36 +0800 - rev 402381
Push 26622 by bmo:cam@mcc.id.au at Thu, 18 Aug 2016 03:28:48 +0000
Bug 1295852 - Part 2: Check for generated content containers correctly in Element.getAnimations(). r?boris MozReview-Commit-ID: E6HkQED2ND8
efa4e312e434f644fe0b075687269777149bc6f6: Bug 1295852 - Part 1: Add nsINode methods for testing whether a node is a ::before/::after generated content container. r?bholley draft
Cameron McCormack <cam@mcc.id.au> - Thu, 18 Aug 2016 11:24:32 +0800 - rev 402380
Push 26622 by bmo:cam@mcc.id.au at Thu, 18 Aug 2016 03:28:48 +0000
Bug 1295852 - Part 1: Add nsINode methods for testing whether a node is a ::before/::after generated content container. r?bholley MozReview-Commit-ID: EyALIQYzQW
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip