Closed
Bug 1633
Opened 26 years ago
Closed 25 years ago
need error handling for bogus URLs
Categories
(SeaMonkey :: General, defect, P3)
SeaMonkey
General
Tracking
(Not tracked)
VERIFIED
WORKSFORME
M14
People
(Reporter: sujay, Assigned: travis)
References
()
Details
using 11/24 build jump to an illegal URL like above.
nothing happens in NGLayout, we need to spit out a message
like the old 4.x browser:
"Netscape is unable to locate the server:
www.netscape
The server does not have a DNS entry.
Check the server name in the Location(URL) and
try again."
On start binding (in the parser at least) never gets called.
It's probably in your domain or netlib.
Re-assigned to gagan@netscape.com.
Gagan, is this a netlib bug? Who should get this?
Comment 4•26 years ago
|
||
setting paulmac as QA contact for all gagan's bugs (sorry for the spam)
Per DP's suggestion marking these till M8. Though Necko lands with M7, we will
be able to verify it for M8.
Comment 7•26 years ago
|
||
I'm moving this to target M9, Necko will be enabled somewhere during late M8 or
early M9. We will need to get on this and it cannot be postponed past the M9
milestone.
The error is now being pushed out to OnStopRequest (in Necko) the consumers now
need to hook in the response. In general we need to set up an error display
mechanism which reads off from standard lists of Netlib errors. Assigning to
component owner to work this out. (How are other errors being handled now?)
We don't care whether this shows up in viewer per se. It just needs to be dealt
within AppRunner. Scott -- Since you're now the webshell API owner, I think you
should own this issue. The error needs to get propagated to the APP, where a
dialog can be flown. The parser is already sending error codes out to the caller
when things like this occur, so it should be easily trapped at the docloader
level. Call me if you need additional help.
Updated•26 years ago
|
Status: NEW → ASSIGNED
Updated•26 years ago
|
Priority: P2 → P3
Target Milestone: M9 → M10
Comment 10•25 years ago
|
||
Moving to M11 per today's bug triage.
Updated•25 years ago
|
Assignee: scc → travis
Status: ASSIGNED → NEW
Comment 11•25 years ago
|
||
According to rickg, this bug goes along with the webshell. Sorry travis.
Updated•25 years ago
|
Component: Viewer App → Browser-General
OS: Windows 95 → All
QA Contact: paulmac → tever
Hardware: PC → All
Comment 12•25 years ago
|
||
*** Bug 11362 has been marked as a duplicate of this bug. ***
Comment 13•25 years ago
|
||
m12
Updated•25 years ago
|
Summary: need error handling → need error handling for bogus URLs
Comment 14•25 years ago
|
||
Move to M13 and re-assess once basic Webshell re-design is complete.
Comment 15•25 years ago
|
||
Move to M14. Is this required for beta 1?
Comment 16•25 years ago
|
||
appears to be fixed with a decent dialog in 2000020310 on NT.
Marking fixed. Please verify.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 17•25 years ago
|
||
yes, the error handling is in except on linux I get a blank dialog.
NT is fine but haven't checked Mac. Re-opening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 18•25 years ago
|
||
Please re-verify.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•