more granular nextHopProtocol cases

[wesinator]

handle http/1.x explicitly, separate from empty protocol value
it seems some http/1.1 sites return a blank nextHopProtocol, but the official 1.1 value is http/1.1:

https://developer.mozilla.org/docs/Web/API/PerformanceResourceTiming/nextHopProtocol#value

[NyeUsr]

Awesome, thank you! Is there a reason for

Might be good to merge #1 and release before merging this and bumping to a new version.

As mentioned in #2 ? Both changes seem to work as an update when combined together.

[wesinator]

Ah, yes it would be fine to do both in one. I just didn't know if you wanted to separate the changes.
You could release one more Manifest v2 extension with this functionality change, then merge the mv3 and make a new release.