Details
Bug
Major
Description
Safari seems to have a problem with client initiated interactions when there is more than one portlet on a page. I could successfully use a single portlet (sync or async) in both Liferay and JBoss. After adding a second portlet to the page, I could no longer interact with either portlet. If it was an async portlet, the clocks would continue to tick (server-push was still working) but any client interaction would fail. Safari's JavaScript console did seem to indicate that there was problem with the bridge (undefined Line 0 and Null value at line 1932).
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Deryk Sinotte [ deryk.sinotte ] |
| Fix Version/s | 1.7DR#3 [ 10112 ] | |
| Assignee | Deryk Sinotte [ deryk.sinotte ] | Mircea Toma [ mircea.toma ] |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 1.7 [ 10080 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Assignee | Mircea Toma [ mircea.toma ] |
The bridge and communication with the framework have undergone a number of changes since this was reported. I'm not sure of the exact issue but it appears that Safari does now support client UI interaction when more than one portlet is on the page. Resolving as fixed.