Page 1 of 1
Devnet Width Issue in Firefox
Posted: Sun Feb 12, 2006 9:25 pm
by Benjamin
I am using a Firefox browser on Linux Fedora and some of the posts on this web site cause the page to be so wide I have to use the horizontal scrollbar to read the entire post. Does anyone else have this problem. I haven't nailed down what is causing it, I am just wondering if anyone else has this problem?
Posted: Sun Feb 12, 2006 9:49 pm
by feyd
It's an issue with all browsers, but the source is someone posting in a
Code: Select all
tag that doesn't wrap due to no spaces to wrap with.
Posted: Sun Feb 12, 2006 9:53 pm
by Benjamin
Perhaps wordwrap() could be added to the output of code, php and qoute.
Code: Select all
<?php
$text = "A very long woooooooooooord.";
$newtext = wordwrap($text, 8, "\n", 1);
echo "$newtext\n";
?>
I understand the width of the page is variable so maybe it could just add a space every X'th character so that the browser can wrap it as required.
Or, possibly an even better solution, put the code, php and qoute output into a div with a fixed width of say 90% and set the overflow to scroll.
Posted: Sun Feb 12, 2006 9:58 pm
by feyd
php tags do not have the issue.
Posted: Sun Feb 12, 2006 10:00 pm
by josh
That's not a good idea, it could effect how the script runs if whitespace is added in the wrong place, for instance if someone had binary data hard coded in a string a space would corrupt it
Posted: Sun Feb 12, 2006 10:01 pm
by Benjamin
jshpro2 wrote:That's not a good idea, it could effect how the script runs if whitespace is added in the wrong place, for instance if someone had binary data hard coded in a string a space would corrupt it
Yeah your right, I was just brainstorming. I think that using the css overflow attribute would be the best solution.
Posted: Sun Feb 12, 2006 10:33 pm
by Roja
feyd wrote:php tags do not have the issue.
So perhaps map the code tags to php tags?
Are there many posts that post code that the php tags would break?
Posted: Sun Feb 12, 2006 11:39 pm
by feyd
I don't think there's a point in making changes to a construct which we are about to change entirely soon after.
Posted: Mon Feb 13, 2006 12:10 am
by Benjamin
feyd wrote:I don't think there's a point in making changes to a construct which we are about to change entirely soon after.
Are there planned changes for the rendering of code and qoute tags?
Posted: Mon Feb 13, 2006 12:14 am
by josh
Yeah, they're using a new syntax highlighter
Posted: Mon Feb 13, 2006 12:23 am
by Roja
feyd wrote:I don't think there's a point in making changes to a construct which we are about to change entirely soon after.
Which construct? What changes?
This loops back nicely to the need for at least a locked message with coming changes that I mentioned in another suggestion thread. We have no idea what you are talking about.
Posted: Mon Feb 13, 2006 12:44 am
by feyd
I was referring to the upcoming changes for the function linking in php tags. We're still working out the details, so I don't want to go modifying code just yet..
Posted: Mon Feb 13, 2006 3:11 am
by Jenk
Can't you just change the style of the