WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
UNCONFIRMED
111020
Plumb wasFetchedViaQUIC() into WebKit.
https://bugs.webkit.org/show_bug.cgi?id=111020
Summary
Plumb wasFetchedViaQUIC() into WebKit.
Ryan Hamilton
Reported
2013-02-27 15:37:03 PST
Plumb wasFetchedViaQUIC() into WebKit.
Attachments
Patch
(7.19 KB, patch)
2013-02-27 15:37 PST
,
Ryan Hamilton
fishd
: review-
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Ryan Hamilton
Comment 1
2013-02-27 15:37:26 PST
Created
attachment 190620
[details]
Patch
Darin Fisher (:fishd, Google)
Comment 2
2013-02-27 16:20:06 PST
Comment on
attachment 190620
[details]
Patch This doesn't need to be here. "wasFetchedViaSPDY" should also be removed. We can put these on the ExtraData object that the embedder gets to define. WebCore and WebKit don't need to know anything about SPDY or QUIC.
Ryan Hamilton
Comment 3
2013-02-27 16:52:51 PST
(In reply to
comment #2
)
> (From update of
attachment 190620
[details]
) > This doesn't need to be here. "wasFetchedViaSPDY" should also be removed. We can put these on the ExtraData object that the embedder gets to define. WebCore and WebKit don't need to know anything about SPDY or QUIC.
I do not know enough about WebKit to fully appreciate the ramifications of what you are proposing. Since we have extensions and existing JS code which expects to be able to read window.chrome.window.chrome.loadTimes().wasFetchedViaSpdy, it is desirable to maintain this interface. Are you proposing that we change the interface, or does ExtraData provide a different mechanism to populate the existing interface. Can you point me at an example?
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