There seems to be a bug in the way C4.3 renders custom widgets when used in a function.
Scenario: Follow the instructions here http://docs.composite.net/Console/Custom-Widgets/Custom-Picker but instead of using it as a form control use it as a function widget by implementing IWidgetFunction.
Expected Result: The widget behaves the same regardless of if it's in the Basic view or Advanced view.
Actual Result: The widget is allowed to run its JS in the Basic view but in the Advanced view the JS is not executed.
This causes problems when doing anything custom like defining a DialogViewDefinition as in the sample or trying to create a custom binding.
Scenario: Follow the instructions here http://docs.composite.net/Console/Custom-Widgets/Custom-Picker but instead of using it as a form control use it as a function widget by implementing IWidgetFunction.
Expected Result: The widget behaves the same regardless of if it's in the Basic view or Advanced view.
Actual Result: The widget is allowed to run its JS in the Basic view but in the Advanced view the JS is not executed.
This causes problems when doing anything custom like defining a DialogViewDefinition as in the sample or trying to create a custom binding.