#13200 closed defect (bug) (invalid)
Problem with styling of Nav Menu screen
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | |
| Component: | Menus | Keywords: | |
| Focuses: | Cc: |
Description
Using twenty ten as parent theme to child in development and 3.0 nightlies. Just upgraded to last night's version and on refresh the attached image is what the appearance/menu now looks like. Looked great before. Just thought a quick mention of this conflict was in order~
Attachments (1)
Change History (5)
#1
@
16 years ago
- Cc dkikizas@… added
- Keywords wp_nav_menu removed
- Summary changed from Problem with Nav Menu to Problem with styling of Nav Menu screen
#3
@
16 years ago
- Milestone Unassigned deleted
- Resolution set to invalid
- Status changed from new to closed
- Version 3.0 deleted
#4
@
16 years ago
As stated, I just thought a mention of the conflict was in order because:
None of the other admin areas have this conflict.
Fluency admin is a very popular admin theme that is current as of 2.9.2.
I was thinking along the same lines as demetris in that if the conflict isn't necessary it would be best to avoid.
Since this has been closed as invalid, and the conflict is still there, I'm guessing it must be a necessary conflict so I'll head over and give the Fluency guys a heads up that they'll be broken when 3.0 releases.
r14287 is what caused this.
Since the issue appears in a custom admin style (Fluency Admin) rather that in the default admin style, I am not sure it belongs in the bug tracker of WordPress core, unless r14287 includes something that is not necessary or that can be avoided and/or that affects other plugins too.