[prev in list] [next in list] [prev in thread] [next in thread]
List: webkit-unassigned
Subject: [Webkit-unassigned] [Bug 265182] [FreeType] Do not special case the "sans" font family name
From: bugzilla-daemon () webkit ! org
Date: 2023-11-21 8:54:55
Message-ID: bug-265182-2851-9Cz2vsJrLD () https ! bugs ! webkit ! org/
[Download RAW message or body]
--17005568940.bB38bD.9034
Date: Tue, 21 Nov 2023 00:54:54 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.webkit.org/
Auto-Submitted: auto-generated
https://bugs.webkit.org/show_bug.cgi?id=265182
--- Comment #1 from Adrian Perez <aperez@igalia.com> ---
Created attachment 468705
--> https://bugs.webkit.org/attachment.cgi?id=468705&action=review
Screenshot of two browser, one of them with the "sans" matching removed
Here's a screenshot comparing how WebKitGTK behaves today (left), and
with the match for "sans" removed (right). The odd choice on the left
was because this particular system does not have a FontConfig "sans"
alias in the configuration, and FontConfig ends up picking a symbols
font (Font Awesome), which has these oddball latin characters.
--
You are receiving this mail because:
You are the assignee for the bug.
--17005568940.bB38bD.9034
Date: Tue, 21 Nov 2023 00:54:54 -0800
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.webkit.org/
Auto-Submitted: auto-generated
<html>
<head>
<base href="https://bugs.webkit.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [FreeType] Do not special case the "sans" font family name"
href="https://bugs.webkit.org/show_bug.cgi?id=265182#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [FreeType] Do not special case the "sans" font family name"
href="https://bugs.webkit.org/show_bug.cgi?id=265182">bug 265182</a>
from <span class="vcard"><a class="email" \
href="mailto:aperez@igalia.com" title="Adrian Perez \
<aperez@igalia.com>"> <span class="fn">Adrian Perez</span></a> </span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=468705" \
name="attach_468705" title="Screenshot of two browser, one of them with the "sans" \
matching removed">attachment 468705</a> <a \
href="attachment.cgi?id=468705&action=edit" title="Screenshot of two browser, one \
of them with the "sans" matching removed">[details]</a></span> Screenshot of two \
browser, one of them with the "sans" matching removed
Here's a screenshot comparing how WebKitGTK behaves today (left), and
with the match for "sans" removed (right). The odd choice on the left
was because this particular system does not have a FontConfig "sans"
alias in the configuration, and FontConfig ends up picking a symbols
font (Font Awesome), which has these oddball latin characters.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>
--17005568940.bB38bD.9034--
_______________________________________________
webkit-unassigned mailing list
webkit-unassigned@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-unassigned
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic