| Summary: | BrowserHistoryListener not working | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Stefan Milchram <stefan.milchram> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | ||
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
In upcoming RAP 2.0M3 (nightly) everything is working fine. The "historyNavigated" was renamed to "Navigation" with commit d1dc77375b7f88bad63205624834cd5fbb4c0d5b. Both Display.js and History.js are using "rwt.client.BrowserHistory" as id. |
The BrowserHistoryListener is not working because in BrowserHistoryImpl.processNavigationEvent() ProtocolUtil.wasEventSent(..) is called with TYPE = "rwt.client.BrowserHistory" but in the clientmessage its called "bh". Excerpt from clientmessage: [ "notify", "bh", "historyNavigated", {"entryId": "abc"} ], You can easily reproduce with the rap examples in the git-repository.