Uncaught DOMException

Jostein Svegården

October 31, 2018 13:17

A form's number element is populated with an integer from a query. When I set the precision of the number element, the console reports this error: "Uncaught DOMException: Failed to execute 'setSelectionRange' on 'HTMLInputElement': The input element's type ('range') does not support selection".

 

The workflow works as if nothing was wrong, so why do I get this error? I use the console for debugging, so I want to get rid of these disturbing error messages

0

• 

  Permanently deleted user

  November 02, 2018 17:54

  Jostein,

   

  I got this to work just fine without any DOM errors, but did notice that to get it to work as you might intend you can't just add the "precision" property to that element. You need to pass an object to the "format" property in the schema of {precision: n}. Make sure that you include the step property too, if you need it (which I think you will).

   

  If this doesn't help you, perhaps look at the developer console in the sandbox for clues.

  0
• 

  Jostein Svegården

  November 08, 2018 16:22

  I have set all these properties. The error message comes with the precision parameter.

   

  What about you, @Stefan Schweigert? or @Ryan Cooney? , do you have a clue?

  0
• 

  Ryan Cooney

  November 08, 2018 17:19

  Hi Jostein,

   

  This happens because when GVH activates a view (like a workflow form) it attempts to apply focus to the first element. The Number Slider form element is implemented using a "range" input type and the way focus is applied isn't correct for the range type.

   

  I've filed this as issue 25181.

   

  This issue doesn't have any negative consequences other than the console error message, so you can safely disregard it for now.

   

  --Ryan

  0

Please sign in to leave a comment.