corysanin/tubestation
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
535,524 Commits 1 Branch 0 Tags
fea80dfb51a70ceb871386c7aab9fb396e4f255e
Commit Graph

35 Commits

Author SHA1 Message Date
Boris Zbarsky
7fa3838d4d Bug 1452185 part 2. Remove nsIDOMXULElement use in JS. r=qdot 
MozReview-Commit-ID: 2JIybnXaudR
 2018-04-09 16:30:32 -04:00
Christoph Kerschbaumer
07965896e9 Bug 1439713 - Add flag to loadinfo for skipping certain security policy checks. r=bz 2018-03-29 11:14:35 +02:00
Christoph Kerschbaumer
56529d1f61 Bug 1439713 - Change nsIContentPolicy shouldLoad to take an <uri, loadInfo> pair instead of the various args. r=bz 2018-03-29 12:16:23 +02:00
Andrew McCreight
272cee1e65 Bug 1432992, part 1 - Remove definitions of Ci, Cr, Cc, and Cu. r=florian 
This patch was autogenerated by my decomponents.py

It covers almost every file with the extension js, jsm, html, py,
xhtml, or xul.

It removes blank lines after removed lines, when the removed lines are
preceded by either blank lines or the start of a new block. The "start
of a new block" is defined fairly hackily: either the line starts with
//, ends with */, ends with {, <![CDATA[, """ or '''. The first two
cover comments, the third one covers JS, the fourth covers JS embedded
in XUL, and the final two cover JS embedded in Python. This also
applies if the removed line was the first line of the file.

It covers the pattern matching cases like "var {classes: Cc,
interfaces: Ci, utils: Cu, results: Cr} = Components;". It'll remove
the entire thing if they are all either Ci, Cr, Cc or Cu, or it will
remove the appropriate ones and leave the residue behind. If there's
only one behind, then it will turn it into a normal, non-pattern
matching variable definition. (For instance, "const { classes: Cc,
Constructor: CC, interfaces: Ci, utils: Cu } = Components" becomes
"const CC = Components.Constructor".)

MozReview-Commit-ID: DeSHcClQ7cG
 2018-02-06 09:36:57 -08:00
Kris Maglione
0bb74efdf1 Bug 1431533: Part 5a - Auto-rewrite code to use ChromeUtils import methods. r=florian 
This was done using the following script:
37e3803c7a/processors/chromeutils-import.jsm

MozReview-Commit-ID: 1Nc3XDu0wGl
 2018-01-29 15:20:18 -08:00
Cosmin Sabou
f09d6d985d Backed out 3 changesets (bug 1431533) for Android mochitest failures on testEventDispatcher on a CLOSED TREE 
Backed out changeset a1eca62826a1 (bug 1431533)
Backed out changeset 34c999fa006b (bug 1431533)
Backed out changeset e2674287e57f (bug 1431533)
 2018-01-30 07:17:48 +02:00
Kris Maglione
fd67f090b2 Bug 1431533: Part 5a - Auto-rewrite code to use ChromeUtils import methods. r=florian 
This was done using the following script:
37e3803c7a/processors/chromeutils-import.jsm

MozReview-Commit-ID: 1Nc3XDu0wGl
 2018-01-29 15:20:18 -08:00
Brindusan Cristian
483ba301cb Backed out 2 changesets (bug 1431533) for ESlint failures on a CLOSED TREE 
Backed out changeset 6e56f4c8843e (bug 1431533)
Backed out changeset 12fc4dee861c (bug 1431533)
 2018-01-30 02:32:43 +02:00
Kris Maglione
683a97d172 Bug 1431533: Part 5a - Auto-rewrite code to use ChromeUtils import methods. r=florian 
This was done using the following script:
37e3803c7a/processors/chromeutils-import.jsm

MozReview-Commit-ID: 1Nc3XDu0wGl
 2018-01-29 15:20:18 -08:00
Shane Caraveo
6a1c954cf4 Bug 1406453 fix http/ws regex r=kmag 
MozReview-Commit-ID: CWPipPGV9vG
 2017-11-15 13:48:30 -08:00
Kris Maglione
7b017c97d6 Bug 1407056: Part 1 - Provide more consistent principal/origin URL to content policies. r=bz,ckerschb 
We're currently fairly vague and inconsistent about the values we provide to
content policy implementations for requestOrigin and requestPrincipal. In some
cases they're the triggering principal, sometimes the loading principal,
sometimes the channel principal.

Our existing content policy implementations which require or expect a loading
principal currently retrieve it from the context node. Since no current
callers require the principal to be the loading principal, and some already
expect it to be the triggering principal (which there's currently no other way
to retrieve), I chose to pass the triggering principal whenever possible, but
use the loading principal to determine the origin URL.

As a follow-up, I'd like to change the nsIContentPolicy interface to
explicitly receive loading and triggering principals, or possibly just
LoadInfo instances, rather than poorly-defined request
origin/principal/context args. But since that may cause trouble for
comm-central, I'd rather not do it as part of this bug.

MozReview-Commit-ID: LqD9GxdzMte
 2017-10-12 15:43:55 -07:00
Shane Caraveo
cf8c5452ed Bug 1305237 Expose frameAncestors to webextensions, r=bz,kmag 
MozReview-Commit-ID: 64lIMu6neaD
 2017-10-10 09:54:22 -07:00
Kris Maglione
e498ce8963 Bug 1404172: Remove MatchPattern.jsm. r=aswan 
MozReview-Commit-ID: ItGMuChHS3z
 2017-09-28 18:27:44 -07:00
