Details
Bug
Major
Description
Seam examples contain a number of anchor tags and location.href='xxxx' snippets
to be generated from the Seam custom link tag <s:link>. All of these navigation
links generate a GET request when retrieving the resource specified. ALL of
these navigation links popup the Network Connection Interrupted dialog until the
response is rendered, which makes Seam examples play out poorly. Note that all
<h:commandLink> and seam link tags that cause partial submits work normally.
We can't rewrite these s:link tags because they have custom attributes that the
ICEfaces commandLink doesn't support.
to be generated from the Seam custom link tag <s:link>. All of these navigation
links generate a GET request when retrieving the resource specified. ALL of
these navigation links popup the Network Connection Interrupted dialog until the
response is rendered, which makes Seam examples play out poorly. Note that all
<h:commandLink> and seam link tags that cause partial submits work normally.
We can't rewrite these s:link tags because they have custom attributes that the
ICEfaces commandLink doesn't support.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Fixed in commit #12135.
Show
Mircea Toma
added a comment - Fixed in commit #12135.
Using the EPS bridge might help here as there is a delay period while the heart-beat mechanism tries to recover the connection. This may prevent the dialog from displaying before the new page is loaded. Suggest we retest once the EPS bridge is committed to the 1.6 trunk.
Show
Ken Fyten
added a comment - Using the EPS bridge might help here as there is a delay period while the heart-beat mechanism tries to recover the connection. This may prevent the dialog from displaying before the new page is loaded. Suggest we retest once the EPS bridge is committed to the 1.6 trunk.
Could we add a delay before showing the "connection lost" or would that cause it to appear on the next
page anyway?