OpenPGP keys field may overlap next field in a user profile
Bug #1996775 reported by
Nathan Teodosio
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Nathan Teodosio | ||
Bug Description
Depending on where the OpenPGP box is placed in a user's page, it may overlap the next field, even with reasonably small font sizes.
The attached picture shows how Firefox at 100% zoom level with Ubuntu font renders that field for https:/
Also verified in Chromium.
Related branches
~cjwatson/launchpad:fix-openpgp-keys-style-logged-out
- Colin Watson (community): Approve
-
Diff: 31 lines (+5/-3)2 files modifiedlib/lp/registry/stories/person/xx-person-home.rst (+4/-2)
lib/lp/registry/templates/person-portlet-contact-details.pt (+1/-1)
~cjwatson/launchpad:openpgp-keys-style-logged-out
- Guruprasad: Approve
-
Diff: 15 lines (+1/-2)1 file modifiedlib/lp/registry/templates/person-portlet-contact-details.pt (+1/-2)
~nteodosio/launchpad/+git/launchpad:master
- Colin Watson (community): Approve
-
Diff: 12 lines (+1/-0)1 file modifiedlib/lp/registry/templates/person-portlet-contact-details.pt (+1/-0)
Revision history for this message
| Nathan Teodosio (nteodosio) wrote | #1 |
| tags: | added: confusing-ui lp-registry ui |
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in launchpad: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Nathan Pratta Teodosio (nteodosio) |
| Changed in launchpad: | |
| status: | In Progress → Fix Released |
Revision history for this message
| Nathan Teodosio (nteodosio) wrote | #2 |
Revision history for this message
| Nathan Teodosio (nteodosio) wrote | #3 |
Revision history for this message
| Colin Watson (cjwatson) wrote | #4 |
| Changed in launchpad: | |
| status: | Fix Released → In Progress |
Revision history for this message
| Nathan Teodosio (nteodosio) wrote | #5 |
| Changed in launchpad: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Although this is fixed when I'm logged in, it's not when I'm not.