Created attachment 569620 [details] rename_with_existing Description of problem: misaligned error messages appeared when trying to create/rename domain with existing name, blank name, over length name, invalid name. Version-Release number of selected component (if applicable): rhc-site-0.88.4-1.el6_2.noarch How reproducible: always Steps to Reproduce: 1.login to openshift website 2.go to /app/account page 3.try to create/rename namespace with illegal names. Actual results: misaligned error messages appeared Expected results: the error messages should show without UI issues. Additional info: see attachments for reference.
Created attachment 569621 [details] create_with_overlength
It seems this error "Your namespace must be letters or numbers with no spaces or symbols." will always there once you have a failure while creating domain.
This is what I was referring to earlier - looks like help-inline in this form wants to be left aligned, but it's not clear that it should. What does bootstrap do?
(In reply to comment #3) > This is what I was referring to earlier - looks like help-inline in this form > wants to be left aligned, but it's not clear that it should. What does > bootstrap do? <p class="help-inline">... should be within input-prepend-append div, currently it's not. This will align short messages to the right. Additional messages that are longer will clear left and appear left aligned, which would be appropriate. Looking at _form.html.haml I'm not sure how to position help-inline to be within that div.
ok fix is committed
checked on devenv_1670, The message "Your namespace must be letters or numbers with no spaces or symbols." stay there forever. But the error message still not align to the left. Please refer to attachment.
Created attachment 572124 [details] devenv_1670
(In reply to comment #5) Tested this issue on devenv_1674, the error message aligned to the left on Chrome17,but on firefox10,still has this issue. And the message "Your namespace must be letters or numbers with no spaces or symbols." will there forever,is this expected?
Fixed.
(In reply to comment #9) Verify this bug on devenv-stage_154, it has been fixed now.