It is too easy to accidentally construct a Color
Created attachment 203019 [details] Patch
This is likely to break other ports. So if any kind soul would help me out, that would be great!
Comment on attachment 203019 [details] Patch Attachment 203019 [details] did not pass qt-ews (qt): Output: http://webkit-queues.appspot.com/results/670158
Comment on attachment 203019 [details] Patch Attachment 203019 [details] did not pass qt-wk2-ews (qt-wk2): Output: http://webkit-queues.appspot.com/results/735142
Comment on attachment 203019 [details] Patch Attachment 203019 [details] did not pass gtk-ews (gtk): Output: http://webkit-queues.appspot.com/results/710276
Comment on attachment 203019 [details] Patch Attachment 203019 [details] did not pass win-ews (win): Output: http://webkit-queues.appspot.com/results/703198
Comment on attachment 203019 [details] Patch Attachment 203019 [details] did not pass efl-ews (efl): Output: http://webkit-queues.appspot.com/results/693212
Comment on attachment 203019 [details] Patch Attachment 203019 [details] did not pass efl-wk2-ews (efl-wk2): Output: http://webkit-queues.appspot.com/results/740036
Comment on attachment 203019 [details] Patch I suggest doing this in a couple steps. I’d add the transparentColor(), whiteColor(), blackColor(), and other three functions first and adopt them without the rest of the change, since that seems to be more than half of the patch. If you want to do this the way I did AdoptCF, then you should have the thing set up locally with explicit constructors, but not land that part until you separately land all the adoption. Then you can have a patch that just tries to flip the switch. RenderTheme::platformTapHighlightColor seems to be the reason for the EFL and Qt failures. prepareCairoContextSource the reason for the GTK failure. There are Windows failures. And probably iOS ones too. I’m going to say review-, but I did not spot any problems with the patch other than the fact that it fails to compile on all the non-Mac platforms.
Created attachment 203215 [details] Patch
Comment on attachment 203215 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=203215&action=review I can’t tell what you intend, Sam. Besides adoption of fooColor functions, this patch contains many examples of adding explicit Color() casts. Did you mean to include them or save them for a separate patch? > Source/WebCore/WebCore.exp.in:1 > +__ZN7WebCore14SecurityOrigin16setDomainFromDOMERKN3WTF6StringE Oops. > Tools/TestWebKitAPI/TestWebKitAPI.xcodeproj/project.pbxproj:99 > + 7C54FC711754712F00A8B391 /* SecurityOriginHash.cpp in Sources */ = {isa = PBXBuildFile; fileRef = 7C54FC6F17546D3000A8B391 /* SecurityOriginHash.cpp */; }; Oops. > Tools/TestWebKitAPI/Tests/WebCore/SecurityOriginHash.cpp:2 > + * Copyright (C) 2013 Apple Inc. All rights reserved. Oops.
Comment on attachment 203215 [details] Patch I didn't mean to upload this at all :(. Sorry for the noise.
Color has changed a bit since I filed this. I don't think this is worth keeping around.