Non-Latin and non-Cryillic text is broken.

[LellyTheTeapot]

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 Cromite to the latest version. The bug is reproducible on this latest version.
• [X] 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?

No

Cromite version

123.0.6312.105

Device architecture

arm64-v8a

Platform version

Android 14

Android Device model

Pixel 6a

Is the device rooted?

No

Changed flags

no flags changed

Is this bug happening in an incognito tab?

No

Is this bug caused by the adblocker?

No

Is this bug a crash?

No.

Describe the bug

Any non-Latin or non-Cryillic text us rendered as thin crossed boxes, likely caused by the embedded fonts in #935 not supporting it.

Steps to reproduce the bug

Demonstrated easiest by using any site that uses CJK text like jisho.org.

Expected behavior

Text should display appropriate scripts as normal.

Screenshots

Details


[islam2hamy]

Arabic also

[apardogi]

Same problem here for Japanese text as shown above.

[DeepBlueBubble]

Simplified and Traditional Chinese is broken too

[uazo]

Any non-Latin or non-Cryillic text us rendered as thin crossed boxes, likely caused by the embedded fonts in https://github.com/uazo/cromite/pull/935 not supporting it.

yes, it's my fault. i didn't think about those characters.

could you give me some sites to check?

[islam2hamy]

Any non-Latin or non-Cryillic text us rendered as thin crossed boxes, likely caused by the embedded fonts in #935 not supporting it.

yes, it's my fault. i didn't think about those characters.

could you give me some sites to check?

https://f-droid.org/ just change site language

[MahdiAhmadnejad]

Hi this is for persian

Details


[uazo]

OK, thanks, I will do a partial revert.

[someftierguy]

Greek characters work fine

Details


[muhammadkarodia]

Arabic also

Same here

[calvin2021y]

Can not install old version(install will failure), and can not read any non Latin pages. this is disaster.

[ABCCOMPANYPOHARKA]

Details


What 😨 happened... After update???

[drogga]

@calvin2021y I can install older versions with MT Manager, which uses Shizuku to downgrade (you will have to remove MT M. from the recents or even force stop it in order to start using Shizuku for the installation, else it won't be able to downgrade), other packages retain their data, so in theory Cromite should too, you can also try InstallWithOptions, InstallerX, manually using the -d & -r params or just wait for an update, which shouldn't take long.

[cvtsi2sd]

Cromite 123.0.6312.105 from F-Droid on Android 8.1.0, ARMv7 build. The situation here is even worse: apparently as soon as the browser needs to render one of the missing glyphs, the whole page crashes

Details


I can reproduce this trivially: if I paste a Chinese character in this (or any website) textbox, the page crashes; same e.g. if I open the "other languages" menu on Wikipedia, or visit any site containing Chinese glyphs.

[wreaver]

I study Japanese and visit pages that use it. I don't mean to pressure but Cromite is unusable for me now, unfortunately.

[uazo]

thank you all for the various reports.

you can deactivate the feature with chrome://flags/#fonts-fingerprint-mitigation (Enable fonts fingerprint mitigation (Cromite flag)) set to off

[cvtsi2sd]

At least for my problem, the workaround doesn't seem to work, probably the crash comes from something that isn't disabled by the flag.

[calvin2021y]

adb install -r -d arm64_ChromePublic.apk 
Performing Streamed Install
adb: failed to install arm64_ChromePublic.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE: Downgrade detected: Update version code 631208604 is older than current 631210504]

not work for me

[calvin2021y]

chrome://flags/#fonts-fingerprint-mitigation this work

[islam2hamy]

thank you all for the various reports.

you can deactivate the feature with chrome://flags/#fonts-fingerprint-mitigation (Enable fonts fingerprint mitigation (Cromite flag)) set to off

thank you

[apardogi]

It did work for me. I disabled the flag, relaunched and then erased the cache. After that I started to get Japanese text displayed correctly again.

Thank you!

[nordicw0lf]

thank you all for the various reports.

you can deactivate the feature with chrome://flags/#fonts-fingerprint-mitigation (Enable fonts fingerprint mitigation (Cromite flag)) set to off

I cant see that flag when I search for it

Details


The bug is also affecting hebrew

Details


[cvtsi2sd]

I cant see that flag when I search for it !

Search doesn't seem to work for Cromite flags, you have to go explicitly in the "Cromite" tab and look for it.

[cvtsi2sd]

I tried making my own build of Cromite without the font patches and, while it did succeed (in 7 hours of compilation, wow), I still can't install it over my current Android installation, as the signature doesn't match; I guess that's because the official releases use a specific certificate that is not available in the public repo? Any way I can workaround this/produce an official build without those patches?

[alisonatwork]

@nordicw0lf I had the same problem. You need to select Cromite tab (on the right) and the setting is in there. Workaround works for me.

[avipars]

I tried making my own build of Cromite without the font patches and, while it did succeed (in 7 hours of compilation, wow), I still can't install it over my current Android installation, as the signature doesn't match; I guess that's because the official releases use a specific certificate that is not available in the public repo? Any way I can workaround this/produce an official build without those patches?

That's the point of these certificates... only the original owner/creator with the private keys can publish a new official version.

You can make your own set of keys and sign the apk with them... then you can uninstall their chromite apk, and install your own.

As for release, you should make a pull request and ask the project owner to integrate it and make a build.

[avipars]

adb install -r -d arm64_ChromePublic.apk 
Performing Streamed Install
adb: failed to install arm64_ChromePublic.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE: Downgrade detected: Update version code 631208604 is older than current 631210504]

