On the wp-login.php and wp-register.php, the CSS and JavaScript was being mapped to the primary domain (i.e example.test) rather than the admin domain (i.e. darkmatter.test). Technically does not affect anything, but as the page is loaded on the admin domain, it should load its assets on the same domain to prevent any issues (especially cross-domain related problems).
With a fresh set of eyes, I noticed there are at least two links which should be going to the mapped URL: the "Go to [Site Name]" link and the Privacy Policy.
On the
wp-login.phpandwp-register.php, the CSS and JavaScript was being mapped to the primary domain (i.e example.test) rather than the admin domain (i.e. darkmatter.test). Technically does not affect anything, but as the page is loaded on the admin domain, it should load its assets on the same domain to prevent any issues (especially cross-domain related problems).With a fresh set of eyes, I noticed there are at least two links which should be going to the mapped URL: the "Go to [Site Name]" link and the Privacy Policy.
This was noticed and repaired in the upcoming 3.0.0, https://github.com/cameronterry/dark-matter/pull/103/commits/45c9b662e44342ad0e5c447df4a9a7e999aafa13, and this PR brings this fix into 2.x.x development due to the unknown release date for 3.0.0.