Bug 298642

Summary:

Web Inspector: Wrong font shown on Inspect > Elements > font when using unicode-range

Product:

WebKit

Reporter:

kenrick95

Component:

Web Inspector

Assignee:

Nobody <webkit-unassigned>

Status:

NEW

Severity:

Normal

CC:

fantasai.bugs, inspector-bugzilla-changes, vitor.roriz, webkit-bug-importer

Priority:

Keywords:

InRadar

Version:

Safari 26

Hardware:

Mac (Apple Silicon)

OS:

macOS 14

Attachments:

Description	Flags
Screenshot 1: devtool panel shows "Times New Roman" even though it is not using it	none
Screenshot 2: Only in the second <span> that it should show "Times New Roman" (this is correct)	none

kenrick95

Reported 2025-09-09 22:55:51 PDT

Created attachment 476687 [details] Screenshot 1: devtool panel shows "Times New Roman" even though it is not using it Using unicode-range to change font-family of a text. Inspect > Elements > font, it always shows "Times New Roman" instead of the actual font Codepen: https://codepen.io/kenrick95/pen/KwdYKxV Descriptions: 1. In the first <span> it should show whatever font used in sans-serif (it is rendered correctly in the page). However the devtool panel shows "Times New Roman" even though it is not using it (Screenshot 1) 2. Only in the second <span> that it should show "Times New Roman" However in both cases, they show it as "Times New Roman" Safari 26.0 (19622.1.22.11.13)

Attachments
Screenshot 1: devtool panel shows "Times New Roman" even though it is not using it (994.29 KB, image/png) 2025-09-09 22:55 PDT, kenrick95	no flags	Details
Screenshot 2: Only in the second <span> that it should show "Times New Roman" (this is correct) (1019.88 KB, image/png) 2025-09-09 22:56 PDT, kenrick95	no flags	Details
View All Add attachment proposed patch, testcase, etc.

kenrick95

Comment 1 2025-09-09 22:56:43 PDT

Created attachment 476688 [details] Screenshot 2: Only in the second <span> that it should show "Times New Roman" (this is correct)

Radar WebKit Bug Importer

Comment 2 2025-09-10 07:49:14 PDT

<rdar://problem/160287388>

Note You need to log in before you can comment on or make changes to this bug.