Description of problem: When creating project with more than 63 characters, it will give error message indicating project name must be no more than 63 characters, this message is not shown well on Safari 9.1, only reproduces in Safari Version-Release number of selected component (if applicable): openshift3/registry-console:3.3 How reproducible: Always Steps to Reproduce: 1.Login to registry-console 2.Click "New project" 3.Set Name with more than 63 characters "uebqghutexcfoychgdnjlxtlmcdplujajqqrcfqomckmbdnagdiqyooklqbuhvwbztxtmk" 4. Hit on "Create" Actual results: 4. Error message is displayed out of message boarder Expected results: 4. Error message should be displayed well Additional info:
Created attachment 1198151 [details] MessageOutOfBoarder
I'm able to reproduce this, and I think I have a good fix for it. Will open a PR upstream.
Pull request here https://github.com/cockpit-project/cockpit/pull/5070
Created attachment 1204052 [details] 63 length out of border on overview check "Images by project" border
Mac safari has a display issue on overview page when length of project name is 63 characters. Project name out of the border. Suggest to append "..." at the end of the name inside "Images by project" border. Please refer to attachment 1204052 [details] (63 length out of border on overview ) Tested on Mac Safari 9 against registry version openshift3/registry-console:3.3
To clarify: fixed upstream in Cockpit 119
Fixed in any image that uses Cockpit >= 119
This is fixed in image openshift3/registry-console:3.4-1 or newer.
Checked against image openshift3/registry-console:3.4-1 1. Create a project with more than 63 characters, show error message correctly on Safari 10.0.1 2. Create a project with 63 characters, check project name on overview, project name is shown correctly Move to VERIFIED
Created attachment 1231008 [details] CreateProjectWithMoreThan63Chars
Created attachment 1231009 [details] CheckProjectWith63CharsOnOverview
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:0066