Another interesting related area is designing URLs for third-party components.
Third-party component have to coexist with existing site navigation logic, so generally you can't safely add URL-based configuration to such a component.
Fortunately, configuration can now be stored in fragment directives in order to hide this from normal site routing. e.g.
Third-party component have to coexist with existing site navigation logic, so generally you can't safely add URL-based configuration to such a component.
Fortunately, configuration can now be stored in fragment directives in order to hide this from normal site routing. e.g.
With fragment directives, location.href and location.hash exclude the additional content in the hash after :~:This is used in Transcend Consent Management for configuring parameters to debug and simulate various privacy experiences[1].
1. https://docs.transcend.io/docs/consent-management/reference/...