summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Issue #1354 - Don't allow glsl[130,400] unless we have gpu_shader5wolfbeast2020-01-16-0/+30
| | | | | - Teach GLContext about gpu_shader5 - Downgrade shader language version if gpu_shader5 support isn't found.
* Issue #1354 - Cherry-pick ANGLE update for broken drivers that supportwolfbeast2020-01-16-23/+12
| | | | required indexing but not the extensions.
* Issue #1332 - Enable seeking to next frame by default.wolfbeast2020-01-14-6/+0
| | | | | | | The indicated BZ bug was resolved in Gecko 50, and could have already been enabled before (since it returns a promise as-required). With the rest of promise-based media implemented it makes no sense to keep this disabled on production.
* No issue - Remove some unused webextension sync preferences.wolfbeast2020-01-14-8/+0
|
* Issue #1319 - Set some obvious prefs for production builds.wolfbeast2020-01-14-22/+3
| | | | | This sets some defaults for production builds that should be self-explanatory.
* Issue #1353 - Disable remote jar: URIs by default.wolfbeast2020-01-14-5/+0
| | | | | | Considering the one exception this was still enabled for on all versions of Firefox since 45 until our fork point is no longer applicable. This resolves #1353
* No issue - Remove unused network.http.bypass-cachelock-threshold pref.wolfbeast2020-01-14-13/+0
|
* No issue - Don't define gamepad prefs when gamepad support isn't built.wolfbeast2020-01-14-4/+2
| | | | This also sets sane defaults when present. See also #1319.
* Issue #1319 - Enable promise debugging only in DEBUG builds.wolfbeast2020-01-14-1/+1
|
* Issue #1319 - Disable MOZ_LOGGING in production builds.wolfbeast2020-01-14-10/+1
| | | | | This makes it only enabled in debug builds, instead, where logging would be most useful.
* Issue #1319 - Remove stderr_to_file.wolfbeast2020-01-14-51/+0
| | | | | This local-debug function is only useful for Android to work around issues with logspewing and should never be in production builds anyway.
* Fix comments for NSS PBKDF setup (no code change)wolfbeast2020-01-14-1/+2
|
* Issue #1338: Follow-up: Cache the most recent PBKDF2 password hash,Kai Engert2020-01-14-1/+83
| | | | | | to speed up repeated SDR operations. Landed on NSS-3.48 for Bug 1606992
* Reinstate the java->c++ source, generator code + documentation.wolfbeast2020-01-13-0/+20210
| | | | | | | | We've kept the java source up-to-date until its removal, so there should be very little additional java mangling needed to have it back up to speed and usable again. This reverts commit c6446f1126232935c85397aac493113dd38496cd.
* Simplify some alias sets in IonMonkey.wolfbeast2020-01-11-11/+2
|
* Prefer file extension as-provided over default extension for mimetype towolfbeast2020-01-11-52/+84
| | | | look up default applications on Windows
* Issue #1338 - Followup: certdb: propagate trust information if trustDaiki Ueno2020-01-10-8/+22
| | | | | | | | | | | | | module is loaded afterwards, Summary: When the builtin trust module is loaded after some temp certs being created, these temp certs are usually not accompanied by trust information. This causes a problem in UXP as it loads the module from a separate thread while accessing the network cache which populates temp certs. This change makes it properly roll up the trust information, if a temp cert doesn't have trust information.
* Update GTK clipboard handlingwolfbeast2020-01-10-25/+31
| | | | | | | | - Store the clipboard even if it was set in a GTK dialog. - Fix a GtkTargetList leak. - Notify GTK that the data is no longer available for clipboard_get_cb(), so that GTK will no longer advertise nor attempt to store the data.
* Issue #1338 - Un-bust building of NSS after update to 3.48 on Linux.wolfbeast2020-01-10-1/+2
|
* Handle missing base64 challenge in NegotiateAuth and NTLMAuth.wolfbeast2020-01-09-3/+6
|
* Make copy of list before iterating over it.Yaron Tausky2020-01-09-1/+2
|
* Be more consistent about decoding IP addresses in PSM.wolfbeast2020-01-09-2/+7
|
* Simplify value setting.wolfbeast2020-01-09-66/+39
| | | | | This gets rid of unused boolean return values on setters and a level of indirection for calls to set values.
* Merge pull request #1347 from g4jc/html5_dialogMoonchild2020-01-09-520/+462
|\ | | | | Implement HMTL5 <dialog>
| * Bug 1379728 part 1. Remove the double-definition of the 'close' event from ↵Gaming4JC2020-01-07-7/+3
| | | | | | | | | | | | EventNameList.h. Tag #1343
| * Bug 1322938 - Make the HTML tree builder aware of <dialog>.Gaming4JC2020-01-07-221/+227
| | | | | | | | | | Original patch by :hsivonen Tag #1343
| * Bug 1322938 - Put <dialog> element behind preference.Gaming4JC2020-01-07-5/+45
| | | | | | | | Tag #1343
| * Bug 1322938 - Update <dialog> element Web Platform Tests expected results.Gaming4JC2020-01-07-289/+0
| | | | | | | | Tag #1343
| * Bug 1322938 - Emit close event when HTMLDialogElement.prototype.close() is ↵Gaming4JC2020-01-07-1/+12
| | | | | | | | | | | | called. Tag #1343
| * Bug 1322938 - Basic implementation of HTMLDialogElement.Gaming4JC2020-01-07-4/+182
| | | | | | | | Tag #1343
* | Issue #1348 - Part 3: Set IS_PRIVATE input scope in private browsing.wolfbeast2020-01-09-9/+28
| | | | | | | | | | | | | | | | | | Microsoft IME on Windows 10 20H1 (build 19025+) supports IME private mode by input scope. Although previous Windows versions use an undocumented API for Edge and IE only, the next Windows 10 release will use a public API for it. We pre-empt this potential privacy concern by setting the IS_PRIVATE flag when in PB mode.
* | Issue #1348 - Part 2: Teach IMEState about Private Browsing mode.wolfbeast2020-01-09-8/+21
| |
* | Issue #1348 - Part 1: Clean up input scope support for IMM32.Makoto Kato2020-01-09-50/+26
|/ | | | Use AutoTArray to set input scope.
* Reject sample rates that are out-of-range for libsoundtouch.wolfbeast2020-01-07-3/+8
| | | | | We never reach this with our normal use of this lib but adding the sanity check just in case. (ported from upstream)
* Merge pull request #1346 from JustOff/PR_CSSStyleSheet_legacyMoonchild2020-01-07-0/+37
|\ | | | | Issue #1345 - Implement non-standard legacy CSSStyleSheet rules
| * Issue #1345 - Implement non-standard legacy CSSStyleSheet rulesJustOff2020-01-07-0/+37
|/
* Merge pull request #1341 from MoonchildProductions/nss-workMoonchild2020-01-04-80091/+1665226
|\ | | | | Update NSPR and NSS
| * Issue #1338 - Part 5: Clobber for NSS updatewolfbeast2020-01-02-0/+1
| | | | | | | | We usually need this, so just in case.
| * Issue #1338 - Part 4: Initialize NSS with desired run-time values.wolfbeast2020-01-02-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | This NSS version (and onward) has variables to enable PKDBF rounds for master password hardening (combating brute-force guessing). Since we use DBM, we need to explicitly enable iteration counts in DBM mode, and adjust the rounds used with a lower maximum because the PKDBF routine for DBM is considerably slower for which the NSS default of 10,000 is debilitatingly high. The method for this is run-time configuration through environment variables. We set these prior to NSS initialization from nsAppRunner.cpp so the NSS lib picks them up and allows us to continue using the DBM cert/key stores with stored rounds per record.
| * Issue #1338 - Part 3: Update NSS symbolswolfbeast2020-01-02-0/+4
| |
| * Issue #1338 - Part 2: Update NSS to 3.48-RTMwolfbeast2020-01-02-31445/+1622266
| |
| * Issue #1338 - Part 1: Update NSPR to 4.24wolfbeast2020-01-02-48646/+42943
|/
* Merge pull request #1340 from g4jc/mailnews_enhanceNew Tobin Paradigm2019-12-31-118/+237
|\ | | | | OAuth2 updates
| * Bug 1599054 - allow callers to ommit sending OAuth2 client_secret parameter.Gaming4JC2019-12-30-2/+21
| |
| * Bug 1597933 - Use URLSearchParams for setting params for OAuth2 ↵Gaming4JC2019-12-30-20/+37
| | | | | | | | authorization request.
| * Bug 1597933 - use fetch + URLSearchParms instead of Http.jsm to request ↵Gaming4JC2019-12-30-32/+32
| | | | | | | | OAuth2 access token.
| * Bug 1597933 - don't pass string constants to determine OAuth refresh token ↵Gaming4JC2019-12-30-10/+16
| | | | | | | | or not.
| * Bug 1597933 - improve OAuth2 params parsing.Gaming4JC2019-12-30-15/+7
| |
| * Bug 1597933 - clean up OAuth2 code: remove responseType which is always code.Gaming4JC2019-12-30-9/+6
| | | | | | | | Response type token is part of the OAuth 2.0 Implicit Flow which is not used in Mail Applications, but also discouraged by the OAuth Working Group: https://developer.okta.com/blog/2019/05/01/is-the-oauth-implicit-flow-dead
| * Bug 1453643 - Enable proper retry on oauth2 authenication failure.Gaming4JC2019-12-30-26/+34
| | | | | | | | This prevents mail applications from attempting to use an unauthenticated connection to mailbox(s) and avoid unexpected deletion of local mbox files and subsequent re-download of mailbox content over imap.