Bugzilla

(In reply to Dragan from comment #20)
> Sorry guys, had to work and didn't have time to do some more testing.
[...]
> Now I see the button for attaching files up on this page, so I guess I can do that there!? Sorry again!

No worries; your bug report & your continued help here is appreciated! And, I'm glad you've found the file-attachment section; I know Bugzilla user-experience is not always the best. :)

> 1. For the last 8 months I am using the "false" value for gfx.e10s.font-list.shared and everything is working just fine. [...] I don't understand why default value for gfx.e10s.font-list.shared is not "false" because everybody could get default FF with normal appearance of websites?

In short: the "false" value represents an old/inefficient configuration, whereas "true" represents a newly-implemented & more-efficient configuration. (In theory the two should behave the same, but with "true" reducing memory usage.  Though there are a few cases where the behavior intentionally changed, though, as Jonathan noted, and there may also be cases where we changed behavior unintentionally).

> 2. In SETTINGS / LANGUAGE AND APPEARANCE / FONTS AND COLORS / ADVANCED there is checkbox "Allow pages to choose their own fonts, instead of your selections above". I did some experiments, but I didn't notice any difference whether the box is checked, or not!? It's like that option didn't work during my testing.

Let's try to avoid going too far into side-conversations on this bug report, so that the thread of investigating-the-core-issue doesn't get too confusing to follow. :)

But in any case: it's not-unusual for that checkbox to not noticably break the web too much, if sites are well designed to have good generic fallback fonts (particularly if the sites' chosen generic fallback fonts happen to already be what you're using).

You should probably notice big differences with that box checked/unchecked at e.g. https://fonts.google.com/ , though.
 
> 3. for me the logical thing would be that FF always, by default, shows the webpages in the way they are, and only if user choose so, to check the box and make FF to use generic (default) fonts instead of original.

I think that's essentially what we intend to do (and it is indeed what happens on my system, and I suspect it's *usually* what happens on your system as well, though you seem to be hitting some interesting edge cases. Hopefully following up on Jonathan's notes/questions in comment 19 will get us closer to an answer. :) )

(In reply to Dragan from comment #20)
> Sorry guys, had to work and didn't have time to do some more testing.
[...]
> Now I see the button for attaching files up on this page, so I guess I can do that there!? Sorry again!

No worries; your bug report & your continued help here is appreciated! And, I'm glad you've found the file-attachment section; I know Bugzilla user-experience is not always the best. :)

> 1. For the last 8 months I am using the "false" value for gfx.e10s.font-list.shared and everything is working just fine. [...] I don't understand why default value for gfx.e10s.font-list.shared is not "false" because everybody could get default FF with normal appearance of websites?

In short: the "false" value represents an old/inefficient configuration, whereas "true" represents a newly-implemented & more-efficient configuration. (In theory the two should behave the same, but with "true" reducing memory usage.  Though there are a few cases where the behavior intentionally changed, as Jonathan noted.   And there may also be cases where we changed behavior unintentionally, which this bug might be a case of.)

> 2. In SETTINGS / LANGUAGE AND APPEARANCE / FONTS AND COLORS / ADVANCED there is checkbox "Allow pages to choose their own fonts, instead of your selections above". I did some experiments, but I didn't notice any difference whether the box is checked, or not!? It's like that option didn't work during my testing.

Let's try to avoid going too far into side-conversations on this bug report, so that the thread of investigating-the-core-issue doesn't get too confusing to follow. :)

But in any case: it's not-unusual for that checkbox to not noticably break the web too much, if sites are well designed to have good generic fallback fonts (particularly if the sites' chosen generic fallback fonts happen to already be what you're using).

You should probably notice big differences with that box checked/unchecked at e.g. https://fonts.google.com/ , though.
 
> 3. for me the logical thing would be that FF always, by default, shows the webpages in the way they are, and only if user choose so, to check the box and make FF to use generic (default) fonts instead of original.

I think that's essentially what we intend to do (and it is indeed what happens on my system, and I suspect it's *usually* what happens on your system as well, though you seem to be hitting some interesting edge cases. Hopefully following up on Jonathan's notes/questions in comment 19 will get us closer to an answer. :) )

(In reply to Dragan from comment #20)
> Sorry guys, had to work and didn't have time to do some more testing.
[...]
> Now I see the button for attaching files up on this page, so I guess I can do that there!? Sorry again!

No worries; your bug report & your continued help here is appreciated! And, I'm glad you've found the file-attachment section; I know Bugzilla user-experience is not always the best. :)

> 1. For the last 8 months I am using the "false" value for gfx.e10s.font-list.shared and everything is working just fine. [...] I don't understand why default value for gfx.e10s.font-list.shared is not "false" because everybody could get default FF with normal appearance of websites?

In short: the "false" value represents an old/inefficient configuration, whereas "true" represents a newly-implemented & more-efficient configuration. (In theory the two should behave the same, but with "true" reducing memory usage.  Though there are a few cases where the behavior intentionally changed, as Jonathan noted.   And there may also be cases where we changed behavior unintentionally, which this bug might be a case of.)

> 2. In SETTINGS / LANGUAGE AND APPEARANCE / FONTS AND COLORS / ADVANCED there is checkbox "Allow pages to choose their own fonts, instead of your selections above". I did some experiments, but I didn't notice any difference whether the box is checked, or not!? It's like that option didn't work during my testing.

Let's try to avoid going too far into side-conversations on this bug report, so that the thread of investigating-the-core-issue doesn't get too confusing to follow. :)

But in any case: it's not-unusual for that checkbox to not noticably break the web too much, if sites are well designed to have good generic fallback fonts (particularly if the sites' chosen generic fallback fonts happen to already be what you're using).

You should probably notice big differences with that box checked/unchecked at e.g. https://fonts.google.com/ or other sites that use exotic fonts, though.
 
> 3. for me the logical thing would be that FF always, by default, shows the webpages in the way they are, and only if user choose so, to check the box and make FF to use generic (default) fonts instead of original.

I think that's essentially what we intend to do (and it is indeed what happens on my system, and I suspect it's *usually* what happens on your system as well, though you seem to be hitting some interesting edge cases. Hopefully following up on Jonathan's notes/questions in comment 19 will get us closer to an answer. :) )