more ci failure investigation - how far does it get before js alert popups up

Author: danielabar

spec/support/date_range_picker_shared_example.rb

@@ -114,7 +114,9 @@ def date_range_picker_select_range(range_name)
 
       date_range = "nov 08 - feb 08"
       page.execute_script("document.getElementById('filters_date_range').focus();")
+      puts "🔍 AFTER FOCUS - URL: #{page.current_url}"
       page.execute_script("document.getElementById('filters_date_range').value = '#{date_range}';")
+      puts "🔍 AFTER POPULATE DATE RANGE - URL: #{page.current_url}"
       # What we really want here is to simulate user hitting Enter to submit the form but only this click worked
       # But on CI, this ends up triggering a JS alert instead of submitting the form
       # FIXME: Can we use something like requestSubmit() to submit the form?
@@ -130,7 +132,7 @@ def date_range_picker_select_range(range_name)
       # Whereas locally it's transitioned to reflect the filters:
       # http://127.0.0.1:53534/distributions?filters%5Bby_item_id%5D=&filters%5Bby_partner%5D=&filters%5Bby_location%5D=&filters%5Bby_state%5D=&filters%5Bdate_range%5D=nov+08+-+feb+08&filters%5Bdate_range_label%5D=during+the+period+31+May+to+31+Aug&button=
       # So on CI, clicking the filter button after "tabbing" into the date range field does not submit the form, or not yet, and JS alert is running first
-      puts "🔍 URL: #{page.current_url}"
+      puts "🔍 AFTER SUBMIT FORM - URL: #{page.current_url}"
 
       # === ON CI: JS ALERT SHOWS UP HERE ===