Closed
Bug 302743
Opened 19 years ago
Closed 9 years ago
Sometimes loads time out (?) with no feedback
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bzbarsky, Unassigned)
Details
(Keywords: regression)
STEPS TO REPRODUCE: 1) Load https://bugzilla.mozilla.org/show_bug.cgi?id=78510 2) Make a change (cc list change, comment change, whatever) 3) Submit. EXPECTED RESULTS: Throbber spins a bit, then shows bug submitted page. ACTUAL RESULTS: Throbber spins a bit, then stops. We're still showing the bug page. I'm assuming we time out or something, but we're not reporting it, if so. I'm pretty sure this is a regression; I don't recall this happening until recently. Unfortunately, I've not been able to reproduce outside of bugzilla thus far (testing with a script that just took several minutes to respond, the throbber kept spinning as it should have). So I don't have a regression range, though I could try to get one by messing with the CC field on that bug if we decide we want one badly enough. My first possible guess is that this fallout from error pages being on by default. At least as far as not reporting the timeout? That wouldn't cause the timeout, of course... Not really sure what else has changed in docshell recently other than fastback, and this doesn't seem too likely to be fastback-related.
| Reporter | ||
Comment 2•19 years ago
|
||
Actually, I take it back. CC list changes don't mail enough people to really test with... I'm really not happy making comments just for the heck of it on that bug, so I'll have to wait to test it (or find some other way to reproduce this...).
afaik this is a server side problem relating to apache and template toolkit. i'm not sure if this ever generate Document Contains No Data in older browsers, because i think we bleed just enough so that it wouldn't, not sure...
Updated•19 years ago
|
Assignee: darin → nobody
QA Contact: benc → networking
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•