Is your feature request related to a problem? Please describe.

The issue of URL routing has been discussed in the multi-branding strategy. The issue is related to the fact that multiple links within AS.com are hard-routed to www.alaskaair.com

Describe the solution you'd like

Currently, when a user of auro-hyperlink adds a href to the UI, it's not simply passed through to the internal <a> element, but it is run through a series of functions to ensure that the URL is written correctly to meet web security standards.

We can leverage this to dynamically look for the page's hostname. Instead of hard-coding the inserted hostname as we currently do, this would be more aware of the hostname of the page be it alaskaair.com or hawaiian.com, and on page render update the href to be the correct domain.

This update would also address many issues that teams have about testing code on lower QA environments where links are being hard-coded to AS.com and when tests are run, the test leaves the QA environment and causes issues with the tests.

Looking at the current footer, for example, some links look like this:

<auro-hyperlink ondark="true" href="https://www.alaskaair.com/content/about-us" type="nav" external="false">Who we are</auro-hyperlink>

That will have this code in the shadow DOM:

<a part="link" class=" hyperlink hyperlink--nav hyperlink--ondark " href="https://www.alaskaair.com/content/about-us"><slot>Who we are</slot></a>

With this update, authors would not have to update their href code, but on the fly, the https://www.alaskaair.com/ would be converted to be hawaiian.com and the shadow DOM href would look like this.

<a part="link" class=" hyperlink hyperlink--nav hyperlink--ondark " href="https://www.hawaiian.com/content/about-us"><slot>Who we are</slot></a>

Describe alternatives you've considered

Asking all teams to manually update their HREF code.

Additional context

There is another feature request that should be considered be done at the same time.

• Handle URL object when passed to href attribute #241

Exit criteria

1. Dynamic Hostname Resolution:

   • auro-hyperlink dynamically updates href based on the page’s hostname (alaskaair.com, hawaiian.com, etc.).

2. Shadow DOM Updates:

   • Shadow DOM reflects the updated href correctly for all domains.

3. Web Security Compliance:

   • All URLs meet web security standards after updates.

4. QA Environment Compatibility:

   • Links resolve correctly in QA environments without breaking tests.

5. Backward Compatibility:

   • Existing auro-hyperlink implementations require no manual updates.

6. Documentation & Testing:

   • Updated documentation and passing tests (unit, integration, and end-to-end) for all scenarios.

7. Cross-Team Coordination:

   • Dependencies, including issue #241, are resolved.

8. Deployment:

   • Feature deployed and validated in production with no issues.