WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 8 years ago

#22219 closed defect (bug) (invalid)

Text beyond the boundary in view.

Reported by: fanyy1984 Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.4.2
Component: Editor Keywords: needs-patch reporter-feedback
Focuses: Cc:

Description

I paste a segment of words like this:
debug debug debug debug debug debug debug. debug debug debug debug debug debug.  debug debug debug debug debug. debug did not enjdebugoy it.  debug debug debug and a debug woman were debug bedebughind me. They debug debug loudly. I goddebugebugt very angdebugry. I could not hear the actors. I debug round. debug looked adebug the man debug the wdedebugbug angdebugrily. They didebugd nodebugt pdebugay adebugy debug. In debug debug, I debug notdebug it. I turned rdebug again. 
Text beyond the boundary in view.

Attachments (1)

20121018214232.png (12.4 KB) - added by fanyy1984 8 years ago.
The same problem in WordPress Trac

Download all attachments as: .zip

Change History (4)

@fanyy1984
8 years ago

The same problem in WordPress Trac

#1 in reply to: ↑ description @fanyy1984
8 years ago

Replying to fanyy1984:

I paste a segment of words like this:
debug debug debug debug debug debug debug. debug debug debug debug debug debug.  debug debug debug debug debug. debug did not enjdebugoy it.   
Text beyond the boundary in view.

#2 @helenyhou
8 years ago

  • Keywords reporter-feedback added

Are these perhaps nonbreaking spaces in between the words? A nonbreaking space would do exactly that, and if I edit your comment and delete the spaces and re-enter them normally, it seems fine again. Where are you copying this from?

#3 @johnbillion
8 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

The character you're using for spaces is unicode character U+00A0 which is a non-breaking space.

Closing as invalid as this is not a WordPress issue.

Note: See TracTickets for help on using tickets.