Closed
Bug 492946
Opened 16 years ago
Closed 16 years ago
Buglists have the "Please stand by ..." text at the top of them
Categories
(Bugzilla :: Query/Bug List, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.4
People
(Reporter: mozillaBugzilla, Unassigned)
References
()
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_7; en-au) AppleWebKit/525.28.3 (KHTML, like Gecko) Version/3.2.3 Safari/525.28.3
Build Identifier: Bugzilla 3.4 branch
In safari 3.2.3 (Mac), the buglists have the "please stand by" text, ahead of the bug list.
Google Chrome (Unknown build) seems to display some HTML code and doesn't display the bug list at all, I'm nto sure if it's the same bug.
This happens both on my local copy of 3.4 branch and on landfill (3.4 branch, and tip)
Reproducible: Always
Steps to Reproduce:
Run a search
Reporter | ||
Comment 1•16 years ago
|
||
this seemed to be fine on the windows version of Safari
Reporter | ||
Comment 2•16 years ago
|
||
I have just installed chrome 1.0.154.65 for Windows, and received teh same HTML problem
Reporter | ||
Updated•16 years ago
|
Flags: blocking3.4?
Updated•16 years ago
|
Version: unspecified → 3.3.4
Comment 3•16 years ago
|
||
I can reproduce this in Safari 3.2.3 on Mac OS X 10.5.7 on both the 3.4 branch and the trunk, but NOT on 3.2. IIRC we used to have code that did browser-sniffing, and refused to do the server-push trick if the browser was WebKit. The way this is behaving makes me think that code got lost somewhere along the line (or got broken).
Updated•16 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking3.4? → blocking3.4+
Keywords: qawanted
Target Milestone: --- → Bugzilla 3.4
Comment 4•16 years ago
|
||
Fixed by the backout of bug 441496.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 5•16 years ago
|
||
(In reply to comment #3)
> I can reproduce this in Safari 3.2.3 on Mac OS X 10.5.7 on both the 3.4 branch
> and the trunk, but NOT on 3.2. IIRC we used to have code that did
> browser-sniffing, and refused to do the server-push trick if the browser was
> WebKit. The way this is behaving makes me think that code got lost somewhere
> along the line (or got broken).
Just so you know, I was running Safari 4 for a while, and it was working on Safari 4
You need to log in
before you can comment on or make changes to this bug.
Description
•