forked from mirrors/gecko-dev
0265423f41
https://w3c.github.io/webdriver/#dfn-get-current-url says: > For each cookie in all associated cookies of session's > current browsing context's active document ... However, the cookie implementations in driver.sys.mjs called _getCurrentURL which returned the URL of the _top level browsing context_ as specified in https://w3c.github.io/webdriver/#dfn-get-current-url As a consequence, the cookie tests that set and deleted cookies inside an iframe used the top level path for deleting cookies instead of the path of the iframe, so they failed to find any cookies applicable to that path. For example running cookies/encoding/charset.html would set cookies by calling `fetch('/cookies/resources/cookie.py?...')` then it would try to delete cookies by calling getAndExpireCookiesForDefaultPathTest which opened an iframe to /cookies/resources/echo-cookie.html This iframe would call `setTestContextUsingRootWindow()` then call `await test_driver.delete_all_cookies();` - but this call attempted to delete cookies for the top level browing context's path - /cookies/encoding/ Differential Revision: https://phabricator.services.mozilla.com/D211434 |
||
|---|---|---|
| .. | ||
| actors | ||
| chrome | ||
| test | ||
| .eslintrc.js | ||
| addon.sys.mjs | ||
| atom.sys.mjs | ||
| browser.sys.mjs | ||
| cert.sys.mjs | ||
| cookie.sys.mjs | ||
| driver.sys.mjs | ||
| evaluate.sys.mjs | ||
| interaction.sys.mjs | ||
| jar.mn | ||
| json.sys.mjs | ||
| l10n.sys.mjs | ||
| message.sys.mjs | ||
| moz.build | ||
| navigate.sys.mjs | ||
| packets.sys.mjs | ||
| prefs.sys.mjs | ||
| README | ||
| reftest-content.js | ||
| reftest.sys.mjs | ||
| server.sys.mjs | ||
| stream-utils.sys.mjs | ||
| sync.sys.mjs | ||
| transport.sys.mjs | ||
| web-reference.sys.mjs | ||
| webauthn.sys.mjs | ||
Marionette [ ˌmarɪəˈnɛt] is * a puppet worked by strings: the bird bobs up and down like a marionette; * a person who is easily manipulated or controlled: many officers dismissed him as the mayor’s marionette; * the remote protocol that lets out-of-process programs communicate with, instrument, and control Gecko-based browsers. Marionette provides interfaces for interacting with both the internal JavaScript runtime and UI elements of Gecko-based browsers, such as Firefox on desktop and mobile. It can control both the chrome- and content documents, giving a high level of control and ability to replicate, or emulate, user interaction. Head on to the Marionette documentation to find out more: https://firefox-source-docs.mozilla.org/testing/marionette/