You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Using the 'discover meteor' book code with reverse mode navbar]
Login buttons don't appear nicely when the sign-in is collapsed : the "Sign in" and "Create account" buttons appear on the side of the password textarea instead of aligned below. I edited the code of login_buttons_dropdown.html in accounts-ui-bootstrap-dropdown to add a div.
Also, with an inverse navbar, the labels "email" and "password" cannot be read. I fixed that making them bright blue but there is probably a better solution
login-dropdown-list div.dropdown-menu label
{
color: blue;
font-weight: bold;
}
Last, when the sign-in button is expanded, there is an animation slow-down that is not visible on other sites using bootstrap (for instance bootstrap 2.3.2 documentation). The slowdown is due to the {{loginbuttons}} and disappears when the command is removed. But I haven't been able to identify precisely the culprit.
The text was updated successfully, but these errors were encountered:
[Using the 'discover meteor' book code with reverse mode navbar]
Login buttons don't appear nicely when the sign-in is collapsed : the "Sign in" and "Create account" buttons appear on the side of the password textarea instead of aligned below. I edited the code of login_buttons_dropdown.html in accounts-ui-bootstrap-dropdown to add a div.
Also, with an inverse navbar, the labels "email" and "password" cannot be read. I fixed that making them bright blue but there is probably a better solution
login-dropdown-list div.dropdown-menu label
{
color: blue;
font-weight: bold;
}
Last, when the sign-in button is expanded, there is an animation slow-down that is not visible on other sites using bootstrap (for instance bootstrap 2.3.2 documentation). The slowdown is due to the {{loginbuttons}} and disappears when the command is removed. But I haven't been able to identify precisely the culprit.
The text was updated successfully, but these errors were encountered: