[Webkit-unassigned] [Bug 37451] Web Inspector: Show Exact Font Being Used
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon May 2 18:42:45 PDT 2016
https://bugs.webkit.org/show_bug.cgi?id=37451
--- Comment #10 from Myles C. Maxfield <mmaxfield at apple.com> ---
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> >
> > > This is an interesting idea.
> >
> > I still like the way Firefox (46) does it, a separate sub tab in the
> > inspector.
> > (Weirdly perhaps, that sub tab doesât seem to exist in Firefox Developer
> > edition and Firefox nightly)
> >
> > > In the WebKit inspector, you can only select an entire node at a time. How
> > > does it work in other browsers when certain characters in an element fall
> > > back to a different font than the rest of the characters?
> >
> > Speaking of Firefox: given this test file:
> > <!doctype html>
> > <body style="font-family: 'Helvetica Neue'; font-size: 2em;">
> >
> > <p>test:â² trigram</p>
> >
> > <p style="font-family: Optima, sans-serif">test letters other Å Ä</p>
> >
> > Selecting any of the two <p>, the font sub tab shows the two font-family
> > being used. For the 1st para, it shows 'Apple Symbols' and 'Helvetica Neue';
> > for the second one, it shows 'Optima' and 'Helvetica' (Optima doesn't have
> > glyphs for Å Ä).
>
> Ah, so it just presents the union of all the used fonts in the node.
>
> Maybe that idea is enough for us. I'm not sure.
I think WebCore should expose something like (in pseudocode)
result: [range]
struct range {
unsigned stringStartIndex
unsigned stringEndIndex
string font
}
Then, the web inspector machinery can determine the best way to expose this information to the user.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160503/664b4d3b/attachment.html>
More information about the webkit-unassigned
mailing list