Considerations and limitations

  • Events are disabled by default. Events occur only if they are explicitly enabled in the configuration.
  • When no RhythmExtensibilityConfig is defined, widget behavior is identical to a standard installation. There is no performance impact.
  • Events use the browser-native CustomEvent API. No additional libraries or polyfills are required.
  • Each widget uses a unique scope prefix. Events from one widget do not interfere with other widgets.
  • Listener errors are caught and logged. A faulty listener cannot break widget functionality.
  • Listeners can be registered before or after the widget loads. There are no race conditions.
  • The configuration is evaluated at runtime. Changes to the enabledEvents array take effect immediately without a page reload.