Repository navigation
Adaptive Page Action visibility - #10
Merged
Merged
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 127 |
| Duplication | 10 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
This file contains hidden or 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
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.
What does this PR do?
Adaptive Page Action visibility:
navigator.hid.Related issue(s)
Close #9
Type of change
Testing
Manually tested on browser
Rust (daemon, NM host, mock)
cargo build --releasepasses, if the change touches Rust codenpm run lint:rs(cargo clippy) passes with no new warningsnpm run test:rspassesreport descriptor parsing, or the data plane
Addon (JS)
npm run lint:jsandnpm run lint(web-ext) passnpm run test:browserpasses (no hardware needed)npm run test:e2epasses if the change touches the data plane orworker-spawn paths (see E2E setup note below)
npm run test:benchmarkif the change affects throughput or latencyChecklist
BENCHMARK.md) if needed