Skip to main content

Default keyboard for Display Form element

Comments

2 comments

  • Gareth Evans

    Hey Marion Bishop good to hear from you! You're not missing anything here - I took a brief look at this and reproduced the behaviour you're describing. Though, I think this is actually a symptom of a larger issue with the Number Form Element in general. I noted it seems to behave like a text box.

    I noted in docs, and in the 3.x API sandbox, we get the expected behaviour of a ticker for your number form element that does use the appropriate keyboard:


    Here's a peek at the form's resultant HTML code in browser, in here we can see it's defined as a text box:

    If we manually change this to "number" we get the expected behaviour:

    This isn't a workaround as we're only changing this in the client-side context of the browser, so this isn't something you could do to force workflow/web to behave as expected. The only way I could see getting the expected behaviour today would be a custom component, which I'd say is outside the scope of what you're trying to do here with relative minimal effort.

    I filed this as bug item 257079 - "Workflow Number Form Element behaves like a text box" for visibility to our product team. Though, I'd still encourage you to take this issue to our VertiGIS Studio Support team as having your name (in particular!) on the item stakeholders adds weight.

    1
  • Ken Lyon

    This is likely a symptom of our decision to base numeric inputs on a text box rather than the HTML input of type number. That's the short answer. There were reasons for the change, that have been discussed elsewhere.

    1

Please sign in to leave a comment.