testInbound #125
Merged
testInbound #125
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…s offsets. r=kats The current code is wrong in several ways when transforms are applied, but even if it were correct, it would give the wrong behavior. See comment in patch for more details. MozReview-Commit-ID: 3RaPuvENnWa --HG-- extra : rebase_source : 25aab67e56f157bdfa500aa7cf029c6ebe90e12a extra : absorb_source : 4da2fd9f11e008b7b70b86b184ade673a68e6978
…r=zombie MozReview-Commit-ID: BuAjyqg1aja --HG-- extra : rebase_source : 03b7368659ccdb39ebedf7aeb6a1902b6abe5808 extra : amend_source : 53eadbc91f2468b8d116cf0e5bf457fd7107bfb8 extra : absorb_source : 379f778671c868a08f560663f31e6248872c7989
… ImageBridgeChild was also reinitialized. r=sotaro
…d if the GPU process reuses its PID. r=dvander
…des have been removed; r=gl MozReview-Commit-ID: 45fHGmuKhkD
… r=dolske MozReview-Commit-ID: LOpGanTIIpm
…ce. r=trivial MozReview-Commit-ID: Css0qzakw14
…eloaders in popup widgets. r=kats On-screen coordinates for points in remote frameloads are calculated relative to the screen origin of the top-level window, while event coordinates are calculated relative to the nearest widget. Since popups have their own widgets separate from the top-level window, their native client offsets have no particular relation to the origin of the top-level window, and we need to manually calculate them relative to the origin of the top-level widget instead. MozReview-Commit-ID: EDyEyu37XuY --HG-- extra : rebase_source : 5d3f7a3fb9518d7a0cf149b8c2f579805d75eb3b extra : absorb_source : f48ee4b131ff67ae686d12f81ed2ad19b934e81e
…ng with js::GetInitDataPropAttrs(JSOp) in devtools tests on Windows, e.g. browser_rules_edit-selector_04.js. r=backout
…g devtools' browser_grids_grid-list-on-iframe-reloaded.js. r=backout
…nt issues. MozReview-Commit-ID: 9GfteuwKeTb
…des have been removed; r=gl MozReview-Commit-ID: 45fHGmuKhkD
…nt intermittent failures. MozReview-Commit-ID: GiHc1OVMFEh
…g devtools' browser_grids_grid-list-on-iframe-reloaded.js with "There's no highlighter shown". r=backout
moz-v2v-gh
pushed a commit
that referenced
this pull request
Sep 11, 2020
https://github.com/mozilla/authenticator-rs/releases/tag/v0.3.0 Major changes: * Move to Rust 2018 edition #125 * Remove dependency on boxfnonce #121 * Reworked error handling #130 * Added a higher-level AuthenticatorService that can use multiple backends #123 * Changed the C API to use the new AuthenticatorService #123 * Added a Status channel for backends #122 * Now obtaining HID report sizes from the descriptors #12 * Add authenticator USB and Firmware details to the C API #93 Differential Revision: https://phabricator.services.mozilla.com/D89823
bvaughn
pushed a commit
to bvaughn/gecko-dev
that referenced
this pull request
Apr 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.