Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add force paste option to context menu #13178

Merged
merged 3 commits into from
Jun 6, 2022
Merged

add force paste option to context menu #13178

merged 3 commits into from
Jun 6, 2022

Conversation

bridiver
Copy link
Collaborator

@bridiver bridiver commented Apr 26, 2022

Resolves brave/brave-browser#22567

Submitter Checklist:

  • I confirm that no security/privacy review is needed, or that I have requested one
  • There is a ticket for my issue
  • Used Github auto-closing keywords in the PR description above
  • Wrote a good PR/commit description
  • Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
  • Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
  • Checked the PR locally: npm run test -- brave_browser_tests, npm run test -- brave_unit_tests, npm run lint, npm run gn_check, npm run tslint
  • Ran git rebase master (if needed)

Reviewer Checklist:

  • A security review is not needed, or a link to one is included in the PR description
  • New files have MPL-2.0 license header
  • Adequate test coverage exists to prevent regressions
  • Major classes, functions and non-trivial code blocks are well-commented
  • Changes in component dependencies are properly reflected in gn
  • Code follows the style guide
  • Test plan is specified in PR before merging

After-merge Checklist:

Test Plan:

@bridiver bridiver requested a review from a team as a code owner April 26, 2022 19:21
Copy link
Contributor

@pes10k pes10k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, with minor nit comment sent on slack

// only enable if there is plain text data to paste - this is what
// IsPasteAndMatchStyleEnabled checks internally, but IsPasteEnabled
// allows non text types
return IsPasteAndMatchStyleEnabled();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it seems we don't actually have tests for this class, but they could be useful

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, I've been waiting to merge this because I need to add tests

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems there are no upstream paste tests so I'm going to leave this for now and maybe do a follow-up

@bridiver bridiver force-pushed the issues/22567 branch 2 times, most recently from 5b4f870 to 576a1f5 Compare June 1, 2022 19:38
@bridiver
Copy link
Collaborator Author

bridiver commented Jun 6, 2022

unrelated test error that didn't happen on previous runs

@bridiver bridiver added this to the 1.41.x - Nightly milestone Jun 6, 2022
@bridiver bridiver merged commit 890c13d into master Jun 6, 2022
@bridiver bridiver deleted the issues/22567 branch June 6, 2022 19:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add "Force paste" option that bypasses onpaste handlers
3 participants