Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I don't have a problem with either 4095 or 4096 x's using Firefox 1.0.7 on Fedora Core 4

    Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7
  • I can confirm on Firefox 1.5 on Mac.

    Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

    But it works fine on 1.5/Win!
  • https://bugzilla.mozilla.org/show_bug.cgi?id=302294 [mozilla.org]

    One of the side effects is "invisible text" which appears to be what you ran into. I wonder if Javascript can still get to it, or if that how you found this problem in the first place?
  • I have replicated the problem, but only if there are 4096 non-newline characters or more in a single line.

    Succeeds:
    perl -le'print "",("x" x 4095),"\n"' > ! test.txt

    Fails:
    perl -le'print "",("x" x 4096),"\n"' > ! test.txt

    Succeeds:
    perl -le'print "",(("x" x 4095),"\n")x2' > ! test.txt
  • perl -e 'print "X"x8192' > firefoxx.txt

    File opens and renders fine in Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.10) Gecko/20050925 Firefox/1.0.4 (opened locally or downloaded from the web).

  • No. Whether I use 4,096 or 40,960 characters – it always renders.

    Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920 Firefox/1.0.7