Ryan VanderMeulen
252c89b8d4 Backed out changesets d0d30a90efa1 and fd1d81b93380 (bug 1305237) for causing bug 1403932. 2017-09-28 17:55:43 -04:00
Shane Caraveo
d7ebe7ee66 Bug 1305237 Expose frameAncestors to webextensions, r=bz,kmag 
MozReview-Commit-ID: HpneTIKPoS1
 2017-09-27 07:58:17 -07:00
Shane Caraveo
60f1dc1af2 Bug 1398622 fix ws handling in contentpolicymanager, and fix stupid error. r=kmag 
MozReview-Commit-ID: EmPvtRrnrnI
 2017-09-10 21:37:27 -07:00
Shane Caraveo
80a11056a8 Bug 1393909 remove sync messaging from WebRequest, r=kmag 
MozReview-Commit-ID: BrZ6FgP7Uyj
 2017-08-25 12:36:28 -07:00
Mark Banner
9916415caf Bug 1371292 - Clean up more ESLint global definitions in configuration files in toolkit/ and browser/. r=mossop 
MozReview-Commit-ID: 5KC23kzaCFN
 2017-06-08 10:59:12 +01:00
Jared Wein
5a181760cc Bug 1348068 - Enable the key-spacing rule for eslint and fix the related issues. r=standard8 
Running eslint with --fix didn't fix many of the issues. The majority here had to be fixed by hand but a significant majority of the issues were related to a few files that I was able to use find-and-replace with. I regret not making this in to separate commits of the hand-fixes and the fixes from --fix but I don't recall --fix fixing any of the issues.

MozReview-Commit-ID: ANyg2qfo3Qx
 2017-03-21 14:29:43 -04:00
Christoph Kerschbaumer
1eea7608a7 Bug 1329288: Allow content policy consumers to identify contentPolicy checks from docshell. r=bz,kmaglione 2017-01-22 18:05:03 +01:00
Sebastian Hengst
91e7448687 Backed out changeset 69fb2fc61535 (bug 1329288) 2017-01-22 13:09:48 +01:00
Christoph Kerschbaumer
14a98039a1 Bug 1329288: Allow content policy consumers to identify contentPolicy checks from docshell. r=bz,kmaglione 2017-01-22 07:30:26 +01:00
Shane Caraveo
9e03764998 Bug 1316256 - WebRequestContent part: return nsIContentPolicy.ACCEPT in shouldLoad for request principal system. r=kmag 2016-12-15 13:18:00 +01:00
Giorgio Maone
ac57061154 Bug 1242871 - add an originUrl property to every webRequest event details object + tests (extended & fixed + nits). r=kmag 
MozReview-Commit-ID: 6PeCwTeCuFs
 2016-04-01 00:48:57 +02:00
Giorgio Maone
b21e727227 Bug 1163862 - Switch to HTTP observer + support requestId & data: URIs + test fixes r=billm 
MozReview-Commit-ID: 30nEXQpWEHg
 2016-02-26 19:08:32 +01:00
Phil Ringnalda
d4818c82ca Back out 8ae0fba61023 (bug 1163862) for Win7 e10s test_ext_webrequest.html bustage 2016-02-25 20:41:40 -08:00
Giorgio Maone
a690c97982 Bug 1163862 - Switch to HTTP observer where possible + support requestId & data: URIs r=billm 
MozReview-Commit-ID: EBRWBgGPqyD
 2016-02-24 00:21:42 +01:00
Kris Maglione
956fe582d0 Bug 1229874: Part 3 - Enable ESLint in WebExtension code. r=billm 
The base .eslintrc is essentially a merge of the root Toolkit .eslintrc and
the devtools .eslintrc, with some minor changes to match our prevalent style.

For the most enforces the coding styles that we've been using most
consistently. There are a couple of significant differences, though:

 * The rule for opening brace alignment can only be applied globally, and
   doesn't make exceptions for top-level functions. I chose to turn it on, and
   change the brace style of existing top-level functions that violated it,
   since the rule seemed worth using, and that's the direction most Toolkit JS
   code has been headed anyway.

 * The rule for switch/case statements requires an added indentation level for
   case statements. Most of our switch statements did not use an extra level
   of indentation, and I initially wrote the rule to enforce that style, until
   I came across case statements that used blocks, and required the extra
   indentation level for sanity.
 2015-12-02 16:58:53 -08:00
Dave Townsend
7b18d60eed Bug 1229519: Fix toolkit/modules to pass eslint checks. r=mak 2015-12-03 09:58:56 -08:00
Carsten "Tomcat" Book
036e6d2fa3 Backed out 2 changesets (bug 1202902) to recking bug 1202902 to be able to reopen inbound on a CLOSED TREE 
Backed out changeset 647025383676 (bug 1202902)
Backed out changeset d70c7fe532c6 (bug 1202902)
 2015-10-07 14:03:21 +02:00
Carsten "Tomcat" Book
12369728f5 Backed out 1 changesets (bug 1202902) for causing merge conflicts to mozilla-central 
Backed out changeset cfc1820361f5 (bug 1202902)
 2015-10-07 12:13:45 +02:00
Shu-yu Guo
474f49adb7 Bug 1202902 - Scripted fix the world. 2015-10-06 14:00:31 -07:00
Shu-yu Guo
37989840cd Bug 1202902 - Mass replace toplevel 'let' with 'var' in preparation for global lexical scope. (rs=jorendorff) 2015-09-15 11:19:45 -07:00
Bill McCloskey
48d0da1cd3 Bug 1171248 - Add MatchPattern support to WebRequest module (r=Mossop) 2015-06-19 17:35:06 -07:00
Bill McCloskey
4d6dec1794 Bug 1157561 - Add webRequest-like API to Firefox (r=Mossop) 2015-05-11 17:19:21 -07:00