RESOLVED FIXED 104570
[Coverity] [GTK] Remove some redundant null checks in DumpRenderTree
https://bugs.webkit.org/show_bug.cgi?id=104570
Summary [Coverity] [GTK] Remove some redundant null checks in DumpRenderTree
Martin Robinson
Reported 2012-12-10 10:17:24 PST
We shoul remove some redundant null checks in DumpRenderTree.
Attachments
Patch (3.17 KB, patch)
2012-12-10 10:52 PST, Martin Robinson
no flags
Patch (3.17 KB, patch)
2012-12-10 15:33 PST, Martin Robinson
dbates: review+
Martin Robinson
Comment 1 2012-12-10 10:52:20 PST
Martin Robinson
Comment 2 2012-12-10 15:33:59 PST
Daniel Bates
Comment 3 2012-12-10 16:18:46 PST
Comment on attachment 178651 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=178651&action=review OK. This patch doesn't change the existing functionality. That is, we currently return an empty string for the NSURLRequest portion of the willSendRequest string when soupMessage is null. I'm unclear how some ports came to the decision to return an empty string for the NSURLRequest portion of the willSendRequest string and some ports return a NSURLRequest string with "(none)" for the HTTP method. > Tools/DumpRenderTree/gtk/DumpRenderTree.cpp:1235 > + path.data(), mainDocumentURIString.data(), soupMessage->method)); For completeness, the Mac and EFL ports return "(none)" when the HTTP method isn't known.
Martin Robinson
Comment 4 2012-12-11 05:53:27 PST
(In reply to comment #3) Thanks for the review! > For completeness, the Mac and EFL ports return "(none)" when the HTTP method isn't known. Dan Winship, the libsoup maintainer, informs me that the method is "GET" by default for SoupMessages. The only way that it is null is if you manually override it (which as far as I know, we never do). I cannot find any examples of test expectations that "have the (none)" output as well.
Martin Robinson
Comment 5 2012-12-11 05:54:15 PST
Martin Robinson
Comment 6 2012-12-12 16:41:54 PST
Note You need to log in before you can comment on or make changes to this bug.