Closed Bug 248290 Opened 21 years ago Closed 21 years ago

Option to line wrap text files

Categories

(Firefox :: General, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 16909

People

(Reporter: d.drury, Assigned: bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9 Firefox is not really suitable for reading plain text files because line wrapping is not possible. While this may be ideal in *some* circumstances, in many cases it is a drag. An option should exist to view any text with line wrapping, in order to avoid horizontal scrolling. This would enable Firefox to read plain text based e-books such as those produced by Project Guttenberg. Reproducible: Always Steps to Reproduce: 1. Visit a site that has .txt files on it such as http://www.gutenberg.net/ 2. View a .txt file Actual Results: Open the file in another reader because text wrapping isn't happening This might also allow overriding <pre> tag line wrapping, providing a nice workaround for the highly annoying Bugzilla line wrapping bug which hasn't been fixed for six years! Would also improve usability of View Source. Should be an option, because there will be cases where line wrapping should be off.
Forget the Bugzilla bug - that seems to be a problem with Proxomitron, not Bugzilla - see http://bugzilla.mozilla.org/show_bug.cgi?id=11901 for details of the line wrapping bug.
Dup of bug 16909.
That is a Mozilla feature request - this is a Firefox feature request. Are they not handled separately?
*** This bug has been marked as a duplicate of 16909 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Isn't this a bug covering adding UI to Firefox to enable this once the ability is there from bug 16909?
So this will get fixed in Firefox if it ever gets fixed in Mozilla - or now it has been marked as a dupe, perhaps when it is fixed in Mozilla it will never get fixed in Firefox? Is that how it works? How *does* it work for these two similar but distinct projects?
You need to log in before you can comment on or make changes to this bug.