- Dec 13, 2022
-
-
Karl Tomlinson authored
so as to add support for double-keyed per device permissions, which can then all be cleared from a single item/button. Differential Revision: https://phabricator.services.mozilla.com/D162233
-
Karl Tomlinson authored
An all-device "Allow" option is not provided because the permission grant prompt is primarily a device selection, which will (with subsequent patches) grant persistent permission for the selected device. Bug 1800287 covers setting a similar block from the selectAudioOutput() prompt. Differential Revision: https://phabricator.services.mozilla.com/D162232
-
Mike Hommey authored
Differential Revision: https://phabricator.services.mozilla.com/D164182
-
Mike Hommey authored
Differential Revision: https://phabricator.services.mozilla.com/D164187
-
Hannah Peuckmann authored
Differential Revision: https://phabricator.services.mozilla.com/D162108
-
Hannah Peuckmann authored
Differential Revision: https://phabricator.services.mozilla.com/D161683
-
Emilio Cobos Álvarez authored
This preserves the revert keyword behavior. This doesn't match the spec to the letter, see https://github.com/whatwg/html/issues/8610, but I think it's probably ok to keep behavior for now. Changing to match the spec would avoid duplicating the details.css summary rule. Differential Revision: https://phabricator.services.mozilla.com/D164439
-
Sylvestre Ledru authored
Differential Revision: https://phabricator.services.mozilla.com/D163769
-
Sylvestre Ledru authored
Differential Revision: https://phabricator.services.mozilla.com/D163157
-
Diego E. Moreno authored
Differential Revision: https://phabricator.services.mozilla.com/D164467
-
Tim Huang authored
Differential Revision: https://phabricator.services.mozilla.com/D163930
-
Tim Huang authored
This patch implements the reload event telemetry for cookie banner. The event telemetry will be collected when the OnLocationChange event fires for reloads. We add the WebProgressListener whenever a browingContext is attached and remove the WebProgressListener as the browsingContext is discarded. By collecting in OnLocationChange event, it allows the reload telemtry on both desktop and mobile. The reload telemetey covers iframes too. This means that we will report there is a rule if the iframe has the rule but the top-level domain doesn't have. Differential Revision: https://phabricator.services.mozilla.com/D163929
-
Tim Huang authored
Differential Revision: https://phabricator.services.mozilla.com/D163928
-
Robert Longson authored
Differential Revision: https://phabricator.services.mozilla.com/D164216
-
Nicolas Chevobbe authored
Differential Revision: https://phabricator.services.mozilla.com/D164104
-
Nicolas Chevobbe authored
As it was done for the netmonitor in Bug 1640689, we need to add the webconsole document to the whitelist of nested content browsers so we can show the html preview of network request in the console. Differential Revision: https://phabricator.services.mozilla.com/D164103
-
Stanca Serban authored
Backed out changeset ad94b64c18cb (bug 1751763) for causing mochitests failures on browser_startup_images.js. CLOSED TREE
-
Stanca Serban authored
-
Nicolas Chevobbe authored
Differential Revision: https://phabricator.services.mozilla.com/D164343
-
Mozilla Releng Treescript authored
sc -> c1ef9867770f8d7cd584b53f48b0fc18a059021f
-
Jan Varga authored
Bug 1805135 - Fix FileSystemWritableFileStream to use the default writer for all IO operations; r=dom-storage-reviewers,webidl,smaug,jari Differential Revision: https://phabricator.services.mozilla.com/D164444
-
Nicolas Chevobbe authored
Differential Revision: https://phabricator.services.mozilla.com/D162990
-
Jan Varga authored
Bug 1803062 - GetSerialEventTarget should return the nested event target when a sync loop is running; r=asuth Differential Revision: https://phabricator.services.mozilla.com/D163841
-
Otto Länd authored
# ignore-this-changeset
-
Paul Bone authored
This structure is more optimal if it is somewhat aligned with the system's cache line length (which we assume is 64 bytes but that's not always true). This reduces the number of cache lines required to access one record on average. On 32-bit systems we can manage 32-bytes, on 64-bit systems we can manage 48 bytes. We do this by: * Make mRunSize the number of pages in a run rather than bytes, so that it can be stored in a single byte and save some space in bin headers. * Make mNumRuns a uint32_t on all platforms. Differential Revision: https://phabricator.services.mozilla.com/D140036
-
Paul Bone authored
This code path would choose from several ways about how to divide numbers. By calculating the inverse of the divisor early we can elude all the branches along this code path we can make it faster than the previous code or naive division. Differential Revision: https://phabricator.services.mozilla.com/D132322
-
Chris Peterson authored
Bug 1804375 - Re-enable clang's -Wimplicit-fallthrough warnings in gfx code including Skia headers. r=gfx-reviewers,lsalzman Bug 1236323 disabled clang's -Wimplicit-fallthrough warnings from some Skia headers, but this warning can be re-enabled because the current version of Skia doesn't trigger these warnings. Depends on D164027 Differential Revision: https://phabricator.services.mozilla.com/D164028
-
Chris Peterson authored
Bug 1804375 - Re-enable clang -Wnull-dereference warnings in gtest. r=firefox-build-system-reviewers,glandium Bug 1324242 disabled clang's -Wnull-dereference warnings in gtest code, but this warning can be re-enabled because the current version of gtest doesn't trigger these warnings. Differential Revision: https://phabricator.services.mozilla.com/D164027
-
Mike Hommey authored
Bug 1804548 - Fail early when trying to cross-compile with wasm sandboxing on Windows. r=firefox-build-system-reviewers,nalexander Differential Revision: https://phabricator.services.mozilla.com/D164136
-
Masayuki Nakano authored
Bug 1803044 - part 9: Make the style editor use existing inline element in the CSS mode as far as possible r=m_kato The other browsers use any inline elements to set CSS property for applying an inline style. However, Gecko limits it to a `<span>` which does not have any attributes. The other browsers' design is better for saving number of elements and runtime cost of inserting new element (moving all children to the new element and inserting it to the original position). Therefore, it's nicer to follow the other browses. Then, we can avoid new WPT failures at aligning other behaviors to the other browsers. With doing that, removing style code requires complicated changes because `RemoveStyleInside` assumes that one element has one style, but after taking the compatible behavior, one element can have multiple styles including the style represented by the element itself. Note that the new expected failures are caused by bug 1183844. Gecko returns closest ancestor element's background color for `queryCommandValue("backColor")`. Therefore, it returns "transparent" of the inner `<span>` element. Differential Revision: https://phabricator.services.mozilla.com/D164004
-
Masayuki Nakano authored
Now, we can make there simpler because the part does one of them: * Replaces element with new `<span>` * Removes element * Removes attribute * Does nothing However, there are duplicated code. We should consider what there does with lambdas. Depends on D164002 Differential Revision: https://phabricator.services.mozilla.com/D164003
-
Masayuki Nakano authored
Bug 1803044 - part 7: Make `HTMLEditor::RemoveStyleInside` use `HTMLEditor::ReplaceContainerWithTransaction` r=m_kato Depends on D164001 Differential Revision: https://phabricator.services.mozilla.com/D164002
-
Masayuki Nakano authored
Bug 1803044 - part 6: Make `HTMLEditor::RemoveStyleInside` remove CSS style before touching the DOM tree structure r=m_kato This change makes the following changes smaller. Once we remove CSS style first, then, it becomes easier to consider whether we should delete the element since `style` attribute may be deleted by `ChangeStyleTransaction` if the removing style is the last rule in it. Depends on D164000 Differential Revision: https://phabricator.services.mozilla.com/D164001
-
Sergey Galich authored
Bug 1805060 - Using Assert.ok()/Assert.equal() instead of ok()/is() in from history browser tests r=mconley,dimi Differential Revision: https://phabricator.services.mozilla.com/D164412
-
Sergey Galich authored
Bug 1805059 - Using Assert.ok()/Assert.equal() instead of ok()/is() in password manager browser and unit tests r=mconley,dimi Differential Revision: https://phabricator.services.mozilla.com/D164411
-
Sergey Galich authored
Bug 1805054 - Using Assert.ok()/Assert.equal() instead of ok()/is() in about:logins browser tests r=mconley,dimi Differential Revision: https://phabricator.services.mozilla.com/D164410
-
Sergey Galich authored
Bug 1751763 - Firefox Relay integration r=dimi,flod,mconley,desktop-theme-reviewers,dao,sfoster,geckoview-reviewers,jonalmeida Differential Revision: https://phabricator.services.mozilla.com/D158155
-
Masayuki Nakano authored
Bug 1803044 - part 5: Make `HTMLEditor::RemoveStyleInside` check whether aElement is editable first r=m_kato Depends on D163999 Differential Revision: https://phabricator.services.mozilla.com/D164000
-
Daisuke Akatsuka authored
Differential Revision: https://phabricator.services.mozilla.com/D164427
-
Masayuki Nakano authored
Bug 1803044 - part 4: Make `HTMLEditor::SetAttributeOrEquivalent` insert a white-space only when old value is empty r=m_kato This causes some new failures after applying the following patches. Depends on D163998 Differential Revision: https://phabricator.services.mozilla.com/D163999
-