FF 68 - Is the "wrap_long_lines" setting being ingnored?
9 posts
• Page 1 of 1
After I updated to FF 68 on my desktop I noticed that long lines are wrapping to fit the window, even though I have set "plain_text.wrap_long_lines" to be "false" in about:config.
It is like this setting is now being ignored. For what it is worth, I now have the same problem on my Android phone when it updated to FF 68. If I'm reading correctly, they've killed it.
Bug 1459483 Remove broken support for plain_text.wrap_long_lines in subframes. |-> Bug 1514655 Plaintext documents in subframes (or <object>) don't get word-wrapping Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript I do not think this is the same thing. But if I read it correctly and it applied here, I would see the opposite (word wrap will not enable).
What I am seeing is in relation to a setting in about:config. The pages I am viewing are plain text, not HTML. Everything had displayed fine up to 67.x, but now 68 no good. While view_source.wrap_long_lines is "view source", see if it might not have an effect?
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript Interesting!
In about:config "view_source.wrap_long_lines" is indeed set to "false" and when I "view page source" it works; that is, the lines do not wrap. The text file I am viewing looks as it should! The only difference is the lines are shifted to the right to accommodate for line numbers, I assume. (Being a plain text file and not HTML there are no line numbers presented.) A nice work around, but would be nicer if it were back to normal. ![]() Does anyone know what is required to get this functionality back so plain text files can be viewed correctly by default?
Is there a userChrome entry that can be edited? plain_text.wrap_long_lines looks to be working in FF 70 (default value is 'true').
(Don't have a 68 on hand to test against.) My test file, test.TXT:
Save it, drag it into a FF window... Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript 65 works.
68.0.1 fails. 70 works. (Don't know about 69 offhand. So at the least, you might expect things to be working by 70's release ![]() Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript Yup. Updated to 68.0.1 this morning and it is still bad.
The View Source trick still works which helps for now.
9 posts
• Page 1 of 1
Who is onlineUsers browsing this forum: No registered users and 0 guests |
![]() |