Commit message (Collapse) | Author | Age | Lines | |
---|---|---|---|---|
* | Issue #1656 - Part 2: Unmangle some unfortunate UTF-8 victims. | Moonchild | 2020-09-23 | -1/+1 |
| | | | | The poor fellows got lost in an ASCII-interpretation of the world. | |||
* | Issue #1656 - Part 1: Nuke most vim config lines in the tree. | Moonchild | 2020-09-23 | -2/+1 |
| | | | | | | Since these are just interpreted comments, there's 0 impact on actual code. This removes all lines that match /* vim: set(.*)tw=80: */ with S&R -- there are a few others scattered around which will be removed manually in a second part. | |||
* | Bug 1396584 - Remove support for multiple ShadowRoots | Matt A. Tobin | 2020-04-17 | -2/+2 |
| | | | | Tag #1375 | |||
* | Bug 1430951 - Avoid element name atomizing to improve performance of ↵ | Gaming4JC | 2020-01-26 | -1/+3 |
| | | | | | | | | LookupCustomElementDefinition Since we are dealing with the element (nodeInfo->LocalName() and NameAtom() are the same value), we could use nodeInfo->NameAtom() instead. Tag UXP Issue #1344 | |||
* | Bug 1406325 - Part 4: Use mType for LookupCustomElementDefinition and also ↵ | Gaming4JC | 2020-01-26 | -1/+1 |
| | | | | | | removing parts of v0. Tag UXP Issue #1344 | |||
* | Bug 1406325 - Part 3: Refactor custom elements clone a node. | Gaming4JC | 2020-01-26 | -25/+19 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1406325 - Part 2: Set CustomElementData when cloning a node. | Gaming4JC | 2020-01-26 | -4/+4 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1319342 - Clone a node should enqueue an upgrade reaction. | Gaming4JC | 2020-01-26 | -5/+23 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1121994 - Implement adopted callback for custom elements. | Gaming4JC | 2020-01-26 | -0/+17 |
| | | | | Tag UXP Issue #1344 | |||
* | Bug 1377993 - Make node slots less memory hungry in common cases. | Gaming4JC | 2020-01-26 | -3/+6 |
| | | | | Tag UXP Issue #1344 | |||
* | Actually unlink targets from registered intersection observers. | wolfbeast | 2019-01-19 | -0/+10 |
| | | | | | | | When a node is released/removed, and it has an intersection observer attached to it, that observer should be unlinked at the time of release. This resolves #935. | |||
* | Stabilize and align Intersection Observers | wolfbeast | 2018-06-27 | -9/+0 |
| | | | | | | | - Fixes several crashes - Aligns the feature with the W3C WD spec Tag #249 | |||
* | Add m-esr52 at 52.6.0 | Matt A. Tobin | 2018-02-02 | -0/+696 |