Opened 15 years ago
Closed 14 years ago
#19613 closed defect (bug) (fixed)
Select menus with long items overflow panels in the admin
| Reported by: | Master Jake | Owned by: | azaozz |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.4 |
| Component: | UI | Version: | 3.3 |
| Severity: | normal | Keywords: | has-patch dev-reviewed commit |
| Cc: | Focuses: |
Description
In the WordPress Admin, select menus which have long options may exceed the width of their parent meta box container.
Related ticket: #15114
Attachments (7)
Change History (17)
#2
@
15 years ago
Ah, you're absolutely right. What exactly do you mean by a regression though? Will the patch you linked to perhaps be included in the next WordPress version?
#3
@
15 years ago
- Keywords has-patch added
- Milestone Awaiting Review → 3.4
- Owner changed from to
- Status new → reviewing
It was added in [18453], but then removed in [18975] (not sure what the exact issue was):
http://core.trac.wordpress.org/changeset/18453#file1
http://core.trac.wordpress.org/changeset/18975#file10
Perhaps a more specific selector is needed here?
#6
@
14 years ago
- Resolution fixed
- Status closed → reopened
This breaks the action selects in IE 8 (19613.actions-ie8.png).
19613.patch sets max-width for parent page select only (which seems to be the main issue here).
19613.2.patch just fixes the action selects.
#7
follow-up:
↓ 8
@
14 years ago
Just noticed that the selects in Quick Edit are also moved to a second line in IE 8 (19613.quick-edit-ie8.png), so 19613.patch is probably safer.
#8
in reply to: ↑ 7
;
follow-up:
↓ 9
@
14 years ago
- Keywords commit added
Replying to SergeyBiryukov:
...19613.patch is probably safer.
Agreed. On the other hand I'm pretty sure we tested this in IE8 before, wondering what has changed... Anyways, +1 for 19613.patch.
#9
in reply to: ↑ 8
@
14 years ago
- Keywords dev-reviewed added
Replying to azaozz:
Replying to SergeyBiryukov:
...19613.patch is probably safer.
Agreed. On the other hand I'm pretty sure we tested this in IE8 before, wondering what has changed... Anyways, +1 for 19613.patch.
The patch looks good to me to - moving to a more targeted fix for the original issue.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
This has been reported before. I think it may be a regression. See #17043 from 5 months ago which is marked as fixed, and #3752.