Re: cvs: php-bugs-web / bug.php style.css /include functions.inc

From: Date: Tue, 16 Dec 2003 08:27:48 +0000
Subject: Re: cvs: php-bugs-web / bug.php style.css /include functions.inc
Groups: php.mirrors 
Request: Send a blank email to php-mirrors+get-22574@lists.php.net to get a copy of this message
> > >>>2. Don't you think that adding a monospaced font for the div would solve > > >>>the whole problem (since that was the only problem with highlighting > > >>>wasn't it?). > > >> > > >>Hm, well it was already in <code>, so it was fine monospaced... So what > > >>was the problem with the highlighted version??? > > > > > > Unreadable, adds unnecessary overhead to the already high load, > > > won't work for scripts without <?php ?>, doesn't make handling > > > the reports any easier..etc.,etc.. > > > > Well, we have introduced highlighting to user notes and manual examples > > I remember a statement "Customer is King". Jani is prolly the only real > user of this system so from my pov he has any reason to complain here. > For your information it also looked unreadable for me and I would have > reverted it myself if Jani didn't do it. Well I know that Jani is the number one user of the bug system, and I respect the work he does. I do beleive though that going further would be a better idea than going backwards, since the user note and manual example coloring showed that *it is possible* to present the text as it was presented before if there are no PHP tags inside. This change would have only needed a little correction to display the bugs as before if there are no PHP tags in them. As far as I have seen, if you have reloaded the cached CSS properly, only a few pixel margin was missing above and below the bug comments, but otherwise it was displayed like it was presented before the change... Goba

« previous php.mirrors (#22574) next »