[KULRICE-3815] Expanding pages when using standalone Rice Created: 08/Jan/10  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: 1.0.1, KFS Release 3.0
Fix Version/s: Backlog

Type: Bug Fix Priority: Major
Reporter: Jonathan Keller Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Similar issues:
KULRICE-4286Standalone rice hosted web screens return to the wrong url.
KULRICE-2732Rice configuration enhancements to support standalone use
KULRICE-10202Expand pager for use in a paged group
KULRICE-7064Setup KFS Locally for expanding Rice Sample App
KULRICE-7451Future Action Requests tab does not work when using standalone Rice server
KULRICE-4110Externalizable BO lookups and inquiries don't work with standalone Rice
KULRICE-1436Modify standalone rice to use Atomikos instead of JOTM
KULRICE-3625problem with handling of SecurityAttributes in standalone rice
KULRICE-4618Update createproject.groovy to have option to create project for use with standalone rice
KULRICE-2932rice-config.xml for deployment of standalone server
Rice Module:
KNS
Application Requirement:
KFS, Rice

 Description   

It looks like our infinitely expanding pages are back when you run with a standalone rice server on a different host. I had seen this before but got it again just before the break. It happens because of the cross-site-scripting limitations. The code which checks the external frame's size can't get the real number and the browser then returns zero. This causes the code to attempt to make the frame wider and so on...

It happens when using the portal screens from KFS and then accessing a Rice screen (like the KIM lookups or the parameter document)

I observed this in both Firefox and Safari.

It seems that we need some way to detect when we are receiving a zero because of a scripting block like this and shut down the resizing code.


Generated at Tue Jul 14 13:54:49 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.