Bugzilla – Full Text Bug Listing
| Summary: | [BrowserNavigation] URL fragment not decoded properly on page reload | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Gunnar Wagenknecht <gunnar> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.0 | ||
| Target Milestone: | 2.1 M2 | ||
| Hardware: | PC | ||
| OS: | Windows 8 | ||
| Whiteboard: | |||
Using back and forward buttons in Chrome do not show the problem. Only refresh (F5) does. Fixed in master with commit dbffab4689af68be24bfafbddb0535a38f9372aa. (In reply to comment #0) > BTW, is it intentional that #pushState does not trigger any attached BrowserNavigationListener? #pushState only store the state... and this is not a navigation operation, but a store operation. |
Steps to repeat: 1. generate a browser history entry from Java with a special character (eg. slash '/') via BrowserNavigation#pushState("/", "Blah") --> it appears encoded in the browser URL bar (%2F) 2. press refresh (F5) --> history listener does not get decoded but encoded value (BrowserNavigationEvent#getState() returns "%2F" instead of "/") This happens for me on Windows 8 using the latest Chrome. BTW, is it intentional that #pushState does not trigger any attached BrowserNavigationListener?