Bug 162783

Summary: Implement animation of font-variation-settings
Product: WebKit Reporter: Myles C. Maxfield <mmaxfield>
Component: TextAssignee: Myles C. Maxfield <mmaxfield>
Status: RESOLVED FIXED    
Severity: Normal CC: commit-queue, dino, dstockwell, esprehn+autocc, glenn, kondapallykalyan, mmaxfield, simon.fraser
Priority: P2    
Version: Other   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 162490    
Attachments:
Description Flags
Patch
none
Patch simon.fraser: review+

Myles C. Maxfield
Reported 2016-09-30 03:20:36 PDT
Created attachment 290319 [details] Patch Implement animation of font-variation-settings
Attachments
Patch (14.87 KB, patch)
2016-09-30 03:20 PDT, Myles C. Maxfield
no flags
Patch (18.47 KB, patch)
2016-09-30 15:15 PDT, Myles C. Maxfield
simon.fraser: review+
Myles C. Maxfield
Comment 1 2016-09-30 15:15:26 PDT
Simon Fraser (smfr)
Comment 2 2016-09-30 15:43:21 PDT
Comment on attachment 290398 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=290398&action=review > Source/WebCore/page/animation/CSSPropertyAnimation.cpp:385 > + if (fromItem.tag() != toItem.tag()) > + return FontVariationSettings(); Is tag order meaningful? If not, I wonder if we should match ignoring order.
Myles C. Maxfield
Comment 3 2016-09-30 15:48:18 PDT
(In reply to comment #2) > Comment on attachment 290398 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=290398&action=review > > > Source/WebCore/page/animation/CSSPropertyAnimation.cpp:385 > > + if (fromItem.tag() != toItem.tag()) > > + return FontVariationSettings(); > > Is tag order meaningful? If not, I wonder if we should match ignoring order. Order isn't meaningful, but the items in the array are already in sorted order (see FontVariationSettings::insert() to see the search for the correct index). Because this list will always be small, I opted for a simple flat array instead of a more complicated tree data structure.
Myles C. Maxfield
Comment 4 2016-09-30 16:10:27 PDT
Note You need to log in before you can comment on or make changes to this bug.