#34585 [Bgs]: php.net causes Firefox to freeze
| From: | goba@php.net | Date: | Thu, 22 Sep 2005 22:02:25 +0000 |
| Subject: | #34585 [Bgs]: php.net causes Firefox to freeze | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-29442@lists.php.net to get a copy of this message | ||
ID: 34585
Updated by: goba@php.net
Reported By: php at transpect dot com
Status: Bogus
Bug Type: Website problem
Operating System: Gentoo Linux
PHP Version: Irrelevant
New Comment:
I don't see how lowering of standards come into the picture. Quite a
few people checked their browsers, and Jacques even reported to the
mirror list that it also works in 1.5. Now what else can we do? How can
we raise our standards here? What respect do you miss? The only
possiblity is to go and check your computer, which you really should
not expect us to do.
Ps. of course I can scroll after the page loaded, there is no freeze.
Anything can cause this behaviour in your whatever
hardware/Gentoo/KDE/Firefox setup, and anything can be buggy of course
as with any other software.
Previous Comments:
------------------------------------------------------------------------
[2005-09-22 23:44:20] nlopess@php.net
I also have Konqueror, Firefox and Opera and all work fine.
This is not a PHP problem! So please report the bug to Mozilla.
------------------------------------------------------------------------
[2005-09-22 22:33:00] php at transpect dot com
Curious. The page fully loads for me too -- it's then that it freezes.
Could you scroll?
As for "buggy desktop stuff," I'm running a standard KDE installation.
There's nothing particularly weird or customized about this
workstation. Nor am I asking you to "help" me with it. If nobody else
sees this problem -- odd. My bet would be that others just aren't as
considerate in reporting bugs to you.
There's been a notable lowering of standards across much of the open
source movement in the last couple of years. I've been with it since
'93, and this isn't the only place I'm now seeing much less respect for
careful bug reports.
------------------------------------------------------------------------
[2005-09-22 18:21:27] goba@php.net
Once again, please understand: our site works with Firefox. Whatever
buggy desktop stuff you have we cannot help with. Just so that we are
using similar software, I also installed the noscript extension (on top
of the extensions I already have), and just as I anticipated, I
encoutered no problems. If this is hard to beleive, look here for a
screen grab:
http://xs.to/xs.php?f=Screenshot.png&h=xs47&d=05384
Notice that the page is fully loaded and that noscript is in effect.
------------------------------------------------------------------------
[2005-09-22 17:21:06] php at transpect dot com
With respect, it is generally accepted that it is the responsibility of
Website authors to maintain compatibility with at least the major
browsers. Mozilla Firefox is a major browser (particularly popular
among those coding PHP) and the noscript extension is also reasonably
common of late (one of the most-used, certainly). The bug, properly
analyzed, is probably in the interaction of the site and noscript --
but no other sites of the many I visit are having this problem. So it's
something you could avoid by recoding the php.net site.
If you don't want to adopt a professional attitude about your site
code, that's of course your business. But then, since PHP has become
more of a Zend corporate thing, and less of a Rasmus amateur thing,
professionalism about Web coding compatibility might be in order.
If it were one of my sites, I'd fix it. Sorry for the attitude, but as
a longtime PHP coder I'd like to see you guys continue to strive for
the highest standards.
------------------------------------------------------------------------
[2005-09-22 11:25:36] sniper@php.net
It's obviously some bug in the browser, not in the website..
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/34585
--
Edit this bug report at http://bugs.php.net/?id=34585&edit=1