Quick Tool Number (weirdness)

  • Profile Image
    Asked on June 13, 2011 at 06:08 PM

    I am using a form populated with a bunch of the "Number" fields found under the quick tools palette.

    When using the up and down arrows to increment the number it shows -1.79xxxxxx

    I have the fields set to validate numerically so this value is throwing an error of course.

    I've also tried popping a new "number" field into a totally blank form with the same results. Is this whole field just bugged?



    I am thinking of replacing the use of number fields with "spinner" fields. This would be extremely labor intensive though.

    Any thoughts on salvaging this approach would be appreciated :)

  • Profile Image
    Answered on June 13, 2011 at 06:30 PM
  • Profile Image
    Answered on June 13, 2011 at 07:50 PM

    *waits patiently while others get responses*

  • Profile Image
    Answered on June 13, 2011 at 09:28 PM

    Hi gciad

    Thanks for your patience. Could you supply a bit more info, please? So far, I have looked at a couple of your forms and have not experienced the same "-1.79" issue. I know you've stated that even if a number field is inserted into a totally blank form, the same thing happens but I would still like a specific form to investigate. Just provide its name and I'll test it.

    Also, are you viewing the form with any browser in particular or is this happening regardless of which one is used? From your screenshot, it looks like Safari but I cannot be sure. Each browser seems to display such fields quite differently.


    ~ Wayne

  • Profile Image
    Answered on June 14, 2011 at 12:31 PM

    Hi Wayne, thanks for your response.

    It does indeed appear to be a Safari issue (OS 10.6 - Safari 5.0.5).

    Within my account the form in question is "L and E Bottling - Product Order Form".

    Besides the number increments there are some other display issues with the html free-form text fields collapsing to the top.

    After testing across a few browsers I am noticing that the fields work correctly in Firefox 4.0.1. In Chrome 12 and IE8 the up and down arrows drop-off the fields. Safari is the only one which spits that 1.79 figure into the field.

    The end-result is that I'd like to be able to increment each field by 1, across browsers. There's already been a few hours of work put into this form, so I'd like a way to proceed which doesn't involve rebuilding using spinners if possible.

  • Profile Image
    Answered on June 14, 2011 at 05:10 PM

    Really not trying to be a pain in the butt. I can see you guys are busy :)

    If I'm out of luck on the number fields bug (or whatever it is) please let me know so I can get back to the project.

    I love jotform a lot! But please don't forget that we've got clients and deadlines to attend to. If it's going to fail, it's better to fail quickly.

  • Profile Image
    Answered on June 15, 2011 at 04:05 PM

    Going to proceed with rebuilding from scratch... Dissapointed with your support on this issue.

  • Profile Image
    Answered on June 15, 2011 at 06:51 PM


    Apologies if we're not able to attend to you in the quickest time possible. Personally, on my end, I am not seeing any of the problems that you were describing except the issue about IE 8 not showing the up and down buttons.

    Just so you know, the number field is an HTML 5 element. HTML 5 is fairly new and is not yet fully supported by a lot of browsers, IE included. In fact, on my end, I can't even see the up and down arrows using Firefox 4 and Safari 5.0.5.

    If I am not able to replicate your situation, I don't know how else I can help solve this 'problem'. I guess I'll just have to advise that you use spinner fields which do work in any JavaScript-enabled browser.

    Again, I apologize for the delay and I hope the advice I gave sounds good enough for you.


  • Profile Image
    Answered on June 15, 2011 at 07:05 PM

    Hi Neil, thanks for the response. As I mentioned above I was not looking for a miracle fix, more a confirmation that this was failing, and to move on (thanks for affirming the use of spinners being a good direction).

    It's especially frustrating seeing lots of lengthy responses flying around on fluffy issues like "which template looks best" when a -real- (albeit obscure) technical issue goes ignored.

    Of course, the advice you gave is plenty good enough for me.

    Thanks much.