Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369533 - Wrong progress of WebKit Browser is reported to ProgressListener on Mac OS X
Summary: Wrong progress of WebKit Browser is reported to ProgressListener on Mac OS X
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.7.1   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-24 10:19 EST by Yahor Radtsevich CLA
Modified: 2019-11-14 03:54 EST (History)
3 users (show)

See Also:

Attachments
WebKitProgressTest.java (2.76 KB, application/octet-stream)
2012-01-24 10:19 EST, Yahor Radtsevich CLA 		no flags Details
View All 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 Yahor Radtsevich CLA 2012-01-24 10:19:55 EST 
Created attachment 209973 [details]
WebKitProgressTest.java

The progress of loading of some sites is never completed on Mac OS X with WebKit. You can easily see this if you open http://www.google.com in the Eclipse Internal Web Browser - the right upper icon which shows the progress never stops changing.

STEPS TO REPRODUCE:
1. Run attached JUnit4: WebKitProgressTest.java .

The test opens a new shell with WebKit browser and loads http://www.google.com . After 20s it checks the progress. If the progress is not 100% and not 0%, than it throws an AssertionError. 

The test passes on Windows, but fails on Mac OS X.
Comment 1 Lars Vogel CLA 2019-11-14 03:54:15 EST 
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.