Bug 112939 - [browser] indicate if a page load failed
Summary: [browser] indicate if a page load failed
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 224385 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-10-18 10:28 EDT by Grant Gayed CLA
Modified: 2019-09-06 16:12 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Grant Gayed CLA 2005-10-18 10:28:57 EDT 
There should be a way for a client to determine if a page load failed (eg.- a 
URL didn't resolve).  This is similar but slightly different to the type of 
error that is the intent of bug 98302.  These _may_ ultimately be combined (?).

The best way to indicate this is probably with a detail on the document 
completed callback, as long as this fires early enough for the client to (for 
example) set the browser's content manually before the default "could not find 
page" page is shown.  I'm not sure of the current support for this in the 
various native browsers.
Comment 1 Eric Zimmerman CLA 2005-11-14 15:24:44 EST 
Just to add a note here.  I originally posted this question in the newsgroup in
an attempt to resolve issues we were having with disconnected users.  We would
like to store web pages on a remote server for updating but if the user is not
able to connect to that page use a locally stored copy or display a message for
them to connect to a network.
Comment 2 Grant Gayed CLA 2008-04-25 12:33:46 EDT 
*** Bug 224385 has been marked as a duplicate of this bug. ***
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:12:07 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.