Håkon Nordli
Nov 25, 2015
  6801
(0 votes)

Extend Dojo's onChange event by using intermediateChanges

One of JavaScripts built-in events are 'change'. It is triggered different depending on which input type you are using. For text input it is fired when the element looses focus after its value has changed. 

Not suprisingly, onChange in Dojo works the same. However it is possible to make it fire whenever the value changes by using intermediateChanges. 

The built-in dijit property, intermediateChanges, is a part of dijit.form widgets. By default it is set to false, but when it is set to true, it fires the onChange event whenever the value of the form widget changes.  This way it is possible to trigger something while the user is editing a property and before a text input looses focus.  

 

image

Nov 25, 2015

Comments

Please login to comment.
Latest blogs
Automate Your OCP Opal Tool Development with PowerShell

Creating an OCP (Optimizely Connect Platform) Opal Tool app from scratch can be time consuming and error prone. You need to set up the project...

Sanjay Kumar | Feb 21, 2026

Using HeadlessKit to build a head for an Optimizely SaaS CMS in .NET 10

Headless has a tendency to promise freedom and deliver alignment meetings. Two codebases. Two sets of models. Two teams trying very hard not to dri...

Allan Thraen | Feb 19, 2026 |

CMS 13 Preview 3: Key changes

If you've been following along with the CMS 13 preview, you've likely worked through the initial upgrade path covered in my previous post. Preview ...

Robert Svallin | Feb 19, 2026

A Tailwind CSS strategy for Visual Builder grids

More findings from using an Optimizely SaaS CMS instance; setting up a CSS strategy for rendering Visual Builder grids.

Johan Kronberg | Feb 18, 2026 |