RESOLVED FIXED 109002
[BlackBerry] Export mimeType in NetworkJob
https://bugs.webkit.org/show_bug.cgi?id=109002
Summary [BlackBerry] Export mimeType in NetworkJob
Mary Wu
Reported 2013-02-05 20:13:42 PST
NetworkJob will analysize resource mimetype and set it to resourceResponse, we will pass it on to be used by other Streams like download stream.
Attachments
Patch (2.33 KB, patch)
2013-02-05 20:23 PST, Mary Wu
no flags
Patch (2.33 KB, patch)
2013-02-06 02:48 PST, Mary Wu
no flags
Patch (2.26 KB, patch)
2013-02-06 18:50 PST, Mary Wu
no flags
Mary Wu
Comment 1 2013-02-05 20:23:04 PST
Mary Wu
Comment 2 2013-02-06 02:48:58 PST
Yong Li
Comment 3 2013-02-06 06:51:39 PST
Comment on attachment 186806 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=186806&action=review > Source/WebCore/platform/network/blackberry/NetworkJob.cpp:958 > +const BlackBerry::Platform::String NetworkJob::mimeType() const > +{ > + String type = m_response.mimeType(); > + > + return type.isEmpty() ? "" : type.utf8().data(); > +} Why do we have to use utf8()? This always creates a new CString
Mary Wu
Comment 4 2013-02-06 18:44:31 PST
(In reply to comment #3) > (From update of attachment 186806 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=186806&action=review > > > Source/WebCore/platform/network/blackberry/NetworkJob.cpp:958 > > +const BlackBerry::Platform::String NetworkJob::mimeType() const > > +{ > > + String type = m_response.mimeType(); > > + > > + return type.isEmpty() ? "" : type.utf8().data(); > > +} > > Why do we have to use utf8()? This always creates a new CString nice, looks we already implemented that in StringBlackBerry. thanks
Mary Wu
Comment 5 2013-02-06 18:50:25 PST
WebKit Review Bot
Comment 6 2013-02-07 07:07:02 PST
Comment on attachment 186977 [details] Patch Clearing flags on attachment: 186977 Committed r142115: <http://trac.webkit.org/changeset/142115>
WebKit Review Bot
Comment 7 2013-02-07 07:07:07 PST
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.