WordPress.org

Make WordPress Core

#46674 closed defect (bug) (wontfix)

Twenty Eleven: Long non-breaking text strings can cause horizontal scrolling

Reported by: ianbelanger Owned by: ianbelanger
Milestone: Priority: normal
Severity: normal Version:
Component: Bundled Theme Keywords: has-patch has-screenshots close
Focuses: Cc:

Description

While fixing #36346 I noticed that all Bundled Themes have some sort of word-wrap issues when using long non-breaking text strings. While this might be an edge case issue, I believe that it warrants fixing. Also, there doesn't seem to be any backwards compatibility issues.

In order to better track this issue in each theme, I am separating #36346 into separate tickets per theme.

Attachments (5)

46674.diff (1.4 KB) - added by ianbelanger 16 months ago.
Fixes word-wrap issues
46674-twenty-eleven-site-title-before.PNG (63.0 KB) - added by ianbelanger 16 months ago.
#site-title before in Chrome
46674-twenty-eleven-site-title-after.PNG (28.3 KB) - added by ianbelanger 16 months ago.
#site-title after in Chrome
46674-twenty-eleven-post-title-before.PNG (24.9 KB) - added by ianbelanger 16 months ago.
.entry-title before in Chrome
46674-twenty-eleven-post-title-after.PNG (46.3 KB) - added by ianbelanger 16 months ago.
.entry-title after in Chrome

Download all attachments as: .zip

Change History (16)

@ianbelanger
16 months ago

Fixes word-wrap issues

#1 @ianbelanger
16 months ago

  • Keywords has-patch needs-testing added

46674.diff adds

-webkit-hyphens: auto;
-moz-hyphens: auto;
hyphens: auto;
word-wrap: break-word;

to these selectors:

#site-title,
#site-description,
#content .entry-title,
.entry-content,
.entry-summary,
#comments

to prevent horizontal scrolling when long non-breaking text strings are used.

However, hyphens: auto; currently only works in Firefox. Unfortunately nothing worked for me in Chrome, IE11 or Edge.

This patch was tested on a Windows 10 machine, in Firefox, Chrome, IE11 and Edge browsers

Testing in other OS's and browsers would be appreciated.

@ianbelanger
16 months ago

#site-title before in Chrome

@ianbelanger
16 months ago

#site-title after in Chrome

@ianbelanger
16 months ago

.entry-title before in Chrome

@ianbelanger
16 months ago

.entry-title after in Chrome

#2 @ianbelanger
16 months ago

  • Keywords has-screenshots added

#3 @ianbelanger
16 months ago

  • Milestone changed from Awaiting Review to 5.2

This ticket was mentioned in Slack in #core by jeffpaul. View the logs.


15 months ago

#5 @JeffPaul
15 months ago

Per input in today's bugscrub, @dswebsme looking to test this on a Mac and update later today.

#6 @dswebsme
15 months ago

  • Keywords needs-testing removed

Patch looks good on Mac.

Tested in Chrome, Safari and Firefox.

Tested Site Title, Site Description, Post Title, Page Title, Content and Comments with non-breaking strings.

Mac results reflect AFTER screenshots captured by @ianbelanger.

Noting an edge case where pages with long non-breaking titles added to a menu result in horizontal scrolling. This could be addressed in a separate issue as menus can be edited via the UI to solve the issue.

#7 @ianbelanger
15 months ago

  • Keywords commit added

Thanks for testing @dswebsme.

I'm marking this for commit

#8 @SergeyBiryukov
15 months ago

Just wanted to note that there are some previous discussions on long non-breaking text strings in bundled themes: #25008, #25232, #29971, all closed as wontfix due to being an edge case. Should we revisit those discussions before making a decision on commit here?

#9 @laurelfulford
15 months ago

I added a comment to #36346 re: the previous tickets closed as wontfix -- it seemed like it'd be easiest to centralize that discussion in one spot. Any feedback/thoughts would be appreciated there!

#10 @laurelfulford
15 months ago

Thanks for tackling this @ianbelanger! I figured I could check these over while this issue is discussed in #36346 :)

I noticed for the #comments styles that were added for Twenty Eleven, there are no prefixes -- is this deliberate? Those styles are also indented with spaces rather than tabs.

Also, similar to my comment in #46704, what do you think about adding the -ms- prefix to hyphens as well, for Edge and IE 10-11?

#11 @ianbelanger
15 months ago

  • Keywords close added; commit removed
  • Milestone 5.2 deleted
  • Resolution set to wontfix
  • Status changed from assigned to closed

As per the discussion in #36346, I am closing this as a wontfix

See comment for details https://core.trac.wordpress.org/ticket/36346#comment:40

Note: See TracTickets for help on using tickets.