[ https://jira.jboss.org/jira/browse/RF-5320?page=com.atlassian.jira.plugin... ] Tsikhon Kuprevich updated RF-5320: ---------------------------------- Attachment: slider-arrow.gif -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-5320?page=com.atlassian.jira.plugin.sy... ] Matt Kenney commented on RF-5320: --------------------------------- I have a workaround on this issue. When the component is rendered it positions the handle for your bound value based on an assumption about the width (or height if vertical orientation). The calculation for the position of the handle seems to be based on a constant, therfore the inputNumberSlider will only work correctly at a specific width. Set the width to exactly 305 pixels using the style attribute as follows: <rich:inputNumberSlider id="yourSlider" style="width: 305px" ... Setting the width using the width attribute will not have the same effect of correcting the handle position, but setting it with the style does the trick. The incorrect handle positioning problem occurs regardless of being wrapped in a rich:tabPanel structure. With this set the handle should be positioned correctly. This occurs in the 3.3.3.Final build. The handle will still be positioned out of range if the bound value is out of range, for example if your maxValue is 100 and the value is 120 the handle will be beyond the slider area. It is not possible to set a value out of range using the slider directly, but this could occur if the bound value is set elsewhere like in a class or javascript function. Matt -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira