Whitelisted website with iframe (interactive code editors) do not load the iframe on macOS only.

[dullin]

Using the Moodle exam activity (Moodle version 4.1) activity to generated the the SEB configuration file (uploaded here). The exam permits student to use of the Mozilla developper network site (https://developer.mozilla.org/en-US/* in the configuration).
On macOS computers, when going on pages with iframes (ex: https://developer.mozilla.org/en-US/docs/Web/CSS/box-sizing ), the iframe does not load. I made sure to not check the embedded content filter to permit these types of iframe. Another example is the playground section ( https://developer.mozilla.org/en-US/play ) where clicking the Run button doens't update the iframe on the right of the page.

Steps to reproduce the behavior:

1. Use the Seb configuration file on macOS
2. Go to https://developer.mozilla.org/en-US/play
3. Write some HTML in the provided box on the left
4. Click Run
5. See that the HTML is not rendered on the iframe on the right of the page.

Expected behavior
iframes should be loaded when embedded content is allowed. This works for SEB on Windows machines.

Version Information

• OS: Sonoma 14.5 (23F79)
• SEB Version SEB 3.3.2 for macOS

Additional Context
This happened on all students with macOS machines and none that were on Windows machines. Uploaded here is the config file generated by Moodle and a log of my own attempt where I navigate to the MDN Play site and another playground that was supposed to be available but also did not work on macOS ( https://dullin.github.io/TCH056/diapos/playground/ )

config.seb.zip
org.safeexambrowser.SafeExamBrowser 2024-05-28--15-08-28-679.log.zip

[danschlet]

Steps to reproduce the behavior:

Use the Seb configuration file on macOS
Go to https://developer.mozilla.org/en-US/play
Write some HTML in the provided box on the left

Please provide some sample HTML for fully valid steps to reproduce!

Click Run
See that the HTML is not rendered on the iframe on the right of the page.

[dullin]

Any HTML wasn't working.

A simple example that didn't work:

<h1>Test</h1>

[danschlet]

I still need steps to reproduce and a SEB configuration file which I can click and try it out. People report issues and it turns out they didn't configure SEB correctly or another component caused the issue. Therefore we MUST have an easily and efficiently reproducible issue report.

You probably can't imagine how many issues we have to work through (there are now probably dozens if not hundreds of millions of SEB exams taken). We're still a nonprofit organization and don't have enough human resources to process each issue that gets reported.

Therefore if you want issues which you report to be handled quickly (or at all), you have to provide a one-click reproducible example.