Works very well within the limitations of the implementation (only triggers when new DOM elements are added).
However, not sure how it should fit into compound skills since new elements maybe added and then removed as a consequence of the multiple actions.
E.g. imagine entering Source and Destination in a flight booking site. Source will trigger a drop down with potential matches, and it will disappear when destination is entered. So any Source related element additions are not valid anymore.
Other option could be we keep track of added and removed nodes and somehow give a net change, which gets complicated logic wise.
Works very well within the limitations of the implementation (only triggers when new DOM elements are added). However, not sure how it should fit into compound skills since new elements maybe added and then removed as a consequence of the multiple actions. E.g. imagine entering Source and Destination in a flight booking site. Source will trigger a drop down with potential matches, and it will disappear when destination is entered. So any Source related element additions are not valid anymore.
Other option could be we keep track of added and removed nodes and somehow give a net change, which gets complicated logic wise.