Compatibility mode somehow different than options flipped to match

ehlo

It appears that turning on "compatibility mode" is somehow different than manually flipping each of the options described in the help tool tip for compantibility mode (the clickable question mark icon).

Steps to reproduce:
This is a little tricky to describe because the site that I'm using, toggl.com, has a very javascript specific issue that has stopped working. I was trying to determine which of the compatibility settings caused it to break when I came across this other problem.

With compatibility mode off, visit the website with compatibility issue
Note the issue is present
Enable compatibility mode
Note the issue is resolved
Disable compatibility mode
Note the issue is not resolved, again.
Now, disable content blocker and tracking prevention. Enable javascript and cookies. Change user agent to Safari.
Note the issue is not resolved.

Expected behavior:
With compantibility mode disabled, disabling content blocker and tracking prevention and enabling javavascript and cookies and changing user agent to Safari is expected to be the same as enabling compatibility mode.

Orion, OS version; hardware type:

Orion: Version 0.99.120.1-beta (WebKit 614.1.20)
macOS: 12.6 (21G115)

Image/Video:
Happy to provide imagry or video if somehow it would help.

eirk

Putting a website into Compatibility Mode will:
Disable content blocking
Disable tracking prevention
Disable web fonts blocking
Enable cookies
Use the Safari user agent
Disable all browser extensions

did you do all of these too?

ehlo

eirk Yes, here's a screenshot of it and I don't have any extensions installed. With these settings the js issue I'm observing is still present, but enabling compatibility mode itself will resolve it. Is there anything else that is changed in compatibility mode?

Vlad

ehlo And the site to reproduce this is toggl.com and what is the issue / how can we reproduce the problem?

ehlo

Vlad Yes, it's toggl.com. It's a really odd js/dom/something issue. I finally thought of a way to create a video without showing the data in my account.

The observed issue has to do with the dropdown and typing in the little search bar. When it is working the list should shrink to only show the matches. When I enable compatibility mode it will start to work.

However, strangly, if I keep compatibility mode disabled and attempt to change all the settings that compatibility mode is supposed to change, it still doesn't work.

With compatibility mode disabled:

With compatibility mode enabled:

I should note that I normally keep toggl.com in a pinned tab, but that doesn't seem to be related.

Vlad

ehlo I wonder if you can replicate this in some other place that does not require an account to reproduce?

ehlo

Vlad I will keep a look out

ehlo

Vlad I dug into this a little and found some interesting stuff in the console. My guess is they must have unfortunately tied some part of the JS to reporting to firebase.google.com and it is failing siliently with content blocking on.

With compatibility mode disabled and the other settings at their default, this shows up in the console:

[Info] Content blocker prevented frame displaying https://track.toggl.com/timer from loading a resource from https://firebaselogging-pa.googleapis.com/v1/firelog/legacy/log?key=AIzaSyCx80ru6-RXeTi3GvqkFsMVyMf-vpgIoVw (670.6df20bad3faf7955.js, line 2)
[Info] [2022-10-21T15:24:10.583Z]  Performance: – "Tries left: 2." (670.6df20bad3faf7955.js, line 2)
[Info] Content blocker prevented frame displaying https://track.toggl.com/timer from loading a resource from https://o43910.ingest.sentry.io/api/4503936890568704/envelope/?sentry_key=f65ec02900844101800a77122d491b4e&sentry_version=7&sentry_client=sentry.javascript.react%2F7.15.0 (670.6df20bad3faf7955.js, line 2)
[Info] Content blocker prevented frame displaying https://track.toggl.com/timer from loading a resource from https://firebaselogging-pa.googleapis.com/v1/firelog/legacy/log?key=AIzaSyCx80ru6-RXeTi3GvqkFsMVyMf-vpgIoVw (670.6df20bad3faf7955.js, line 2)
[Info] [2022-10-21T15:24:20.587Z]  Performance: – "Tries left: 1." (670.6df20bad3faf7955.js, line 2)
[Info] Content blocker prevented frame displaying https://track.toggl.com/timer from loading a resource from https://firebaselogging-pa.googleapis.com/v1/firelog/legacy/log?key=AIzaSyCx80ru6-RXeTi3GvqkFsMVyMf-vpgIoVw (670.6df20bad3faf7955.js, line 2)
[Info] [2022-10-21T15:24:30.589Z]  Performance: – "Tries left: 0." (670.6df20bad3faf7955.js, line 2)

However, if I leave compatibility mode disabled and also manually disable content blocker and/or intelligent tracking prevention, the problem is still present and those same log messages are there — so, something seems different between manually changing the settings and using compatibiliy mode.

As an aside, unexpectedly, the content blocker doesn't block a request to firebase.googleapis.com while it does block firebaselogging-pa.googleapis.com.

https://firebase.googleapis.com/v1alpha/projects/-/apps/1:744884606549:web:1e7b92771f31bd9c/webConfig

ehlo

In my last comment, I had assumed that I would see similar log entries (the "Tries left" entries) whether with Compatibillity mode disabled or by manually disabling content blocking and intelligent tracking prevention.

However, I do not see those entries when with manually disabling options. In fact, I don't see any appreciable differences between the logs. Yet, the javascript issue I described is still there.

This comes back to my original report and curiosity – compatibility mode seems to be doing more than just disabling content blocking and intelligent tracking.

Vlad

ehlo Compatibility mode also disables all web-extensions related scripts for page which is extra from the other checkboxes available.

mchung

Steps to reproduce:

Go on any video calling services
Enable Compatiability mode in order to use snapchat web

However, following what the compability mode settings WITHOUT turning on compatibility mode (e.g. turning off content-blcoker, tracking prevention, enable cookies, using safari user-agent) does not work on snapchat web which causes a loading screen that's stuck

Expected behavior:
Use snapchat web without the use of compatibility mode

Orion, OS version; hardware type:
Version 0.99.124.4.1-beta (WebKit 616.1.14.11.1)

Vlad

mchung compatibility mode also disables extensions

mchung

I have also disabled all extensions and it doesn't seem to work at all

mchung

I figured out the problem, it was the Grammarly extension that affected the use of snapchat web. The Chrome extension for grammarly might be broken for certain websites