Today the RouterLink directive will only reference an elements href attribute value (and preventDefault() on click events) if its elementRef's tagName is explicitly a or area. This presents a unique ...
I can load the main and aux outlets via navigateByUrl however I cannot determine the correct structure for a routerLink to load both? Loading aux or named routes appears to be broken or unsupported?
Some results have been hidden because they may be inaccessible to you
Show inaccessible results
Feedback