Currently, "amazon", "audible", and "wholefoodsmarket" include explicit TLDs. For the sake of maintenance and ease of adding new domains, these TLDs could be appended dynamically.
I'm not sure if this would be considered an expensive operation depending on when the browser actually executes the extension's code - need to research.
Also, using this method would make the assumption that Amazon owns all listed TLDs for "wholefoodsmarket" for instance, or could potentially containerize sites not actually owned by Amazon. This is probably a safe assumption for National TLDs, maybe not for others.
Currently, "amazon", "audible", and "wholefoodsmarket" include explicit TLDs. For the sake of maintenance and ease of adding new domains, these TLDs could be appended dynamically.
I'm not sure if this would be considered an expensive operation depending on when the browser actually executes the extension's code - need to research.
Also, using this method would make the assumption that Amazon owns all listed TLDs for "wholefoodsmarket" for instance, or could potentially containerize sites not actually owned by Amazon. This is probably a safe assumption for National TLDs, maybe not for others.