Bug 92623

Summary: Web Inspector: font names that start with a @ in CSS font-face are not properly handled.
Product: WebKit Reporter: Alexander Pavlov (apavlov) <apavlov>
Component: Web InspectorAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: apavlov, bburg, bweinstein, graouts, joepeck, keishi, loislo, pfeldman, pmuellr, rik, timothy, webkit-bug-importer, yurys, zherczeg
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Bug Depends on:    
Bug Blocks: 116924    

Description Alexander Pavlov (apavlov) 2012-07-30 02:20:07 PDT
What steps will reproduce the problem?
1. Open Inspector on http://blogs.msdn.com/b/oldnewthing/archive/2012/07/19/10331400.aspx
2. Inspect the element with the "font-face: SimSun" style.
3. Check the styles sidebar.
4. Attempt to edit the font-face and change the name.
5. Inspect the element with the "font-face: @SimSun" style.
6. Check the styles sidebar.
7. Attempt to edit the font-face and set it to the correct name.

What is the expected result?

The second element's font-face is displayed as @SimSun and both entries can be edited the same way.

What happens instead?

Font-face is displayed as "@SimSunn", though in the Elements view it is correct.  If you attempt to put a @ in a font name you are editing, Inspector crosses the line out and says the value is invalid.  You must escape the @ with a \ (as seen in the Elements view) for it to be accepted.  Editing the value will also add extra "n" on the end.

Upstreaming http://code.google.com/p/chromium/issues/detail?id=138077
Comment 1 Alexander Pavlov (apavlov) 2012-07-30 04:59:51 PDT
void CSSParser::parseEscape(UChar*& result) rewrites the input string, based on which CSSParser computes the actual (source) property name and value. According to zherczeg who rewrote the lexer earlier this year, this is a huge refactoring and doesn't seem reasonable at the moment.
Comment 2 Radar WebKit Bug Importer 2014-12-01 14:36:10 PST
<rdar://problem/19107002>
Comment 3 Blaze Burg 2016-12-04 16:24:01 PST
Unable to repro. Closing.