summaryrefslogtreecommitdiffstats
path: root/testing
Commit message (Collapse)AuthorAgeLines
* Issue #1375 - Merge CustomElements pref with Webcomponents PrefMatt A. Tobin2020-04-17-2/+1
|
* Bug 1409976 - Add `slotchange` eventMatt A. Tobin2020-04-17-146/+0
| | | | | | | * Add support for `slotchange` event * Signal `slotchange` when slot's assigned nodes changes Tag #1375
* Bug 1412775 - Implement Event.composedPathMatt A. Tobin2020-04-17-106/+0
| | | | Tag #1375
* Bug 1413619 - Fix insertion point computation when display: contents pseudos ↵Matt A. Tobin2020-04-17-0/+5
| | | | | | are involved. Tag #1375
* Bug 1409975 - Implement node distribution for shadow tree slotsMatt A. Tobin2020-04-17-214/+2
| | | | | | | | | | * Implementation for assignedNodes * Include slots in the flat tree * Fix event get-the-parent algorithm for a node * Update and add reftests for Shadow DOM v1 * Update web platform tests expectations Tag #1375
* Bug 1411878 - Support Element.shadowRoot and Element.assignedSlot / ↵Matt A. Tobin2020-04-17-8/+0
| | | | | | TextNode.assignedSlot on closed shadow root Tag #1375
* Bug 1404842 - Implement Element.attachShadow and Element.slotMatt A. Tobin2020-04-17-807/+0
| | | | Tag #1375
* Bug 1408341 - Implement assignedSlot on Element and TextMatt A. Tobin2020-04-17-9/+1
| | | | Tag #1375
* Issue #1498 - Part 4: Remove clearPreloads.wolfbeast2020-03-27-1/+0
| | | | Also tag #1280
* Remove gtest reference to non-existing path of removed componentwolfbeast2020-02-21-5/+0
|
* Issue #1356 - Add tests.athenian2002020-01-28-0/+25
| | | | Forgot to include these before.
* Merge branch '1360'wolfbeast2020-01-27-18/+9
|\
| * Issue #1360 - Part 2: Update tests for changed preferences.wolfbeast2020-01-26-18/+9
| |
* | Bug 1430034 - Fix attributeChangedCallback isn't fired with correct newValue ↵Gaming4JC2020-01-26-0/+31
| | | | | | | | | | | | when the attribute value is an empty string; Tag UXP Issue #1344
* | Bug 1415761 - Catch the exception and rethrow it after invoking custom ↵Gaming4JC2020-01-26-0/+31
| | | | | | | | | | | | | | | | elements reactions; The spec was unclear on how CEReactions interact with thrown exceptions; see https://github.com/whatwg/html/issues/3217. The spec is now being clarified in https://github.com/whatwg/html/pull/3235. Tag UXP Issue #1344
* | Bug 1319342 - Clone a node should enqueue an upgrade reaction.Gaming4JC2020-01-26-37/+0
| | | | | | | | Tag UXP Issue #1344
* | Bug 1121994 - Implement adopted callback for custom elements.Gaming4JC2020-01-26-119/+0
| | | | | | | | Tag UXP Issue #1344
* | Bug 1334044: Replace detached callback (v0) with disconnected callback (v1).Gaming4JC2020-01-26-62/+0
| | | | | | | | Tag UXP Issue #1344
* | Bug 1334043 - Part 3: Update tests for connected callback.Gaming4JC2020-01-26-78/+0
| | | | | | | | Tag UXP Issue #1344
* | Bug 1334051 - Part 2: Invoke attributeChangedCallback only if attribute name ↵Gaming4JC2020-01-26-28/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | is in the observed attribute list. We call attributeChangedCallback in two cases: 1. When any of the attributes in the observed attribute list has changed, appended, removed, or replaced. 2. When upgrading an element, for each attribute in element's attribute list that is in the observed attribute list. Note: w/ Fixup for not implementing an API Enhancement Bug 1363481. Tag UXP Issue #1344
* | Bug 1274159 - Part 3-2: Update web-platform-test expected result;Gaming4JC2020-01-26-28/+0
| | | | | | | | Tag UXP Issue #1344
* | Bug 1274159 - Part 1: Support looking up definitions by using constructor as ↵Gaming4JC2020-01-26-29/+0
| | | | | | | | | | | | a key; Tag UXP Issue #1344
* | Bug 1271549 - Remove details and summary preference.Gaming4JC2020-01-26-10/+3
| | | | | | | | Tag UXP Issue #1344
* | Bug 1276438 part 3. Align the .body setter with the spec a bit better.Gaming4JC2020-01-26-0/+50
|/ | | | | | | | | | | | 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
* No issue - Remove unused network.http.bypass-cachelock-threshold pref.wolfbeast2020-01-14-5/+0
|
* Bug 1322938 - Put <dialog> element behind preference.Gaming4JC2020-01-07-3/+10
| | | | Tag #1343
* Bug 1322938 - Update <dialog> element Web Platform Tests expected results.Gaming4JC2020-01-07-289/+0
| | | | Tag #1343
* Issue #1118 - Part 6: Fix various tests that are no longer correct.wolfbeast2019-12-22-11/+12
| | | | | The behavior change of document.open() requires these tests to be changed to account for the new spec behavior.
* Merge branch 'master' into js-moduleswolfbeast2019-11-10-35/+356
|\ | | | | | | | | # Conflicts: # modules/libpref/init/all.js
| * 1333045 - Update Location object properties to current spec.Gaming4JC2019-07-18-0/+67
| | | | | | | | | | | | | | Specifically, three changes: 1) valueOf should be non-enumerable. 2) valueOf should be === to Object.prototype.valueOf. 3) There should be no toJSON.
| * Issue #1160 - Remove HotFix preferences from testingGaming4JC2019-07-05-4/+1
| |
| * Remove Firefox Accounts service and tie-ins.wolfbeast2019-04-19-19/+0
| | | | | | | | See previous commit for removal of browser identity module.
| * Remove Parser::reportBadReturnwolfbeast2019-04-06-1/+1
| | | | | | | | Report simpler errors that don't use the offset of a node as location.
| * Merge branch 'master' into 816wolfbeast2019-04-05-2/+284
| |\
| | * Update webplatform tests for multiline placeholder.wolfbeast2019-02-20-2/+284
| | | | | | | | | | | | | | | | | | | | | | | | | | | Note: MANIFEST updated per the normal procedure using `mach wpt-manifest-update` lint.whitelist updated to reflect intentional use of CR in these tests. Resolves #977
| * | Stage 1-4: Update testsTooru Fujisawa2019-02-03-3/+3
| |/
| * Issue #832 Part 1: Remove modules, chrome, and preferences.Ascrod2018-10-11-6/+0
| |
* | Merge branch 'master' into js-moduleswolfbeast2018-08-05-6/+3
|\|
| * Bug 1351193 - Update testsjanekptacijarabaci2018-07-20-3/+0
| |
| * Update requirements.txtMoonchild2018-07-13-1/+1
| |
| * Update mozharness reqs.wolfbeast2018-07-13-2/+2
| |
* | Bug 1340865 - New tests. (not hooked up)wolfbeast2018-07-10-0/+29
|/
* Remove UITour and customize tips.Ascrod2018-05-31-4/+0
|
* Remove Social API.Ascrod2018-05-30-1/+0
|
* Merge pull request #412 from g4jc/hsts_priming_removal_backportMoonchild2018-05-30-15/+0
|\ | | | | Remove support and tests for HSTS priming from the tree. Fixes #384
| * Remove support and tests for HSTS priming from the tree. Fixes #384Gaming4JC2018-05-26-15/+0
| |
| * Revert "Remove the Social API"Moonchild2018-05-25-0/+1
| |
| * Remove the Social APIAscrod2018-05-24-1/+0
| |
* | Bug 1394399 - Fix web-platform-tests to expect "same-origin" default ↵janekptacijarabaci2018-05-26-2/+2
|/ | | | | | Request.credentials Issue #389
* Bug 1384062 - Make SystemResourceMonitor.stop more resilient to errors. ↵Mike Hommey2018-05-16-12/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r=ahal,gps The poll() call in SystemResourceMonitor.stop might fail even though there is something to read from the pipe, in some corner cases, and python won't let us know about it. In that case, an exception is thrown, leaving the SystemResourceMonitor (and its callers) in a weird state. In practice, this leads BuildMonitor.__exit__ to recall stop, which then fails. So when poll() throws an exception, we pretend there's still something to read, and we try to read anyways. If there is something to read, recv() will return it, otherwise, it will throw an exception of its own, which we catch, pretending we're done. Furthermore, when there is nothing to read from the pipe, poll() simply returns False, and our loop never sets `done` to True, and we then hit an assert, which doesn't have its place here, so we remove it. Finally, the other end of the pipe might have died at any time, making sending over the pipe fail, so we also protect against that. With all these changes, it feels like the reason to backout bug 1239939 in bug 1272782 should have been dealt with, and we can drop the timeout again. --HG-- extra : rebase_source : ac72dd5b2602cf3ffddfb429f95e02380f939893
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-02 08:17:42 +0000