We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Den här webbplatsen har begränsad funktionalitet medan vi utför underhåll för att förbättra din upplevelse. Om en artikel inte löser ditt problem och du vill ställa en fråga har vi vår gemenskap som väntar på att hjälpa dig på @FirefoxSupport på Twitter, /r/firefox på Reddit.

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Firefox doesn't wrap overlong text, but Chrome will. I want Firefox to wrap it also.

  • 7 svar
  • 1 har detta problem
  • 8 visningar
  • Senaste svar av JohnnyBeau

more options

FF 61,0,1 (64but) Windows 7

This Firefox will not wrap the overlong text on this Webpage when I Zoom in.

https://mailchi.mp/yabla/the-latest-from-yabla-it-nk12-105573?e=e0a9da419a

Chrome wraps it nicely, but I don't want to use Chrome.

Yes, I have wrap long lines True.

Any suggestions?

P,S. There is a similar problem with the email version of this page on Thunderbird.

FF 61,0,1 (64but) Windows 7 This Firefox will not wrap the overlong text on this Webpage when I Zoom in. https://mailchi.mp/yabla/the-latest-from-yabla-it-nk12-105573?e=e0a9da419a Chrome wraps it nicely, but I don't want to use Chrome. Yes, I have wrap long lines True. Any suggestions? P,S. There is a similar problem with the email version of this page on Thunderbird.

Alla svar (7)

more options

Hi, Long lines of text are wrapped by default. To check please Copy/Paste about:config to the Address Bar and Enter

In the page that opens there is a Search Bar the width of the page. Please Copy/Paste plain_text.wrap_long_lines make sure the setting is set for True. Other than that I have no idea as the text on the URL you sent is wrapped for me.

See if a Extension is the issue : Hello,

Try Firefox Safe Mode to TEST & see if the problem goes away. Firefox Safe Mode is a troubleshooting mode that temporarily turns off hardware acceleration, resets some settings, and disables add-ons (extensions and themes).

If Firefox is open, you can restart in Firefox Safe Mode from the Help menu:

  • Click the menu button New Fx Menu, click Help Help-29 and select Restart with Add-ons Disabled.

If Firefox is not running, you can start Firefox in Safe Mode as follows:

  • On Windows: Hold the Shift key when you open the Firefox desktop or Start menu shortcut.
  • On Mac: Hold the option key while starting Firefox.
  • On Linux: Quit Firefox, go to your Terminal and run firefox -safe-mode
    (you may need to specify the Firefox installation path e.g. /usr/lib/firefox)

When the Firefox Safe Mode window appears, select "Start in Safe Mode".

SafeMode-Fx35

If the issue is not present in Firefox Safe Mode, your problem is probably caused by an extension, theme, or hardware acceleration. Please follow the steps in the Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems article to find the cause.

To exit Firefox Safe Mode, just close Firefox and wait a few seconds before opening Firefox for normal use again.

When you figure out what's causing your issues, please let us know. It might help others with the same problem.

more options

Hi JohnnyBeau, that text makes heavy use of non-breaking spaces, which instruct the browser NOT to break lines there. For example:

In&nbsp;questo&nbsp;corridoio&nbsp;io&nbsp;ho&nbsp;anche&nbsp;il&nbsp;condizionatore&nbsp;dell'aria&nbsp;calda&nbsp;e&nbsp;fredda,&nbsp;che&nbsp;mi&nbsp;aiuta&nbsp;un&nbsp;po'&nbsp;a&nbsp;<strong>regolare</strong>&nbsp;la&nbsp;temperatura.

Firefox doesn't break that line at all; Chrome breaks it after the ' character. I don't know which is right or wrong; I'm not sure it matters because even in Chrome the layout is still wide enough to trigger a horizontal scroll bar (until the page flips to a narrow mobile layout).

According to some online chatter, this can be caused by pasting HTML into the TinyMCE editor, but whatever the cause, it's difficult for the reader to detect and fix.

As a brute force approach, you could use a snippet of script to change all the non-breaking spaces in a document to regular spaces. Easy to say, but not so easy to implement. Hopefully someone will be able to suggest a better workaround.

more options

Yes. I did try it in Safe Mode before I asked the question.

The wrap long lines = True, I'm including a Screen Shot.

I'm also including a screen shot of the page that shows the lines not wrapping. I must have something different than you.

Before I forget, thank you for looking at the problem.

Since I have the same problem in Thunderbird, with the same page in an email, there must be something in my settings that FF and TB don't like.

Thanks again.

more options

jscher2000, Your answer was helpful to see what the problem is, but I'm not so sure I want to put in any more time than I have on the problem.

What I found interesting in your response was that it came as an email and did not wrap at all. I don't assume you did it on purpose, but why did your note not wrap in TB? Or did you do it to illustrate a point?

Thanks for looking and responding.

more options

Hi JohnnyBeau, oh sorry about that. It didn't wrap because there are no spaces anywhere in the line.

more options

A possible workaround could be in inject a style rule to force a word break. It is not prefect, but might be acceptable.

Add code to the userContent.css file.


@-moz-document domain(mailchi.mp){
 body *{
  word-break: break-all !important;
  word-wrap: break-word !important;
 }
}
more options

cor-el,

I hopefully tried your solution, but it didn't work. I did learn about creating userContent.css and finding where to put it a good learning experience. So nothing lost for my part.

I noticed that the note I received in the email did not have !important in the css file, but the example here did. I tried it both ways.

I did close FF and restart FF before I tried it.