| Summary: | [Browser] Progress event not fired on hidden browser widget | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Tim Buschtoens <tbuschto> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P2 | CC: | tbuschto |
| Version: | 1.5 | ||
| Target Milestone: | 1.5 M7 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Tim Buschtoens
I'm setting this to P2 because it can break many browser-widget based custom-widgets (like the CKEditor). If the widget is created on an invisible composite, like in an hidden tab of a tabfolder, it will load the content, but the server is not informed. (The BrowserFunctions may also not be created, i have not tested this yet). Since we encourage developers to use the Browser widget to create custom widgets, this should be fixed in 1.5. Checked in SWT and the progress event is fired on invisible or disabled Browser widget. Even on invisible parent or inactive Shell the event is fired too. That's why I fixed it by changing ProgressEvent#allowProcessing to always returns true instead of EventUtil#isAccessible(). |