Both of these don't display the page:
meet.google.com
Richmond wrote:
Both of these don't display the page: meet.google.com
Is that Hangouts in disguise? Thought it had been killed-off?
<https://gcemetery.co/google-hangouts/>
I have installed Firefox fenix-146.0.1-android-arm64-v8a and fennec_fdroid_1450020 on a FireOS tablet. Both of these don't display
the page:
meet.google.com
properly. There is something wrong with the fonts, or some text from the
html is displayed which should not be. Is it a font problem? Is there
some font which can be downloaded? I cannot find any settings available
for fonts.
Richmond <dnomhcir@gmx.com> wrote:
I have installed Firefox fenix-146.0.1-android-arm64-v8a and
fennec_fdroid_1450020 on a FireOS tablet. Both of these don't display
the page:
meet.google.com
properly. There is something wrong with the fonts, or some text from the
html is displayed which should not be. Is it a font problem? Is there
some font which can be downloaded? I cannot find any settings available
for fonts.
Don't know what "something wrong" might mean. Lots of possibilities.
Do placeholder characters appear instead of the expected characters?
That's caused by blocking 3rd-party fonts.
Font foundaries, of which Google's is the most used, can track where you visited, when, and how often. A site that offloads fonts to a foundary
has your client fetch them from the foundary. Sites will use
foundaries, for example, to have icons to indicate what a button or link might do when clicked. If you block 3rd-party fonts (aka web fonts), a placeholder is displayed in place of the would-be character from an
external font source.
"Don't display the page" makes it sound like you don't get anything.
There is no content delivered to you, or the HTML is screwed up as to be missing the <body>, or the web doc is heavily Javascripted and the
scripts at that time generate the web doc content, or other cause to
prevent you getting anything in the body of the web doc, so you see a
blank web doc. Yet then you discuss fonts, so you are seeing something.
3rd-party fonts can be blocked by extensions. For example, uBlock
Origin has an option to block them. Or you might use some other
extension that lets you define rules, and one is *$font,third-party.
Using 3rd-party font foundaries is a privacy issue. A web site could
store the font set locally at their web server to have them delivered
from there to you. You are visiting their site, do delivering fonts
from them doesn't affect your level of privacy. However, sites want to offload as much bandwidth to CDNs (Content Delivery Networks) even for
images and scripts, including having someone else's bandwidth deliver
fonts to you.
https://www.ghacks.net/2022/09/17/how-to-block-web-fonts-to-improve-privacy/
At one time, I had uBlock Origin configured to block 3rd-party fonts.
Some sites ended up with tons of placeholder characters making it
difficult to know what action or event an element in the web doc might
do. My pharmacy is like that: disable 3rd-party fonts, and it's hard to
know how to navigate their site. I don't visit there often enough to memorize that element does what event. I gave up on blocking 3rd-party
fonts to improve privacy (prevent tracking by font foundaries).
The above article mentions an about:config setting that will block
3rd-party fonts: gfx.downloadable_fonts.enabled. Default is true.
False blocks them. No idea what gfx.downloadable_fonts.woff2.enabled
does (didn't bother to research it). The article also mentions a config setting "Allow pages to choose their own fonts". I recall when I tried
it that web docs were too often illegible. I didn't have local fonts
that matched on what the web doc tried to use. Extensions can also
block web fonts.
Have you tried creating a new profile in Firefox, and revisit that web
site? A fresh profile won't have any extensions, and all Firefox
settings would be at their install-time defaults.
It is displaying words over the top of words, so that it is not clear
what the word is. The oddest example is by the input box where it says "keyboard". The menu on the left hand side has the word 'event'
partially covering the word 'meetings'.
I see now, looking at the site from desktop chromium, that the word 'keyboard' is a substitute for the image of a keyboard which has come
from somewhere. There are also calendar and video camera images, or pictograms. These are not being displayed properly on the FireOS
Firefox.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 54 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 17:34:49 |
| Calls: | 742 |
| Files: | 1,218 |
| D/L today: |
4 files (8,203K bytes) |
| Messages: | 184,412 |
| Posted today: | 1 |