Broken webpage (aistudio.google.com)

[lakshay487]

Preliminary checklist

• I have read the README.
• I have searched the existing issues for my problem. This is a new ticket, NOT a duplicate or related to another open issue.
• I have read the FAQs.
• I have updated Cromite to the latest version. The bug is reproducible on this latest version.
• This is a bug report about the Cromite browser; not the website nor F-Droid nor anything else.

Can the bug be reproduced with corresponding Chromium version?

No

Are you sure?

Yes

Cromite version

132.0.6834.122

Device architecture

arm64-v8a

Platform version

Android 12

Android Device model

RMP2107

Is the device rooted?

No

Changed flags

no flags changed

Is this bug happening ONLY in an incognito tab?

No

Is this bug caused by the adblocker?

No

Is this bug a crash?

No.

Describe the bug

Adblocker and userscript are disabled, I also tried enabling JavaScript JIT (after going through the faqs) but the page is still broken.
There are no such issues in brave, even on agressive adblocking mode.
https://github.com/user-attachments/assets/322ed032-13d1-4238-9d35-e39d60a70da3

Steps to reproduce the bug

Go to https://aistudio.google.com/prompts/new_chat

Expected behavior

Obvious.

Screenshots

No response

[uazo]

it is more than likely the anti-ads rules, try disabling adblock.

[lakshay487]

Adblock was already disabled.

Details

[itsmartashub]

Same issue. Removed all the blockers on the phone I have, even private DNS is turned off, and still some website are not usable, for example Deepseek chat. While in Brave, with all ad blockers and private DNS turned on, everything works...

[lakshay487]

@uazo ?

[mnb21]

Other site is also broken - pro.kraken.com/app
JIT enabled, Webgl enabled, Adblock disabled - still cannot load.
Chromium can load it.

[uazo]

the problem is related to your adblock rules.

disable it from "page info":

[lakshay487]

"Intrusive ads" from "page info" are allowed, I already shared the screenshot showing that.

[uazo]

you should check the behaviour using the chromium developer tools, alternatively you can send the generated file with chrome://net-export for an analysis of what is being blocked.

[lakshay487]

It was "JavaScript JIT" that was causing this problem. I must have forgotten to refresh the page when I first tried enabling it. Thanks for your help and I apologise for wasting your time.