WordPress.com

1. wadekwon
   Member
   Oct 12, 2012, 9:15 PM

   When editing a post or a page on my WordPress.com site, mediaofbirmingham.com, the right margin is not flush with the right edge of the WYSIWYG window.

   See screenshot.

   * It looks fine in preview and published modes.

   * I'm using Coraline theme, but it's not a theme problem; I switched temporarily to the Twenty Twelve theme, and the problem was still there.

   * Of all my WP.com blogs, this is the only one that has this problem.

   * No custom CSS: The only paid feature on this site is domain mapping.

   I suspect this is a bug, and not fixable on my end. But if anyone has an idea, please let me know.

   The blog I need help with is mediaofbirmingham.com.

2. absurdoldbird
   Member
   Oct 12, 2012, 9:24 PM

   That won't affect the way it appears in the post or page itself. And you can adjust that yourself by clicking and dragging the bottom right corner of the editor.

3. wadekwon
   Member
   Oct 13, 2012, 3:05 AM

   I could not. Dragging the lower right corner only works vertically, so it does not affect the width of the display window.

   I understand that it doesn't affect the post / page appearance. But it bothers me that I can't use the full width of the editing window, as I can in my other WP.com blogs.

4. thebiglaskowski
   Member
   Oct 17, 2012, 2:21 AM

   I too am experiencing this exact same issue and its driving me crazy trying to figure it out, I cannot properly format a simple blog post.

5. justpi
   Member
   Oct 17, 2012, 2:46 AM

   @wadekwon: It is theme related, but it's not a bug. The main edit box has a fixed width, no matter what the theme. In most themes, the text in the Visual editor covers the whole available width, which means that the Visual editor is not a WYSIWYG editor (in most cases the result on the published post is narrower). But in some themes (including Coraline and Twenty Twelve), the text in the Visual editor is constrained to the actual width of the published post, so in these cases the Visual editor becomes more of a WYSIWYG editor (and I'm surprised you don't like this). If you wish to "use the full width of the editing window", you can switch the editor to Text (=code).

6. wadekwon
   Member
   Oct 17, 2012, 5:12 PM

   Ah, now I understand. Thank you, justpi.

   The reason I don't like the "enhanced" margins is because it takes control away from the user (me). I'm perfectly capable of deciding if I need true WYSIWYG, or if I want to view the post in context in the Preview (which has been my habit for 7 years).

   Having a random theme override basic functionality is poor UI/UX. What if a theme designer decides to make the text area 1" wide? Chaos.

   And I prefer editing in WYSIWYG mode, not code/text/HTML mode.

   Oh well, in my book, this is still a bug, and a big one at that.

7. thebiglaskowski
   Member
   Oct 17, 2012, 5:30 PM

   Yes I was able to properly format a post and use the full space provided in the post editor by turning off the visual editor setting in my user account. @justpi, is there a setting in the css or anywhere that we could alter to allow full width use of our editors with WYSIWYG enabled?

8. justpi
   Member
   Oct 18, 2012, 1:11 AM

   @wadekwon: You're welcome.
   It's deliberate, so it's not a bug - it's an inconsistency (as you pointed out). If WP thinks that actual width instead of full width is better, they should apply it to all themes.
   And this would probably please many users: it's the first time I'm seeing a complaint like yours, while we often see complaints by users who arrange things based on what they see in the Visual editor and then get surprised that the published result is different.

   @thebiglaskowski: Not directly. The CSS editor allows you to modify the appearance of the actual blog (if you have the Custom Design upgrade), not the appearance of things on the dashboard. In theory, you can modify the latter if you use Firefox, install the Greasemonkey add-on, and create the right script; but I haven't tried it for this particular detail.

Topic Closed

This topic has been closed to new replies.