Closed
Bug 57867
Opened 24 years ago
Closed 22 years ago
Only show timeout error dialog for main document, not objects
Categories
(Core :: DOM: Navigation, enhancement, P3)
Core
DOM: Navigation
Tracking
()
Future
People
(Reporter: aheitner, Unassigned)
References
()
Details
(Keywords: arch)
From Bugzilla Helper: User-Agent: Mozilla/4.73 [en] (X11; I; Linux 2.2.16 i686) BuildID: 2000101805 On a page like the Washington Post front page, if doubleclick is having a bad day, you may get the popup (and be forced to hit "ok") quite a few times as JS tries again and again to load an ad for you. The popup is fine for pages explicitly entered by the user, but shouldn't happen on other pages. The message should probably show up in the statusbar (without interrupting the user). Reproducible any time doubleclick is busy :) Reproducible: Always Steps to Reproduce: 1. go to washingtonpost.com 2. usually you have to choose an article to read 3. watch in helpless pleasure as the script tries and fails to load an ad, time afer time after time Actual Results: The end user got annoyed by the extraneous popups warning me about pages i don't care about Expected Results: i should have been quietly notified about the failures.
Comment 1•24 years ago
|
||
Confirming. This could be considered a duplicate of bug 28586, depending on how quickly bug 28586 gets fixed.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Summary: "transaction has timed out when attempting to connect to foo.com" should only pop up for failures to connect to the site specified in the navigation bar → Only show timeout error dialog for main document, not objects
Sending this design feedback bug to Networking
Assignee: hangas → gagan
Component: User Interface: Design Feedback → Networking
QA Contact: mpt → tever
We have other bugs on this site so I have used it on various occassions, but not seen this problem (we either share our contributors with their viewers or this site has a lot of problems...) At any rate, since this problem is somewhat well understood but not easy to reproduce, I would like to mark it a duplicate, based on mpt's previous comments.
Reporter | ||
Comment 7•23 years ago
|
||
I'll buy mpt's dup, as long as 28586 gets fixed in a reasonable way for this. i.e. I don't want a whole page killed and replaced by a bloody IE-style "HTTP 404" page if only one element on the page fails to respond. The correct behaviour is "show the working parts of a page, and show the error in a sidebar, if it's open" or something like that. If a frame dies, the error can be shown in-frame; that way if a single-frame page dies you get the IE behaviour (seems reasonable to me). It's hard to reproduce because the DoubleClick guys have a lot invested in keeping their stuff working :) It's also possible in the like 9 months since I filed this that their stuff works quite a bit better than it used to...
Comment 8•22 years ago
|
||
moving neeti's futured bugs for triaging.
Assignee: neeti → new-network-bugs
Comment 9•22 years ago
|
||
marking as dupe *** This bug has been marked as a duplicate of 28586 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Comment 10•22 years ago
|
||
VERIFIED: there is also a supress secondary URL get errors bug, but this is close enough.
Status: RESOLVED → VERIFIED
Component: Networking → Embedding: Docshell
You need to log in
before you can comment on or make changes to this bug.
Description
•