Uploaded image for project: 'ZK'
  1. ZK
  2. ZK-3716

Different format used for OUT_OF_RANGE message

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 7.0.8
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      There is a difference in popup error message produced by spinner component.
      If and error is generated server side on (i.e. exceeding min/max constanint on spinner here org.zkoss.zul.SimpleSpinnerConstraint#outOfRangeValue)
      then

      OUT_OF_RANGE min ~ max

      message is produced.
      If the message is generated on client side (i.e. exceeding integer range, Spinner.src.js#coerceFromString_)

      OUT_OF_RANGE min - max

      message produces (notice the difference ov using - vs ~ sign)

        Activity

        Hide
        sirvaulterscoff sirvaulterscoff added a comment -

        Also noticed the absence of dot in js-generated version of error message.
        Thus server side actualy is

        OUT_OF_RANGE min ~ max.
        

        while js-version lacks the trailing dot sign

        Show
        sirvaulterscoff sirvaulterscoff added a comment - Also noticed the absence of dot in js-generated version of error message. Thus server side actualy is OUT_OF_RANGE min ~ max. while js-version lacks the trailing dot sign

          People

          • Assignee:
            Unassigned
            Reporter:
            sirvaulterscoff sirvaulterscoff
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: