-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermittent results in /css/css-fonts/variations/font-weight-matching.html #20686
Labels
I-intermittent
Problem reproduces intermittently.
Comments
This was referenced Apr 12, 2023
4 tasks
This was referenced Aug 29, 2023
This was referenced Sep 5, 2023
This was referenced Sep 13, 2023
Merged
3 tasks
This was referenced Apr 15, 2024
Merged
3 tasks
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
Apr 27, 2024
This change adds initial support for the CSS font fallback algorithm [^1]. There are a couple major changes here: 1. Support is added for the `weight`, `style`, `stretch` and `unicode-range` declarations in `@font-face`. 2. Font matching in the font cache can return templates and `FontGroupFamily` can own mulitple templates. This is due to needing support for "composite fonts". These are `@font-face` declarations that only differ in their `unicode-range` definition. This fixes a lot of non-determinism in font selection especially when dealing with pages that define "composite faces." A notable example of such a page is servo.org, which now consistently displays the correct web font. One test starts to fail due to an uncovered bug, but this will be fixed in a followup change. Fixes servo#20686. Fixes servo#20684. Co-authored-by: Mukilan Thiyagarajan <mukilan@igalia.com>
3 tasks
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
Apr 27, 2024
There are a couple major changes here: 1. Support is added for the `weight`, `style`, `stretch` and `unicode-range` declarations in `@font-face`. 2. Font matching in the font cache can return templates and `FontGroupFamily` can own mulitple templates. This is due to needing support for "composite fonts". These are `@font-face` declarations that only differ in their `unicode-range` definition. This fixes a lot of non-determinism in font selection especially when dealing with pages that define "composite faces." A notable example of such a page is servo.org, which now consistently displays the correct web font. One test starts to fail due to an uncovered bug, but this will be fixed in a followup change. Fixes servo#20686. Fixes servo#20684. Co-authored-by: Mukilan Thiyagarajan <mukilan@igalia.com>
3 tasks
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
Apr 29, 2024
There are a couple major changes here: 1. Support is added for the `weight`, `style`, `stretch` and `unicode-range` declarations in `@font-face`. 2. Font matching in the font cache can return templates and `FontGroupFamily` can own mulitple templates. This is due to needing support for "composite fonts". These are `@font-face` declarations that only differ in their `unicode-range` definition. This fixes a lot of non-determinism in font selection especially when dealing with pages that define "composite faces." A notable example of such a page is servo.org, which now consistently displays the correct web font. One test starts to fail due to an uncovered bug, but this will be fixed in a followup change. Fixes servo#20686. Fixes servo#20684. Co-authored-by: Mukilan Thiyagarajan <mukilan@igalia.com>
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
Apr 29, 2024
There are a couple major changes here: 1. Support is added for the `weight`, `style`, `stretch` and `unicode-range` declarations in `@font-face`. 2. Font matching in the font cache can return templates and `FontGroupFamily` can own mulitple templates. This is due to needing support for "composite fonts". These are `@font-face` declarations that only differ in their `unicode-range` definition. This fixes a lot of non-determinism in font selection especially when dealing with pages that define "composite faces." A notable example of such a page is servo.org, which now consistently displays the correct web font. One test starts to fail due to an uncovered bug, but this will be fixed in a followup change. Fixes servo#20686. Fixes servo#20684. Co-authored-by: Mukilan Thiyagarajan <mukilan@igalia.com>
github-merge-queue bot
pushed a commit
that referenced
this issue
Apr 29, 2024
There are a couple major changes here: 1. Support is added for the `weight`, `style`, `stretch` and `unicode-range` declarations in `@font-face`. 2. Font matching in the font cache can return templates and `FontGroupFamily` can own mulitple templates. This is due to needing support for "composite fonts". These are `@font-face` declarations that only differ in their `unicode-range` definition. This fixes a lot of non-determinism in font selection especially when dealing with pages that define "composite faces." A notable example of such a page is servo.org, which now consistently displays the correct web font. One test starts to fail due to an uncovered bug, but this will be fixed in a followup change. Fixes #20686. Fixes #20684. Co-authored-by: Mukilan Thiyagarajan <mukilan@igalia.com>
Looks like this is still an issue. |
This was referenced Apr 30, 2024
Merged
This was referenced May 16, 2024
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
May 24, 2024
This is a port from Gecko of the CSS font matching algorithm distance functions as well as the "simple family" concept for optimizing matching when dealing with simple fonts. Fixes servo#189. Fixes servo#190. Fixes servo#20686. Fixes servo#20684. Co-authored-by: Mukilan Thiyagarajan <mukilan@igalia.com> Signed-off-by: Martin Robinson <mrobinson@igalia.com>
3 tasks
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
May 24, 2024
This is a port from Gecko of the CSS font matching algorithm distance functions as well as the "simple family" concept for optimizing matching when dealing with simple fonts. Fixes servo#189. Fixes servo#190. Fixes servo#20686. Fixes servo#20684. Co-authored-by: Mukilan Thiyagarajan <mukilan@igalia.com> Signed-off-by: Martin Robinson <mrobinson@igalia.com>
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
May 24, 2024
This is a port from Gecko of the CSS font matching algorithm distance functions as well as the "simple family" concept for optimizing matching when dealing with simple fonts. Fixes servo#189. Fixes servo#190. Fixes servo#20686. Fixes servo#20684. Co-authored-by: Mukilan Thiyagarajan <mukilan@igalia.com> Signed-off-by: Martin Robinson <mrobinson@igalia.com>
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
May 24, 2024
This is a port from Gecko of the CSS font matching algorithm distance functions as well as the "simple family" concept for optimizing matching when dealing with simple fonts. Fixes servo#189. Fixes servo#190. Fixes servo#20686. Fixes servo#20684. Co-authored-by: Mukilan Thiyagarajan <mukilan@igalia.com> Signed-off-by: Martin Robinson <mrobinson@igalia.com>
github-merge-queue bot
pushed a commit
that referenced
this issue
May 24, 2024
* fonts: Add support for the CSS font matching algorithm This is a port from Gecko of the CSS font matching algorithm distance functions as well as the "simple family" concept for optimizing matching when dealing with simple fonts. Fixes #189. Fixes #190. Fixes #20686. Fixes #20684. Co-authored-by: Mukilan Thiyagarajan <mukilan@igalia.com> Signed-off-by: Martin Robinson <mrobinson@igalia.com> * Ensure that simple faces are removed for removed stylesheets --------- Signed-off-by: Martin Robinson <mrobinson@igalia.com> Co-authored-by: Mukilan Thiyagarajan <mukilan@igalia.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: