WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
160898
[Win] Add tests for linked fonts.
https://bugs.webkit.org/show_bug.cgi?id=160898
Summary
[Win] Add tests for linked fonts.
Per Arne Vollan
Reported
2016-08-16 07:00:36 PDT
Add tests for
https://trac.webkit.org/changeset/204502
.
Attachments
Patch
(7.33 KB, patch)
2016-08-16 07:24 PDT
,
Per Arne Vollan
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Per Arne Vollan
Comment 1
2016-08-16 07:24:52 PDT
Created
attachment 286174
[details]
Patch
Brent Fulgham
Comment 2
2016-08-16 10:13:02 PDT
Comment on
attachment 286174
[details]
Patch Looks good! r=me.
Myles C. Maxfield
Comment 3
2016-08-16 11:10:25 PDT
Comment on
attachment 286174
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=286174&action=review
> Source/WebCore/platform/graphics/win/FontCacheWin.cpp:99 > +WEBCORE_EXPORT void appendLinkedFonts(WCHAR* linkedFonts, unsigned length, Vector<String>* result)
There is no way to test this without exporting the function? This seems suspicious.
Per Arne Vollan
Comment 4
2016-08-16 11:45:48 PDT
(In reply to
comment #3
)
> Comment on
attachment 286174
[details]
> Patch > > View in context: >
https://bugs.webkit.org/attachment.cgi?id=286174&action=review
> > > Source/WebCore/platform/graphics/win/FontCacheWin.cpp:99 > > +WEBCORE_EXPORT void appendLinkedFonts(WCHAR* linkedFonts, unsigned length, Vector<String>* result) > > There is no way to test this without exporting the function? This seems > suspicious.
Since we have a separate test executable for WebCore, I thought this was the way to do it. I might have missed something, though. Thanks for looking into this :-)
Per Arne Vollan
Comment 5
2016-08-16 11:46:29 PDT
(In reply to
comment #2
)
> Comment on
attachment 286174
[details]
> Patch > > Looks good! r=me.
Thanks for reviewing!
Myles C. Maxfield
Comment 6
2016-08-16 12:52:25 PDT
(In reply to
comment #4
)
> (In reply to
comment #3
) > > Comment on
attachment 286174
[details]
> > Patch > > > > View in context: > >
https://bugs.webkit.org/attachment.cgi?id=286174&action=review
> > > > > Source/WebCore/platform/graphics/win/FontCacheWin.cpp:99 > > > +WEBCORE_EXPORT void appendLinkedFonts(WCHAR* linkedFonts, unsigned length, Vector<String>* result) > > > > There is no way to test this without exporting the function? This seems > > suspicious. > > Since we have a separate test executable for WebCore, I thought this was the > way to do it. I might have missed something, though. > > Thanks for looking into this :-)
I mean, isn't there a way a regular layout test can trigger this code path?
Per Arne Vollan
Comment 7
2016-08-17 07:19:49 PDT
(In reply to
comment #6
)
> (In reply to
comment #4
) > > (In reply to
comment #3
) > > > Comment on
attachment 286174
[details]
> > > Patch > > > > > > View in context: > > >
https://bugs.webkit.org/attachment.cgi?id=286174&action=review
> > > > > > > Source/WebCore/platform/graphics/win/FontCacheWin.cpp:99 > > > > +WEBCORE_EXPORT void appendLinkedFonts(WCHAR* linkedFonts, unsigned length, Vector<String>* result) > > > > > > There is no way to test this without exporting the function? This seems > > > suspicious. > > > > Since we have a separate test executable for WebCore, I thought this was the > > way to do it. I might have missed something, though. > > > > Thanks for looking into this :-) > > I mean, isn't there a way a regular layout test can trigger this code path?
Normally, there will be a comma in the linked font list, since this is read from the Windows registry. I think it would be possible to write a layout test for this, but it will require a bit more work.
WebKit Commit Bot
Comment 8
2016-08-17 07:41:00 PDT
Comment on
attachment 286174
[details]
Patch Clearing flags on attachment: 286174 Committed
r204558
: <
http://trac.webkit.org/changeset/204558
>
WebKit Commit Bot
Comment 9
2016-08-17 07:41:05 PDT
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug