fix: Disable context-menu on right-click in TinyMCE

[xitij2000]

The context menu in the TinyMCE editor only displayed a "Link" option but as a result disabled the browser-native context menu which includes more useful actions. This change disables the context menu.

What changed?

• TinyMCE's default context menu is disabled

Developer Checklist

• Reviewed the release process
• Translations and JS/SASS compiled
• Bumped version number in openassessment/__init__.py and package.json

Testing Instructions

Install the XBlock and see that the context menu in TinyMCE is disabled.

Reviewer Checklist

Collectively, these should be completed by reviewers of this PR:

• I've done a visual code review
• I've tested the new functionality

FYI: @openedx/content-aurora

[openedx-webhooks]

Thanks for the pull request, @xitij2000!

This repository is currently maintained by @openedx/2u-aurora.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.29%. Comparing base (628d44f) to head (075a0b8).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2289   +/-   ##
=======================================
  Coverage   95.29%   95.29%           
=======================================
  Files         195      195           
  Lines       21663    21663           
  Branches     1509     1509           
=======================================
  Hits        20643    20643           
  Misses        771      771           
  Partials      249      249           

Flag	Coverage Δ
unittests	95.29% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pomegranited]

Hi @xitij2000 , ping me on the Jira ticket if you need help getting this merged? I'm CC on this repo.

[kaustavb12]

👍

• I tested this: Tested in local setup
• I read through the code

[itsjeyd]

@xitij2000 Now that this change has product approval, could you please resolve merge conflicts here and fix the failing tests so we can put this up for a final round of review?

[xitij2000]

@itsjeyd I've resolved the issue, but the test failures seem to be unrelated. Will push again so check.

[xitij2000]

The tests seems to pass locally but fail here. This particular test seems to be flaky since it's also failing on other PRs. I'll push again and see how it goes.

[pomegranited]

@xitij2000 JS tests are always flaky.. I'll re-run.

[itsjeyd]

Hey @pomegranited! 🙂 👋 It looks like we got a green build here. Let us know when you'd be able to give this a final look?

[itsjeyd]

@pomegranited Do you think you'll have time to come back to this PR in the coming days? Happy to ping someone else for final 👍 if not; just let me know.

[itsjeyd]

Hi @openedx/2u-aurora team, could you please help get this small PR merged?

[itsjeyd]

Hi @openedx/committers-edx-ora2, we still need a review on this small PR. Could one of you please help get it merged?

[itsjeyd]

@openedx/axim-engineering There seem to be no takers for reviewing this PR at the moment (I also posted on Slack about it last week).

It has been waiting for engineering review since early August, so I was wondering if one of you could help with getting it over the line?

[brian-smith-tcril]

The context menu in the TinyMCE editor only displayed a "Link" option but as a result disabled the browser-native context menu which includes more useful actions. This change disables the context menu.

I just want to confirm we aren't losing any functionality here. Is there still a way to add a link after this change?

[xitij2000]

The context menu in the TinyMCE editor only displayed a "Link" option but as a result disabled the browser-native context menu which includes more useful actions. This change disables the context menu.

I just want to confirm we aren't losing any functionality here. Is there still a way to add a link after this change?

There are alternative ways to add links using the toolbar or shortcuts. The feature as-is takes over the default browser context menu and as such masks any features and functionality provided by the browsers, so if anything this change to restore browser features that are curretly obscured.

[brian-smith-tcril]

There are alternative ways to add links using the toolbar or shortcuts.

I figured that was the case but just wanted to verify and document that on this PR.

The last question I have here is about the developer checklist part of the PR template. I see it mentions bumping the version in package.json and this PR doesn't do that. Is that an outdated requirement or just something missed in this PR?

[xitij2000]

The last question I have here is about the developer checklist part of the PR template. I see it mentions bumping the version in package.json and this PR doesn't do that. Is that an outdated requirement or just something missed in this PR?

I've updated the version in package.json. sorry for missing that step.

[brian-smith-tcril]

LGTM!

[itsjeyd]

Thanks a lot for jumping in here @brian-smith-tcril!

Neither @xitij2000 nor I have merge rights for this repo, so if you could it the button for us when you're ready, that would be great.