Of course I can simply fix it overriding the Nav::Init method but maybe I overlooked something? Has the extra ‘nav’ class to be there for some reasons?
I made PR at first being convinced the problem lies in the wrong extra .nav class in the Nav element.
Today I checked it again and found that the behavior is caused by the logout button CSS style defined in web/css/site.css file:
/* align the logout "link" (button in form) of the navbar */
.nav li > form > button.logout {
padding: 15px;
border: none;
}
This ‘padding: 15px’ interferes with the other nav elements which have 0.5rem padding.
The fix is fairly simple but maybe I’ve made a mistake during BS4 extension installation? Should be this style overridden by some asset registered by extension itself?