bromite
bromite copied to clipboard
arm64 bromite/webview navigator.platform return wrong value
Preliminary checklist
- [X] I have read the README.
- [X] I have searched the existing issues for my problem. This is a new ticket, NOT a duplicate or related to another open issue.
- [X] I have read the FAQs.
- [X] I have updated Bromite to the latest version. The bug is reproducible on this latest version.
- [X] This is a bug report about the Bromite browser; not the website nor F-Droid nor anything else.
Can the bug be reproduced with corresponding Chromium version?
No
Bromite version
104.0.5112.91
Device architecture
arm64-v8a
Android version
12.1
Device model
Pixel 4 XL
Changed flags
no flags changed
Is this bug about the SystemWebView?
Yes
Is this bug happening in an incognito tab?
Yes
Is this bug caused by the adblocker?
No
Is this bug a crash?
No.
Describe the bug
navigator.platform return armv8l on arm64 Bromite, not aarch64
Steps to reproduce the bug
https://www.quanzhanketang.com/jsref/tryjsref_nav_platform.html?filename=tryjsref_nav_platform
Expected behavior
return aarch64
Screenshots
This happens when you install the armv8 APK.
This happens when you install the armv8 APK.
Vanilla Chromium/Google Chrome/Firefox will return Linux aarch64. As far as I know, armv8l is 64bit kernel+32bit ELF, and the Bromite of arm64 should be 64bit
I observe the same value with Vanilla Chromium, Linux armv81
. It means that the Chromium/Bromite ELFs are 32bit.
I observe the same value with Vanilla Chromium,
Linux armv81
. It means that the Chromium/Bromite ELFs are 32bit.
I installed Vanilla Chromium on Pixel 4 XL ProtonAOSP. the navigator.platform return Linux aarch64
.
I cannot reproduce this; I think that the APK contains both versions and the appropriate one is automatically used. @uazo @wchen342 @chirayudesai do you know about this?
Disable chrome://flags/#reduce-user-agent, problem solved. https://chromestatus.com/feature/5098783126323200 This seems to be expected behavior in the future?
ReduceUserAgent
is enabled by default in Bromite, so this is already expected behaviour. I assume that my test with Chromium is invalid for some other reason.