Commit message (Collapse) | Author | Age | Lines | |
---|---|---|---|---|
* | Creating customized built-in elements without relevant definitions ↵ | Gaming4JC | 2020-01-26 | -94/+0 |
| | | | | | | | | registered first shouldn't throw NotFoundError; per spec change: https://github.com/w3c/webcomponents/issues/608 Tag UXP Issue #1344 | |||
* | Bug 1359346 - Implement custom element state; | Gaming4JC | 2020-01-26 | -22/+44 |
| | | | | | | https://dom.spec.whatwg.org/#concept-element-custom-element-state Tag UXP Issue #1344 | |||
* | Bug 1357002 - Part 2: Don't call SetupCustomElement() if the custom element ↵ | Gaming4JC | 2020-01-26 | -1/+2 |
| | | | | | | feature is pref-ed off; Tag UXP Issue #1344 | |||
* | Bug 1357002 - Part 1: Cache dom.webcomponents.customelements.enabled preference; | Gaming4JC | 2020-01-26 | -1/+9 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1341898 - Make nsDocument::IsWebComponentsEnabled use a cached bool pref; | Gaming4JC | 2020-01-26 | -4/+12 |
| | | | | | | Note: Minus IPC bit. Tag UXP Issue #1344 | |||
* | Bug 1309147 - Part 5: Eliminate performance cliff when accessing CEReactions ↵ | Gaming4JC | 2020-01-26 | -5/+19 |
| | | | | | | code. Tag UXP Issue #1344 | |||
* | Bug 1309147 - Part 4: Add CEReactions for CustomElementRegistry. | Gaming4JC | 2020-01-26 | -10/+2 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1309147 - Part 3: Implement the support for CEReactions in Codegen. | Gaming4JC | 2020-01-26 | -0/+96 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1309147 - Part 2: Add the name of 'this' value's JSObject* for codegen ↵ | Gaming4JC | 2020-01-26 | -2/+3 |
| | | | | | | to generate CEReaction code. Tag UXP Issue #1344 | |||
* | Bug 1309147 - Part 1: Implement the support for CEReactions in WebIDL parser. | Gaming4JC | 2020-01-26 | -0/+180 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1350960 - Release CustomElementReactionsStack in TabGroup thread when ↵ | Gaming4JC | 2020-01-26 | -0/+3 |
| | | | | | | | | DocGroup is going away. Note: In UXP we use non-Quantum thread checking implementation here. Tag UXP Issue #1344 | |||
* | Bug 1351979 - Change CustomElementRegistry::Define code to properly ↵ | Gaming4JC | 2020-01-26 | -1/+1 |
| | | | | | | propagate out JS exceptions; Tag UXP Issue #1344 | |||
* | Bug 1347446 - Move custom element reactions stack to DocGroup. | Gaming4JC | 2020-01-26 | -90/+136 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1341693 - Don't need to check GetDocShell() when creating ↵ | Gaming4JC | 2020-01-26 | -35/+23 |
| | | | | | | CustomElementRegistry; Tag UXP Issue #1344 | |||
* | Bug 1309184 - Implement upgrade reaction for custom element reactions. | Gaming4JC | 2020-01-26 | -29/+267 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1274159 - Part 4: Add test cases for HTMLConstructor; | Gaming4JC | 2020-01-26 | -0/+437 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1274159 - Part 3-2: Update web-platform-test expected result; | Gaming4JC | 2020-01-26 | -28/+0 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1274159 - Part 3-1: Add HTMLConstructor to HTMLElement and its subclass; | Gaming4JC | 2020-01-26 | -6/+68 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1274159 - Part 2-2: Support HTMLConstructor WebIDL extended attribute ↵ | Gaming4JC | 2020-01-26 | -30/+534 |
| | | | | | | for custom elements; Tag UXP Issue #1344 | |||
* | Bug 1274159 - Part 2-1: Include the name of relevant interface in ↵ | Gaming4JC | 2020-01-26 | -108/+104 |
| | | | | | | nsHTMLTagList.h; Tag UXP Issue #1344 | |||
* | Bug 1274159 - Part 1: Support looking up definitions by using constructor as ↵ | Gaming4JC | 2020-01-26 | -36/+50 |
| | | | | | | a key; Tag UXP Issue #1344 | |||
* | Bug 1271549 - Remove details and summary preference. | Gaming4JC | 2020-01-26 | -121/+21 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1276438 part 3. Align the .body setter with the spec a bit better. | Gaming4JC | 2020-01-26 | -5/+53 |
| | | | | | | | | | | | | There are two changes here: 1) We allow setting .body even if the root element is not an <html:html>. This is what the spec says to do, and what we used to do before the changes in bug 366200. No tests for this yet, pending https://github.com/whatwg/html/issues/3403 getting resolved. 2) We use GetBody(), not GetBodyElement(), to look for an existing thing to replace. This matters if there are <frameset>s involved. Tag UXP Issue #1344 Tag UXP Issue #252 | |||
* | Bug 1276438 part 2. Move the implementation of the .body setter from ↵ | Gaming4JC | 2020-01-26 | -26/+28 |
| | | | | | | | nsHTMLDocument to nsIDocument. Tag UXP Issue #1344 Tag UXP Issue #252 | |||
* | Bug 1276438 part 1. Move the implementation of the .body getter from ↵ | Gaming4JC | 2020-01-26 | -21/+25 |
| | | | | | | | nsHTMLDocument to nsIDocument. Tag UXP Issue #1344 Tag UXP Issue #252 | |||
* | Merge pull request #1371 from athenian200/ftp-list | Moonchild | 2020-01-26 | -4/+20 |
|\ | | | | | Potential hang on bad FTP sequence | |||
| * | Fix whitespace. | athenian200 | 2020-01-26 | -1/+1 |
| | | ||||
| * | Issue #1349 - Stop 2xx FTP responses from causing browser to hang. | athenian200 | 2020-01-26 | -4/+20 |
|/ | | | | | | LIST and RETR still appear to work as intended on ftp:// URLs after my changes. I wasn't able to test STOR because the browser doesn't appear to support FTP uploads at this time (although our FTP implementation appears perfectly capable of doing an FTP upload.) If I understood the issue correctly, though, what we're doing is ensuring that we receive a preliminary 100 response from the FTP server for a given action before jumping to the 200 code describing what we do if the action was completed. Even though it makes no logical sense for a server to say an action was completed before it was initiated, someone could write a really annoying FTP server that takes advantage of this fact to crash the browser if they wanted. | |||
* | No issue - Always use jemalloc allocator for storage memory when | wolfbeast | 2020-01-23 | -8/+1 |
| | | | | MOZ_MEMORY is defined (which is defined by enabling jemalloc in config) | |||
* | Issue #1338 - Follow-up: Also cache the most recent PBKDF1 hash | Kai Engert | 2020-01-23 | -50/+140 |
| | | | | This rewrites the caching mechanism to apply to both PBKDF1 and PBKDF2 | |||
* | Issue #1342 - Remove support for system libevent | wolfbeast | 2020-01-23 | -55/+4 |
| | ||||
* | Issue #1366 - Fix build bustage from erroneously removing 2 function ↵ | wolfbeast | 2020-01-22 | -0/+14 |
| | | | | implementations. | |||
* | Issue #1354 - Fix another potential crashing scenario in WebGL. | wolfbeast | 2020-01-22 | -95/+81 |
|\ | | | | | | | (merge of gl-work branch) | |||
| * | Issue #1354 - Fix typo | wolfbeast | 2020-01-21 | -1/+1 |
| | | ||||
| * | Issue #1354 - Clear the current context when MakeCurrent() fails. | wolfbeast | 2020-01-20 | -95/+81 |
| | | ||||
* | | Merge pull request #1367 from g4jc/showmodaldialog | Moonchild | 2020-01-22 | -1313/+14 |
|\ \ | |/ |/| | Completely remove showModalDialog | |||
| * | Issue #1366 - Completely remove showModalDialog | Gaming4JC | 2020-01-21 | -1313/+14 |
|/ | ||||
* | Issue #1338 - Bump NSS version | wolfbeast | 2020-01-20 | -3/+3 |
| | | | | | | | Our NSS version is closer to the currently-released .1, so bump version to that. Note: we still have some additional patches to the in-tree version in place so this isn't a 100% match to the RTM one. | |||
* | Merge branch 'master' of https://github.com/MoonchildProductions/UXP | wolfbeast | 2020-01-19 | -16/+17 |
|\ | ||||
| * | Issue #1358 - Default to SSL/TLS when using the Account Wizard | Matt A. Tobin | 2020-01-18 | -3/+6 |
| | | ||||
| * | Issue #1359 - Pointlessly rename greprefs.. again. | Matt A. Tobin | 2020-01-18 | -13/+11 |
| | | ||||
* | | Issue #1362 - Revert "Implement regular expression lookbehind" | wolfbeast | 2020-01-19 | -359/+157 |
| | | | | | | | | This reverts commit fa473930f424bf17a9e545b601c84dd2e61364e3. | |||
* | | Issue #1362 - Revert "Update js/src/builtin/TestingFunctions.cpp for | wolfbeast | 2020-01-19 | -3/+3 |
|/ | | | | | | regex lookbehind changes" This reverts commit e79607a7a694dc2d48d65697b48138fa585145c9. | |||
* | Minor update to the html5 parser component doc | wolfbeast | 2020-01-18 | -2/+2 |
| | ||||
* | No issue - Fix unsafe http methods on HTTP/2 with TLSv1.3 0RTT. | wolfbeast | 2020-01-18 | -2/+6 |
| | ||||
* | Add component documentation for the HTML5 parser. | wolfbeast | 2020-01-18 | -0/+63 |
| | ||||
* | Revert "No issue - Fix unsafe http methods on HTTP/2 with TLSv1.3 0RTT." | wolfbeast | 2020-01-18 | -6/+2 |
| | | | | This reverts commit 67d336a6f27889bdef4723194b6611d049830266. | |||
* | No issue - Fix unsafe http methods on HTTP/2 with TLSv1.3 0RTT. | wolfbeast | 2020-01-17 | -2/+6 |
| | ||||
* | Update readme instructions for how to use the java html5 parser codegen makefile | Matt A. Tobin | 2020-01-16 | -18/+13 |
| | ||||
* | Merge branch 'html5-parser-work' | Matt A. Tobin | 2020-01-16 | -221/+71285 |
|\ |