Location's implementation is responsible to determine whether an navigation should happen or not.  Since Location is defined in HTML spec, assign Components=Blink>HTML.

That test is occasionally flaky:

https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_tests&tests=external%2Fwpt%2Fhtml%2Fbrowsers%2Fhistory%2Fthe-location-interface%2Flocation-protocol-setter-non-broken.html

Note the green does not mean passing; there are expectations with FAIL in:

third_party/WebKit/LayoutTests/platform/linux/external/wpt/html/browsers/history/the-location-interface/location-protocol-setter-non-broken-expected.txt
third_party/WebKit/LayoutTests/platform/win/external/wpt/html/browsers/history/the-location-interface/location-protocol-setter-non-broken-expected.txt
third_party/WebKit/LayoutTests/platform/mac/external/wpt/html/browsers/history/the-location-interface/location-protocol-setter-non-broken-expected.txt

clamy is the "Browser Side Navigation Linux" FYI bot yours? It seems both these tests are broken on that bot. I haven't dug into the details.

The relevant spec is around here-ish <https://html.spec.whatwg.org/#dom-location-protocol>, the protocol setter step: "If copyURL's scheme is not an HTTP(S) scheme, then terminate these steps."

Bulk disowning per sshruthi's email about bug triage best practices.