Bug 205750 - [Browser] Web browser hangs Eclipse if you follow the file:// hyperlink with an invalid target
Summary: [Browser] Web browser hangs Eclipse if you follow the file:// hyperlink with ...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-08 13:19 EDT by Sasha CLA
Modified: 2019-09-06 15:35 EDT (History)
4 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 Sasha CLA 2007-10-08 13:19:44 EDT 
Build ID: I20070625-1500

Steps To Reproduce:
1. Create the file like this one
<html>
<body>
<a href="file://__">aaa</a>
</body>
</html>

(The link "file://__" should be invalid at your machine)

2. Open the file with a built-in Eclipse web browser

3. Follow the "aaa" link

4. Eclipse hangs up


More information:
Maybe the bug appears only in Windows, I didn't test it on other platforms
Comment 1 Kevin McGuire CLA 2007-10-10 13:54:55 EDT 
Works for me on Vista, 3.3M2.
It does take a few seconds to fail though.
Comment 2 Kevin McGuire CLA 2007-10-10 14:00:21 EDT 
This works for me on WinXP too (3.3 M2).
Moving to SWT for comment since I believe there's some Mozilla hook we do but I don't know the specifics.
Comment 3 Grant Gayed CLA 2008-02-14 16:15:53 EST 
I cannot reproduce this on win2000 (IE6) or Vista (IE7).  I've also tried with an SWT.MOZILLA-style Browser, even though eclipse's browser view never uses this on windows.  Is there anything unusual about your XP or IE that could be causing this different behaviour?
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:35:39 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.