Be sure your post includes:
Reproducible in version v9.0p_2013-08-01/Enterprise Deployment (built 2013-08-01) as well as the SmartClient/SmartGWT showcase portal example (http://www.smartclient.com/#portalFS)
Its been tested in chrome and firefox
When maximizing and minimizing a portlet in a portal layout the width will automatically increase and force a second portal to shrink. This was first reported in our app by one of our testers using SmartGWT. It was then found to be reproducible in the Smartclient showcase. I've included steps and screenshots.
1) Remove right column
2) Drag business analytics into the column
3) Drag sales forecasting into the same column so that they are side by side, as shown in image 1.
4) Maximized business analytics portlet (button #2)
5) Minimize business analytics portlet (button #1)
6) Restore business analytics portlet (button #1)
Notice that after restore the business analytics portlet became much wider and the sales forecasting much thinner, to the point that it is not useable as shown in image 2.
Reproducible in version v9.0p_2013-08-01/Enterprise Deployment (built 2013-08-01) as well as the SmartClient/SmartGWT showcase portal example (http://www.smartclient.com/#portalFS)
Its been tested in chrome and firefox
When maximizing and minimizing a portlet in a portal layout the width will automatically increase and force a second portal to shrink. This was first reported in our app by one of our testers using SmartGWT. It was then found to be reproducible in the Smartclient showcase. I've included steps and screenshots.
1) Remove right column
2) Drag business analytics into the column
3) Drag sales forecasting into the same column so that they are side by side, as shown in image 1.
4) Maximized business analytics portlet (button #2)
5) Minimize business analytics portlet (button #1)
6) Restore business analytics portlet (button #1)
Notice that after restore the business analytics portlet became much wider and the sales forecasting much thinner, to the point that it is not useable as shown in image 2.
Comment