Litehouse reporting not using http2 when content delivered using quic

[AJHopper]

• Provide the steps to reproduce

1. Run LH on https://southernswords.co.uk (or even https://www.litespeedtech.com, or https://google.com)

2. Jump to the best practices section of the report and notice it says not delivered via http2

What is the current behavior?

it currently lists the sites as not using http2

What is the expected behavior?

as quic requires http2 (or a modied google version / http3) this should surely show this as either using http2 or not flag this as a red issue - as quic is essentially a modified / google improved tech?

[patrickhulce]

Thanks for filing @AJHopper! I'm not able to reproduce this issue with LH 5.5.0 on any of those URLs. What environment were you testing in? (The rest of the bug template report that got deleted 😃)

[AJHopper]

Hey @patrickhulce , this is when running is chrome 77, using either the inspector tools audit section - which is running Lighthouse 5.2 or, when using the latest extensions install which is running 5.4 from the looks of it - haven't run it on LH 5.5

[patrickhulce]

Hmm, I'm not able to reproduce this with the extension 5.4.0 on those URLs either. Are there any other steps in your testing process that might be relevant for us to be able to reproduce?

[AJHopper]

Hey Patrick, nothing else going on really steps wise - I've not changed anything on the Lighthouse extension, and I've run this from Chrome on home PC - along with having tested from several systems at work and I get the same result on all of them - not sure what a difference would be that would cause you not to be able to see it =/