Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

  • Spinner Item Customization and clicking increase/decrease in IE11 increments/decrements by 2

    1. The *complete* SmartGWT or SmartClient version from the lower left-hand corner of the Developer Console (see FAQ for how to open Developer Console), for example, "v10.0p_2015-06-18/PowerEdition Deployment"

    v9.1p_2016-04-15/Pro Development Only (built 2016-04-15)


    2. Browser(s) and version(s) involved
    IE11

    3. Description -

    In our codebase we have overwritten
    Code:
    decreaseIconDefaults
    and
    Code:
    increaseIconDefaults
    to make the increase and decrease icon appear something like shown below

    Click image for larger version

Name:	Screen Shot 2017-10-06 at 12.43.38 PM.png
Views:	1
Size:	4.3 KB
ID:	249528












    The following video demonstrates what is going on in IE -



    In development environment the issue can be fixed by overriding the mouseDown function as follows -

    Code:
    mouseDown : function (form, item, event) {
        if (this.isDisabled() || this.isReadOnly()) return;
        // force focus into the item on mouseDown - required to ensure we save out change made via
        // icon click
        if (!this.hasFocus) this.focusInItem();
        this._mouseStillDownCounter = 0;
        if (!isc.Browser.isIE) {
            isc.Page.setEvent(isc.EH.MOUSE_UP, this, isc.Page.FIRE_ONCE, "_clearLastTargetIcon");
        }
    }
    But running this code in production environment fails potentially because of the minified code. I was wondering if there is a different approach that i can try, Thanks

  • #2
    Please check if you have the issue with the fully patched version.

    This should always be done before posting.

    Comment


    • #3
      Hi,

      Thanks for the reply. If you don't mind me asking - is this a known issue which is fixed in the latest patch?

      Thanks

      Comment


      • #4
        You are about a year and a half behind on fixes - several fixes have gone in that might have addressed this.

        Comment


        • #5
          the issue still persists

          Comment


          • #6
            OK, what we now need (as always - and for any issue for any product) is a way to reproduce the issue: ideally a minimal, ready-to-run test case.

            This will reveal whether the issue is in your code or a framework issue.

            Comment

            Working...
            X