inputNumber components migration

    Overview

    This document will describe the migration of inputNumberSlider and inputNumberSpinner components.

    information from 3.3.x:

     

    references:

    http://docs.jboss.org/richfaces/latest_3_3_X/en/devguide/html/rich_inputNumberSlider.html

    http://docs.jboss.org/richfaces/latest_3_3_X/en/devguide/html/rich_inputNumberSpinner.html

     

    tld:

    http://docs.jboss.org/richfaces/latest_3_3_X/en/tlddoc/rich/inputNumberSlider.html

    http://docs.jboss.org/richfaces/latest_3_3_X/en/tlddoc/rich/inputNumberSpinner.html

     

    svn

     

     

    Related requests and jiras

    http://tinyurl.com/358exee

     

    InputNumberSlider component

    There are almost no functional changes in the component comparing to 3.3.3 implementation. That caused by the fact that component is pretty simple and we decided not requires functional redesign. So there I will list all the changes were made from 3.3.x which should be considered during QE and documenting.

     

    Layouts

    there should be two option to define layout - vertical and horizontal.

    Vertical - not implemented in M2

    Focusable parts

    opposite to 3.3 where only input get focus - in 4.x both slider and input could be focused.

     

    We should wait for the feedback on the feature as there are some guys who could preffer navigate more quickly between page inputs and so could request to make it configurable. but that could be easilly added after the first release.

    Focused parts and keyboard

    if input focused - no additional keyboard handling should occur.

     

    if track focused:

    up and right keys should increase the value according to step attribute for horizontal layout.

    down and left keys should decrease the value according to step attribute for vertical layout.

     

    client side built-in validation

    slider should not allow to enter not valid characters to input(letters, other characters except decimal separator). Entered letter should be just not added to input.

     

    JS API

    there should be next api functions available:

    • setValue(newValue)
    • getValue()
    • increase()
    • decrease()
    Attributes names changes

    TBD

     

     

    InputNumberSpinner component

    As for slider - there are almost no functional changes in the component comparing to 3.3.3 implementation.

    So there I will list all the changes were made from 3.3.x which should be considered during QE and documenting.

     

    Keyboard handling

    Arrow buttons - should not be focusable by tab key

    When focus set to input - up and down keys should increase/decrease value to step attribute.

     

    client side built-in validation

    slider should not allow to enter not valid characters to input(letters, other characters except decimal separator). Entered letter should be just not added to input.

     

    JS API

    the same as for slider