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!

본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Gaps apper after groups of characters in a rendered html, not in the code html, but whatever firefox uses to render what we see when open a page.

  • 7 답장
  • 1 이 문제를 만남
  • 29 보기
  • 최종 답변자: freethebit

more options

Loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong

If you take that long word put in a .html, and render, for me shows small gaps after groups of 9, 14, 18, 20... characters. The number of characters may change in different tags, like tables or a div, but always show small gaps. Tested in chromiun, but just works fine, without this gaps.

In online text editor does not show, but when rendered is shows.

Another detail, you need a css to force the word to break. And when this lines are created by the brake is when the gaps are visible. The css code used in that flow:


tag { word-break: break-word; //1 For chromiun word-wrap: break-word; //2 For chromiun overflow-wrap: anywhere; //3 For Firefox }

Loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong If you take that long word put in a .html, and render, for me shows small gaps after groups of 9, 14, 18, 20... characters. The number of characters may change in different tags, like tables or a div, but always show small gaps. Tested in chromiun, but just works fine, without this gaps. In online text editor does not show, but when rendered is shows. Another detail, you need a css to force the word to break. And when this lines are created by the brake is when the gaps are visible. The css code used in that flow: tag { word-break: break-word; //1 For chromiun word-wrap: break-word; //2 For chromiun overflow-wrap: anywhere; //3 For Firefox }
첨부된 스크린샷

글쓴이 freethebit 수정일시

모든 댓글 (7)

more options

See also:

This could be a problem with the font that is used.

You can right-click and select "Inspect Element" to open the builtin Inspector with this element selected.

You can check in the Rules tab in the right panel in the Inspector what font-family is used for selected text. You can check in the Font tab in the right panel in the Inspector what font is actually used because Firefox might be using a different font than specified by the website.

more options

cor-el said

See also: This could be a problem with the font that is used. You can right-click and select "Inspect Element" to open the builtin Inspector with this element selected. You can check in the Rules tab in the right panel in the Inspector what font-family is used for selected text. You can check in the Font tab in the right panel in the Inspector what font is actually used because Firefox might be using a different font than specified by the website.

It happens with any font, I use 3 different fonts (open sans, oswald, roboto mono). Ok, i tested without those, with system fonts, the problem still persist. I think there is a bug in firefox related to 'overflow-wrap'.

글쓴이 freethebit 수정일시

more options

Can you attach screenshots for comparison?


If content is wrapped then you can always expect some extra white-space. Only with a real monospace font this shouldn't happen unless the available width isn't a multiple of the character width. With a proportional font this could be possible if the next character doesn't fit.

more options

cor-el said

Can you attach screenshots for comparison? If content is wrapped then you can always expect some extra white-space. Only with a real monospace font this shouldn't happen unless the available width isn't a multiple of the character width. With a proportional font this could be possible if the next character doesn't fit.

Going deep, If the element that has 'overflow-wrap' also have 'letter-spacing=0.003em;' it will will show random gaps, but without the 'letter-spacing' only monospace fonts show gap.

more options
more options

Why such a very small value (letter-spacing:0.003em;) ? This would normally be about zero but after some characters this can result in a 1px shift (position is rounded).

Note that such a faint gray text on a black background like you use isn't very good readable (low contrast).

more options

cor-el said

Why such a very small value (letter-spacing:0.003em;) ? This would normally be about zero but after some characters this can result in a 1px shift (position is rounded). Note that such a faint gray text on a black background like you use isn't very good readable (low contrast).

About the small number, really? It make difference, in other browsers works fine, in Firefox it create small gaps that are not supposed to be there.

Low contrast is good for dark places, disagree with your opinion. Just try to read something with lower contrast in the darkness for more than 30minutes and you are going to feel the your eyes less tired than with high contrast.

The sidebar contrast is activated on :hover. it has a lower contrast because of when you reading long stuff you don't wan't your eyes to get distracted with a lot of stuff.

글쓴이 freethebit 수정일시