What?

Determine internal vs external by new URL('https://mysite.com').host instead of new URL('https://mysite.com').origin. On trunk, when you use the same URL but change the http:// vs https://, one is considered external.

Why?

When determining whether a navigation link is internal or external, the previous implementation compared URLs by their origin (scheme + host + port). This caused links using http:// to be incorrectly classified as external when the site URL used https://, even if they pointed to the same domain.

How?

This PR fixes the comparison to use host instead of origin, so http://example.com/page and https://example.com/page are both treated as internal links to an https://example.com site.

Additionally, the window.location.origin fallback (used when homeUrl was not provided) has been removed. The homeUrl is now required for internal/external detection; without it, URL parsing fails gracefully and the link is treated as external.

A unit test covering the http/https case is included.

Testing Instructions

• Use the navigation block to add two manual, identical URLs to your navigation:
  • One with http:// - ie: http://localhost:8888
  • One with https:// - ie: https://localhost:8888
• Both should report "Page" and not "External"
• Add an external link, like http://test.com
• Should correctly report external

Testing Instructions for Keyboard

Screenshots or screencast