summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* 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.
| * Bug 1176399 - Multiple requests for master password when GMail OAuth2 is ↵Gaming4JC2019-12-30-21/+101
|/ | | | enabled.
* Merge pull request #1335 from MoonchildProductions/document_openMoonchild2019-12-28-629/+640
|\ | | | | Align document.open() with the overhauled specification
| * Issue #1118 - Part 9: Don't allow reuse of unlinked CallbackObjectHolder.wolfbeast2019-12-23-1/+2
| |
| * Issue #1118 - Part 8: Remove no-longer-used mDidDocumentOpen andwolfbeast2019-12-23-40/+0
| | | | | | | | | | | | | | | | | | | | | | CheckForOutdatedParent() This was only used to check for cases when document.open() changed the global, and elements being inserted into the document needing a new reflector as a result. Since document.open() no longer changes the global, this code is no longer needed.
| * Issue #1118 - Part 7: Remove no-longer-used mWillReparent debug code.wolfbeast2019-12-23-17/+0
| |
| * Issue #1118 - Part 6: Fix various tests that are no longer correct.wolfbeast2019-12-22-205/+71
| | | | | | | | | | The behavior change of document.open() requires these tests to be changed to account for the new spec behavior.
| * Issue #1118 - Part 5: Change the way document.open() workswolfbeast2019-12-22-297/+400
| | | | | | | | | | | | | | | | | | | | | | | | This changes the work we do for document.open() in the following ways: - We no longer create a new Window when doing document.open(). We use the same Window but remove all the event listeners on the existing DOM tree and Window before removing the document's existing children to provide a clean slate document to use for .write(). - We no longer create a session history entry (previously would be a wyciwyg URI). We now replace the current one, effectively losing the entry for the original document. - We now support document.open() on windowless documents.
| * Forward to new tree structure.wolfbeast2019-12-22-612345/+600642
| |\
| * | Issue #1118 Part 4: Allow UpdateURLAndHistory to work even if there's nowolfbeast2019-08-06-13/+17
| | | | | | | | | | | | | | | | | | | | | root session history. This can happen when someone does a document.open() on a document that has no session history.
| * | Issue #1118 Part 3: Add a public RemoveAllListeners method onwolfbeast2019-08-06-4/+25
| | | | | | | | | | | | EventListenerManager.
| * | Issue #1118 Part 2: Allow UpdateURLAndHistory to work even if mOSHE iswolfbeast2019-08-06-2/+15
| | | | | | | | | | | | | | | | | | | | | | | | null, if we're doing a replace. We're going to end up hitting this if someone does a document.open() before mOSHE has been set. We shouldn't need to worry about mLSHE, because the document.open() will cancel the corresponding load.
| * | Issue #1118 Part 1: Split out part of nsDocShell::AddState into awolfbeast2019-07-31-52/+112
| | | | | | | | | | | | | | | | | | | | | separate method. This implements the "URL and history update steps" from the HTML spec. See https://html.spec.whatwg.org/multipage/history.html
* | | Merge pull request #1336 from athenian200/html-media-hackMoonchild2019-12-28-32/+313
|\ \ \ | | | | | | | | Issue #1332 - Backport promise-based media playback.
| * | | Fix typo.athenian2002019-12-24-0/+1
| | | |
| * | | Issue #1332 - Backport promise-based media playbackathenian2002019-12-23-32/+312
|/ / / | | | | | | | | | | | | | | | | | | | | | https://bugzilla.mozilla.org/show_bug.cgi?id=1244768 I happened to find an older version of the promise-based media playback patch in Bugzilla, the one that was originally submitted for review. It had the DocShell changes I already knew how to deal with, and had fewer of the audio wrapper and nsISupports changes that were confusing me in the later patch. I was able to do a better job getting this back into a UXP-appropriate configuration than I could have with the final version. I'm honestly still a little unsure about some of the minor refactoring done in the patch itself, insisting on already_AddRefed promises and such, but I don't really know how to avoid those completely. Still, I think it's better than it was.
* | | Merge pull request #1334 from g4jc/bug1333Moonchild2019-12-22-5/+4
|\ \ \ | |_|/ |/| | Don't hang on to pointer from temporary NS_LossyConvertUTF16toASCII.
| * | Bug 1341238 - Don't hang on to pointer from temporary ↵Gaming4JC2019-12-22-5/+4
|/ / | | | | | | | | | | NS_LossyConvertUTF16toASCII. Resolves #1333
* | Update READMEwolfbeast2019-12-21-5/+7
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-22 20:44:35 +0000