#2015 closed defect (fixed)
Browser doesn't show big text file
Reported by: | redbaron | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | normal | Milestone: | 0.9 |
Component: | version control/browser | Version: | 0.8.4 |
Severity: | major | Keywords: | |
Cc: | rhind@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
When I try to view in source browser a big text files (about 500 kb) it shows me only about first 50-100 kb of text, other part is blank
Attachments (1)
Change History (6)
by , 19 years ago
Attachment: | CorruptedText.PNG added |
---|
comment:1 by , 19 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
This was fixed in the trunk.
For 0.8.x, you can fix this manually by modifying the CSS:
Remove line 5 ( overflow: auto
) in htdocs/css/code.css
.
comment:2 by , 19 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
When I remove line 5 in htdocs/css/code.css and now it show me less then half, other part simply dissapear. When I click "original format" everything fine and I can see whole file.
comment:3 by , 19 years ago
This is really a problem similar to the one described in #1345.
Some browsers have problems when a large text is enclosed
in a block which has the overflow
property set to auto
:
- Internet Explorer is very slow.
- Firefox on Windows either shows a repeated garbage near the end, as demonstrated in your attachment:CorruptedText.PNG, or shows nothing (as described in your second comment, so I believe the CSS rule is still active somehow, can you check with the web developer tool bar/edit stylesheets?).
We decided to keep overflow: auto
only for the small code blocks
enclosed with {{{...}}}
in the wiki pages, but not for the source browser
nor for the attachments.
In the trunk, this is fixed for the source browser, but apparently not for the attachment view, as can be seen in the example given in #1345.
comment:4 by , 19 years ago
Cc: | added |
---|
comment:5 by , 19 years ago
Milestone: | → 0.9 |
---|---|
Resolution: | → fixed |
Status: | reopened → closed |
This was similar to the problem described in #1345.
Screenshot of corrupted text