| Summary: | Browser bars occasionally lead to multiple instance warning | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Stefan Röck <stefan.roeck> | ||||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | ||||||||
| Version: | 1.3 | ||||||||
| Target Milestone: | 1.4 M1 | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | sr131 | ||||||||
| Attachments: |
|
||||||||
|
Description
Stefan Röck
Created attachment 170640 [details]
Sample html page
This simplified login form redirects to the rap demo application.
In case of error, the following three requests are send: Request 1: w1.bounds.width:1280 w1.bounds.height:955 w1.scrollbar.size:17 w1.dpi.x:96 w1.dpi.y:96 w1.colorDepth:32 w1.cursorLocation.x:358 w1.cursorLocation.y:20 uiRoot:w1 Request 2: w1.bounds.width:1280 w1.bounds.height:927 w1.cursorLocation.x:358 w1.cursorLocation.y:-8 uiRoot:w1 Request 3: w1.bounds.width:1280 w1.bounds.height:925 w2.mode:maximized w1.cursorLocation.x:358 w1.cursorLocation.y:-8 uiRoot:w1 requestCounter:0 If everything is OK, the last request is *not* send. I wonder why the 2 request succeeds as the requestCounter is missing there... Created attachment 170643 [details]
Patch proposal
This patch works for me, however, I'm not sure if this is a good solution as there still some RAP internals I haven't fully understood yet :-)
Hi Stefan, I had the same issue before with FF and Firebug, but I can't reproduce it anymore. I can't reproduce the issue with your attached file too and CVS HEAD. Tested on FF 3.6.6, Chrome 6 and IE8 - about 20-30 times each. Nevertheless, your patch looks good for me - I had exactly the same patch prepared, when I had this issue but I've never committed it. What are the browser versions used by you? Hi Ivan, I could reproduce this with Google Chrome. In contrast to Firefox, Chrome displays the "remember password"-bar slightly delayed which seems to cause the trouble. I could reproduce it wiht Chrome and Firefox. The patch looks good, I would only replace the access to the internal field with a function call. Fixed in CVS HEAD. Backported fix to v13_maintance. |