Cal Video fails to load in Firefox 148 with Enhanced Tracking Protection enabled

[hrisant]

Found a bug? Please fill out the sections below. 👍

Issue Summary

For an interview I was given a link from cal.com.
While trying to connect I arrived at a page that looked like waiting for the meeting to start screen, especially for someone who uses the platform for the first time, like me. So I waited thinking I would join the interview but that did not happen. The interview was rescheduled, no worries but still it was a weird experience

Steps to Reproduce

System:
OS: Windows 10
Browser: Firefox 148.0.2 with "Enhanced Tracking Protection" on

1. Went to https://app.cal.com/video/[identifier]

2. Introduced my name and clicked ""Join call as guest"

3. Next page(same url) looks like a waiting page, only dsplaying Cal.com and a pulsating circle, which is confusing

4. Console errors:
   "Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://meetco.daily.co’) does not match the recipient window’s origin (‘https://app.cal.com’). 6ZYNjqiKZGPdK3iEZv7DNA
   Uncaught (in promise) DOMException: The operation is insecure."
   So I presume it is a cross origin access issue.

5. Upon disabling ""Enhanced Tracking Protection" on Firefox (or using Chrome or Firefox 140.8.0esr) the page fully loaded.
   Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

I also reported this to Firefox from the menu related to Enhanced Tracking Protection(the shield near the url).

Actual Results

• What's happening right now that is different from what is expected

Expected Results

• This is an ideal result that the system should get after the tests are performed

Technical details

Full console output:

<< query #2 viewer.teams.hasTeamPlan
Object { input: undefined, result: TRPCClientError, elapsedMs: 355, context: {} }
console.ts:38:50
eW console.ts:38
n loggerLink.mjs:126
a loggerLink.mjs:157
error loggerLink.mjs:169
error operators.mjs:86
error observable.mjs:41
error observable.mjs:41
error observable.mjs:41
e0 createHTTPBatchLink.mjs:60
<< query #3 viewer.me.get
Object { input: undefined, result: TRPCClientError, elapsedMs: 354, context: {} }
console.ts:38:50
eW console.ts:38
n loggerLink.mjs:126
a loggerLink.mjs:157
error loggerLink.mjs:169
error operators.mjs:86
error observable.mjs:41
error observable.mjs:41
error observable.mjs:41
e0 createHTTPBatchLink.mjs:60
Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://meetco.daily.co’) does not match the recipient window’s origin (‘https://app.cal.com’). 6ZYNjqiKZGPdK3iEZv7DNA
Uncaught (in promise) DOMException: The operation is insecure.
<< query #6 viewer.me.get
Object { input: undefined, result: TRPCClientError, elapsedMs: 249, context: {} }
console.ts:38:50
eW console.ts:38
n loggerLink.mjs:126
a loggerLink.mjs:157
error loggerLink.mjs:169
error operators.mjs:86
error observable.mjs:41
error observable.mjs:41
error observable.mjs:41
e0 createHTTPBatchLink.mjs:60
<< query #5 viewer.teams.hasTeamPlan
Object { input: undefined, result: TRPCClientError, elapsedMs: 266, context: {} }
console.ts:38:50
eW console.ts:38
n loggerLink.mjs:126
a loggerLink.mjs:157
error loggerLink.mjs:169
error operators.mjs:86
error observable.mjs:41
error observable.mjs:41
error observable.mjs:41
e0 createHTTPBatchLink.mjs:60
<< query #8 viewer.teams.hasTeamPlan
Object { input: undefined, result: TRPCClientError, elapsedMs: 189, context: {} }
console.ts:38:50
eW console.ts:38
n loggerLink.mjs:126
a loggerLink.mjs:157
error loggerLink.mjs:169
error operators.mjs:86
error observable.mjs:41
error observable.mjs:41
error observable.mjs:41
e0 createHTTPBatchLink.mjs:60
<< query #9 viewer.me.get
Object { input: undefined, result: TRPCClientError, elapsedMs: 202, context: {} }
console.ts:38:50
eW console.ts:38
n loggerLink.mjs:126
a loggerLink.mjs:157
error loggerLink.mjs:169
error operators.mjs:86
error observable.mjs:41
error observable.mjs:41
error observable.mjs:41
e0 createHTTPBatchLink.mjs:60

Evidence

• How was this tested? This is quite mandatory in terms of bugs. Providing evidence of your testing with screenshots or/and videos is an amazing way to prove the bug and a troubleshooting chance to find the solution.