Idea Summary:

Enhance the resilience of the OutSystems UI Date Picker widget initialization, specifically when testing mobile views using Chrome DevTools' device simulation. Currently, the widget does not always reinitialize properly after a hard refresh in this environment, potentially leading to confusion during development and QA.

Issue Description:

When simulating a mobile device in Chrome DevTools and performing a hard refresh, the Date Picker widget occasionally fails to initialize correctly. This behavior appears to be due to:

• JavaScript/UI libraries not consistently re-triggering widget initialization in simulated environments.

• The use of dynamic selectors (e.g., .active, input.form-control.OSFillParent.input.active) in the widget’s initialization logic, which may not be immediately available after a refresh.

Key Observations:

• On actual mobile devices (e.g., Safari on iOS), the widget functions reliably, even after refreshes.

• In Chrome DevTools mobile simulation, the widget behaves correctly on initial load or when toggling to mobile view but fails after a hard refresh.

Impact:

• Creates confusion during testing and QA phases.

• May mislead developers into thinking the widget is broken.

• Increases friction when debugging using browser tools.

Suggested Improvements:

• Make initialization more robust in simulated environments.

• Avoid dependency on dynamic class-based selectors that may not exist immediately on load.

• Implement fallback logic or explicit reinitialization to handle DevTools mobile simulation scenarios.

Thanks,

Senthil