Opened 11 years ago
Closed 11 years ago
#279 closed defect (bug) (duplicate)
responsive formatting hides page content below menu
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Component: | Plugin Directory | Keywords: | |
| Cc: |
Description
In Chrome with Viewport: 938px x 916px the menu pushes all of the main content down below the menu which creates two plus screens of scrolling and the effect that a user may perceive the page as being blank or empty. At Viewport: 989px x 916px this effect disappears and content renders as expected. This happens on most pages within .org, but an example would be: http://wordpress.org/plugins/search.php?q=git also see attached image with a screen capture of the issue.
This appears to be from the wp4.css line 914 and the fixed width of the column and the column id sidebar with the menu which is not floated left but may need to be to fix this issue.
Attachments (1)
Change History (4)
#2
follow-up:
↓ 3
@
11 years ago
- Component changed from General to Plugins Directory
I'm a plugin author and I love providing good support to the users of my plugin.
From last few months, I noticed - the header and footer of the entire WordPress.org was made responsive; but not the content area of individual sites (like plugins directory) & this has broken the layout.
Honestly, since then - I hate visiting the directory & support forum from mobile devices. Is there any way I can contribute to make the plugins directory responsive?
Sorry - but I'm kind of a newbie here, willing to make a contribution. Some guidance / instructions would be appreciated.
Regards,
Sujay
#3
in reply to:
↑ 2
@
11 years ago
- Resolution set to duplicate
- Status changed from new to closed
Replying to brainstormforce:
Is there any way I can contribute to make the plugins directory responsive?
[...] willing to make a contribution. Some guidance / instructions would be appreciated.
We've been working on the responsiveness of the sites in phases, starting with the global header/footer, so it's still in transition.
We'd love for you to help out. I think the first step would be to get caught up on #270 and submit a patch to build on the work that's already been done there.
If you'd like some more background info on the Meta team and the network of WordPress.org sites in general, check out these pages:
- https://meta.trac.wordpress.org/ - Overview
- http://make.wordpress.org/meta/ - The team's P2
- https://meta.svn.wordpress.org/ - The source code repository
- http://irclogs.wordpress.org/chanlog.php?channel=wordpress-meta - Logs for the #wordpress-meta IRC channel
screencap