Firefox Multi-Account Containers | Container Name in URL Bar
Firefox 126.0.1 displays a very long name of a container completely in the URL bar.
Firefox 127.0 truncates container names
AWS long account and role names make keeping the long name very convenient (works with the 'AWS SSO Containers' Add-On
Избрано решение
Thank you for the Github link. It sounds as though this was intentional to ensure that the URL wasn't obscured.
The restriction is in a built-in style sheet, any characters beyond 8em in width are trimmed:
If this is a big problem, you could consider delving into the unsupported realm of userChrome.css rules to override built-in rules. In this case, you could use:
#userContext-label {
max-width: unset !important;
}
The effect is visible in the attached screenshot (which obviously shows a lot of other modifications). If you are new to userChrome.css and want to learn more, I have a site here:
Note: The How To videos are missing the last step about the about:config change.
Прочетете този отговор в контекста 👍 1Всички отговори (3)
Itai said
Firefox 126.0.1 displays a very long name of a container completely in the URL bar. Firefox 127.0 truncates container names AWS long account and role names make keeping the long name very convenient (works with the 'AWS SSO Containers' Add-On
More information here https://github.com/mozilla/multi-account-containers/issues/2641
Избрано решение
Thank you for the Github link. It sounds as though this was intentional to ensure that the URL wasn't obscured.
The restriction is in a built-in style sheet, any characters beyond 8em in width are trimmed:
If this is a big problem, you could consider delving into the unsupported realm of userChrome.css rules to override built-in rules. In this case, you could use:
#userContext-label {
max-width: unset !important;
}
The effect is visible in the attached screenshot (which obviously shows a lot of other modifications). If you are new to userChrome.css and want to learn more, I have a site here:
Note: The How To videos are missing the last step about the about:config change.
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.