Title: [Plugin: Plugin Central] Issue with entry textarea positioning
Last modified: August 20, 2016

---

# [Plugin: Plugin Central] Issue with entry textarea positioning

 *  [stevemagruder](https://wordpress.org/support/users/stevemagruder/)
 * (@stevemagruder)
 * [13 years, 7 months ago](https://wordpress.org/support/topic/plugin-plugin-central-issue-with-entry-textarea-positioning/)
 * When using Plugin Central, I have to widen my browser so that the entry textarea
   is positioned correctly. If I don’t, it displays below the ads that display on
   the right.
 * Couldn’t the textarea be made to be more reflexive, so it can it in the regular
   spot without me having to widen my view?
 * [http://wordpress.org/extend/plugins/plugin-central/](http://wordpress.org/extend/plugins/plugin-central/)

Viewing 1 replies (of 1 total)

 *  Thread Starter [stevemagruder](https://wordpress.org/support/users/stevemagruder/)
 * (@stevemagruder)
 * [13 years, 7 months ago](https://wordpress.org/support/topic/plugin-plugin-central-issue-with-entry-textarea-positioning/#post-3112093)
 * “so it can _fit_ in the regular spot”

Viewing 1 replies (of 1 total)

The topic ‘[Plugin: Plugin Central] Issue with entry textarea positioning’ is closed
to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/plugin-central.svg)
 * [Plugin Central](https://wordpress.org/plugins/plugin-central/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/plugin-central/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/plugin-central/)
 * [Active Topics](https://wordpress.org/support/plugin/plugin-central/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/plugin-central/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/plugin-central/reviews/)

 * 1 reply
 * 1 participant
 * Last reply from: [stevemagruder](https://wordpress.org/support/users/stevemagruder/)
 * Last activity: [13 years, 7 months ago](https://wordpress.org/support/topic/plugin-plugin-central-issue-with-entry-textarea-positioning/#post-3112093)
 * Status: not resolved