Closed Bug 187992 Opened 22 years ago Closed 13 years ago

Font Inspector

Categories

(Core :: Layout: Text and Fonts, enhancement, P3)

Product:
Core
Component:
Layout: Text and Fonts
Type:
enhancement

Tracking

()

Status:
RESOLVED DUPLICATE of bug 467669
Milestone:
Future

People

(Reporter: smontagu, Unassigned)

References

Details

Many issues are hard to debug for lack of knowledge of what font is actually
being used to render a specific element. It would be immensely useful to have a
simple tool to show this information, possibly as an independent tool similar to
DOM Inspector, or possibly as a new view in DOM Inspector itself.
ToDo:
- We need a new API to obtain "platform-specific comment strings" for each
fontmetrics node
- We need XPCOM glue to access this API from JS
... more items ?
Is the fontmetrics stuff scriptable?  What (if anything) do we plan to do about
glyph substitution out of other fonts?
Priority: -- → P3
Target Milestone: --- → Future
OS: Windows 2000 → All
Hardware: PC → All
*** Bug 339776 has been marked as a duplicate of this bug. ***
*** Bug 266741 has been marked as a duplicate of this bug. ***
Blocks: 266741
Depends on: 467669
Assignee: layout.fonts-and-text → nobody
QA Contact: ian → layout.fonts-and-text
Given that bug 266741 was reopened to "keep the DOMI bug distinct from the core bug", which would imply that this bug only concerns an API, and indeed comment 1 and comment 2 reinforce that...

If there's some subtlety here that doesn't fall into bug 266741 or bug 467669 that I'm not seeing, let the rebuke roll in.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.