1331111 - Latest firefox does not preserve whitespace inside the "pre" tag

Status: RESOLVED WORKSFORME

(Core :: Layout: Text and Fonts, defect)

Description

[Ben White]

Attachment: example1.html

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20161208153507

Steps to reproduce:

I have a simple HTML test case attached.  In older versions of Firefox (such as 45.4.0 running on Linux), as well as in latest Chrome, it displays the embedded whitespace as I would expect.  In Firefox 50 (running in Windows 7), it collapses multiple spaces into a single space.  This is undesirable.

Comment 1

[Mark]

I have also seen this - initially on Win7 running Firefox 43.  After updating to FF-50, the problem remained.  My Options->Monospace was set to "Times New Roman" - with no monospace designation.  I changed it to "Arial monospace for SAP" and the problem went away.

Comment 2

[Loic]

Attachment: win7-ff50.jpg

It looks fine on my Win 7.

Comment 3

[Jonathan Kew [:jfkthame]]

(In reply to Ben White from comment #0)
> Created attachment 8826759 [details]
> example1.html
> 
> User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101
> Firefox/50.0
> Build ID: 20161208153507
> 
> Steps to reproduce:
> 
> I have a simple HTML test case attached.  In older versions of Firefox (such
> as 45.4.0 running on Linux), as well as in latest Chrome, it displays the
> embedded whitespace as I would expect.  In Firefox 50 (running in Windows
> 7), it collapses multiple spaces into a single space.  This is undesirable.

Please attach a screenshot showing how it displays for you. Thanks.

Comment 4

[Ben White]

Okay, I will do that on Monday Jan 16.

Comment 5

[Ben White]

Attachment: example1_capture.PNG

Screen shot showing how the example HTML is rendered in my Firefox browser.

Comment 6

[Jonathan Kew [:jfkthame]]

Strange; that doesn't match Loic's result (comment 2) at all.

Could you please (a) try with a fresh profile, to see if any local settings/addons/etc are affecting it, and if that doesn't help, (b) post your about:support content for us to see further details.

Comment 7

[Ben White]

Jonathan:  new profile fixed the problem, the display of example1.html now looks correct.  So, I think the next step for me is to start using the new profile.  I don't really want to spend the time figuring out which setting or addon in my profile is causing this.

Comment 8

[Ben White]

Moving the bug to resolved -- I am satisfied by creating a new profile.