FontInspector/TestPlan: Difference between revisions

FontInspector/TestPlan (view source)

259 bytes added , 4 April 2013

Confirmed users

834

edits

@@ Line 20: / Line 20: @@
 == Summary ==
-Users falling victim to "search hijacking" (keyword.URL being taken over by an unwanted search engine) is a common problem.
+Mozilla is adding a new typography-centric tool called the “Font Inspector” to Firefox’s DevTools.
-There are two cases we can detect:
+The tools job is to display the font with editable “Abc” placeholder text, to name the typeface and to show the @font-face CSS. Some might think of this as being redundant because you can already view the CSS via the Inspector, when you want to find the typefaces in use. Here you have a counterpoint: since typography is inherently visual, it's handy to see it displayed as such.
-*pref is changed, and the hostname is different (e.g. switched from the default of Google to SuperAwesomeWebDealsSearch.com)
-*pref is changed, and only parameters are different (e.g. user customized to a specific type of Google search, or referral codes where added)
-In either case, we could prompt the user and offer to reset the keyword.URL value to the default after they trigger a search from the location bar.
+The most beneficial aspect of this feature, however, is the “See all the fonts used in this page” button, which permits users understand what Web fonts and font-based icons are in use, along with seeing all of them in one place.
+As a conclusion, the purpose of the Font Inspector feature is to learn how typography is applied on any site.
 == Reference ==