not work for me

Uninstall the original apk and then try again

[GfEW]

@uazo

you can deactivate the feature with chrome://flags/#fonts-fingerprint-mitigation (Enable fonts fingerprint mitigation (Cromite flag)) set to off

Because of obvious similarities, I'd like to also test this workaround against #971 which is different in that there, even chrome://flags is unreadable due to font placeholders, so I've tried to identify and disable the flag #fonts-fingerprint-mitigation blindly:

Screenshot 1

 _(Note that in this screenshot, the search box is really empty, the placehoders there only represent the inactive, normally greyed-out search hint.)_

Apparently, this shows many flags. Let's search for the string 'font':

Screenshot 2

 _(In this screenshot, the four placeholders in the search box represent real contents, namely the entered letters 'f' 'o' 'n' 't'.)_

The shape of those placeholder lines suggests there's only one search result, and according to the same search conducted in an unaffected cromium instance (same v123.0.6312.105 on another device), that one search result is #enable-fontations-backend!

Details

~So, there doesn't seem to be a `#fonts-fingerprint-mitigation` flag in my instances of cromite v123.0.6312.105 at all.~ ~Now that's odd - how can a flag possibly be available in one instance and entirely missing (not even listed as "unavailable") in another instance of the same version of cromite? Has anyone else failed to find that flag?~ #### EDIT: > > I cant see that flag when I search for it ! > > Search doesn't seem to work for Cromite flags, you have to go explicitly in the "Cromite" tab and look for it. Sigh, I should have read _all_ previous comments before commenting.

However, in the 'cromite' tab of chrome://flags in that unaffected instance, there's indeed a #fonts-fingerprint-mitigation flag.

Alas, without 'cromite' flag search, it's very difficult to identify that flag in the affected instance.

[drogga]

@calvin2021y IDK why the ADB command doesn't work for you, but not only I managed to downgrade with the mentioned apps (in my prev. comment) in an A.11 emulator, but also SAI (by Aefyr), by using a custom install-create command in the super secret settings menu: pm install-create -d -r

Keep in mind that there's always a risk to lose the app's data when downgrading, so don't keep me responsible if that happens.

[GfEW]

971. There, even chrome://flags is unreadable due to font placeholders [...]

Screenshot


[...] without flag search, it's very difficult to identify that flag in the affected instance.

I've managed to identify and disable #fonts-fingerprint-mitigation in that flood of font placeholders posing as listing of flags. And since restarted, cromite renders all affected pages, including chrome://flags, readable again. Yay!

[cvtsi2sd]

That's the point of these certificates... only the original owner/creator with the private keys can publish a new official version.

Yep, I was just wondering if there was some way for me to explicitly override the check when installing, but apparently there is not (unless with root probably).

You can make your own set of keys and sign the apk with them... then you can uninstall their chromite apk, and install your own.

I hoped to avoid that to avoid losing my data (which isn't all that much, but still is a nuisance for bookmarks, home screen, some logins, etc); ultimately I tried to make a custom build to avoid having to do that to downgrade.

As for release, you should make a pull request and ask the project owner to integrate it and make a build.

@uazo would that be accepted? The current state of affairs is very sad, the workaround doesn't work and the browser is borderline unusable (a renderer process crash whenever a "strange" character should appear is a huge problem).

[uazo]

I have only now better understood the issue.

The identifiability of emojii is only a subset of the larger problem that is related to the handling of fallback fonts in android. To solve it, I would have to insert all the necessary fonts, about 90 mega in the apk more. Not feasible. For now I decided to drop the patch, maybe in the future I will reactivate the component update and the automatic download of the necessary fonts. Having it active, even for emojii alone, could have the effect of decreasing entropy by improving fingerprinting efficiency.

Thank you all for letting me know (OK, at the cost of a huge bug :)

[Vinfall]

I've managed to identify and disable #fonts-fingerprint-mitigation in that flood of font placeholders posing as listing of flags. And since restarted, cromite renders all affected pages, including chrome://flags, readable again. Yay!

I know you have solved it, but In case anyone discovered this issue as late as I am, you can actually head to cromite tab, then use Find in page in the toolbar instead. Search using that would still work.

---

Given that uazo already dropped the patch in recent commits, I don't whether the following would add any value but just post here.

For me the symptom is a bit weirder. CJK characters still appear normally as long as they are not inside the <code> HTML element...

[uazo]

thank you all for checking.

I think I will proceed in this way:

• reactivate component updates to download the full set of fonts (about 60mb compressed). this way the apk will not grow.
• edit the patch by retrieving the font content via mojo (due because the render is sandboxed and has no access to the file system)

if it works, all cromite will use the same set of fonts and I will probably also be able to drop the Canvas::measureText() antifingerprinting patch.

[vishalscodes]

It doesn't work properly for Tamil, Kannada and Hindi too.

EDIT: It works now. Thanks @uazo for the quick response.

[uazo]

It doesn't work properly for Tamil, Kannada and Hindi too.

please use the latest version released today. it cannot not work, that patch has been removed.

[GfEW]

@uazo Can we reset #fonts-fingerprint-mitigation to enabled (default) by v123.0.6312.106 or is there any reason to keep it disabled?

[alisonatwork]

I switched it back to default after upgrading and haven't noticed any untoward effects.

[uazo]

Can we reset #fonts-fingerprint-mitigation to enabled (default) by v123.0.6312.106

yes, you can reactivate it, although in android, in the light of what I have learned (now), it does basically nothing. I am working on a new approach.

[atauzki]

Also broken on Windows build.