[Webkit-unassigned] [Bug 254552] New: Web Inspector: "h3" protocol not appearing in network panel protocol column

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=254552

            Bug ID: 254552
           Summary: Web Inspector: "h3" protocol not appearing in network
                    panel protocol column
           Product: WebKit
           Version: Safari 16
          Hardware: Mac (Apple Silicon)
                OS: macOS 13
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Web Inspector
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: odinman08 at me.com
                CC: inspector-bugzilla-changes at group.apple.com

Created attachment 465619

  --> https://bugs.webkit.org/attachment.cgi?id=465619&action=review

Chrome dev tools showing h3 protocol vs Safari showing blank

Steps
- Use Safari Version 16.4 (18615.1.26.11.22). Running on M2 MacBook air.
- Visit www.jetblue.com which, according to https://http3check.net/?host=www.jetblue.com, has QUIC & HTTP/3 supported.
- inspect page
- switch to network tab
- Right click table column headings and ensure "Protocol" is visible.
- Refresh the page 

Observe that there's no network calls labeled as "H3".

background:

It's my understanding that Safari 16.4 has enabled Http/3 by default as per https://bugs.webkit.org/show_bug.cgi?id=251952 Though https://caniuse.com/http3 still has it marked as "not supported by default"


I'm a product owner so not as technical but it's my understanding that engineers on my team have enabled http3 on our infustructure and our services should be making requests with it. When we looked at Google Chrome inspect tools to validate, we could see that some network calls switch from h2 protocol to many h3. But in Safari I don't see that. I know that first connections are on http/2 but on refresh a few times I'd expect to see H3.

see attached comparison of Chrome protocols vs safari 16.4

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230327/583647d1/attachment-0001.htm>