Disable flay context menu test on macOS

[simonhong]

issue: brave/brave-browser#42232

Resolves

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• 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 wiki
  • npm run presubmit wiki, 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:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

[cdesouza-chromium]

Is this test going to just be permanently disabled for macOS then?

[simonhong]

Is this test going to just be permanently disabled for macOS then?

I think disabling on macOS is fine as it's cross platform feature.
We could investigate later. This PR is for unlocking other PR merging.
Or, should we revert original PR?

[cdesouza-chromium]

Is this test going to just be permanently disabled for macOS then?

I think disabling on macOS is fine as it's cross platform feature. We could investigate later. This PR is for unlocking other PR merging. Or, should we revert original PR?

Would you mind creating a ticket then for it? I understand you are swamped lately, but having a ticket might help revisiting it.

[brave-builds]

Released in v1.75.13

[wknapik]

@simonhong should brave/brave-browser#42232 be resolved?

[simonhong]

Is this test going to just be permanently disabled for macOS then?

I think disabling on macOS is fine as it's cross platform feature. We could investigate later. This PR is for unlocking other PR merging. Or, should we revert original PR?

Would you mind creating a ticket then for it? I understand you are swamped lately, but having a ticket might help revisiting it.

Yup, filed brave/brave-browser#42252

[simonhong]

@simonhong should brave/brave-browser#42232 be resolved?

Closed.