Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 4.1.1
-
Fix Version/s: 4.2
-
Component/s: ACE-Components
-
Labels:None
-
Environment:supported browsers
-
Assignee Priority:P2
Description
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Modified Resizable.Setup to render the setup script as child of the target component only if it already has children.
I was testing with ICEfaces4 trunk r50153, and indeed, the ace:resizable with MandatoryResourceConfig passes.
However, all the other tests for GraphicImage don't render the handle. As example:
/resizableOnly.jsf
/graphicImage/resizableDynAttribute.jsf
On other tests, the handle becomes visible after a form submit, as example:
- after adding a row on /graphicImage/resizableTableTop.jsf
- after switching tabs on /graphicImage/resizableSparkleTabset.jsf
This is only an issue for the tests with the graphicImage and not for the resizable ACE container components.
I don't see that. The resize handle is there and when clicking 'Submit' button the width and height of the image is shown. I believe that is the expected behavior?! Are you sure that you are running with the latest code?
ICEfaces4 trunk r50153 /IE11, MsEdge, Chrome55, FF49: the ajax tests have been fixed, however the ace:resizable with MandatoryResourceConfig still fails.
All resizable graphicImage tests are missing the handle and the graphic images cannot be resized. This is an issue on all browsers.
This was not an issue with ICEfaces 4.2.BETA libraries.
To avoid polluting the component's tag with the resizable related attributes we could have them defined on a facet or client behaviour tag, declared within the component's tag. For example:
<ace:panel header="Header ..." closable="true" toggleable="true" collapsed="#{panelBean.collapsed}"> <ace:resizable animate="true" ghost="false" containment="true"/> ..... panel content ..... </ace:panel>
Implementation wise the resizable feature can be implemented server side as a ClientBehaviour just like the ace:ajax behaviour while the client side will need to invoke the jQuery resizable functionality in the component initialization.
Hopefully the issue is resolved now.