Views admin UI proximity filter setting does not update dynamically based on other setting changes

[indigoxela]

This is only a problem in views UI. This is the form in the dialog:

Multiple other settings in the same form should influence the form widget, but none of them does by AJAX:

Different types of proximity plugins have different input forms for the value.

The operator also has some influence (between, not between obviously needs two distance inputs).

Grouped filters have a table style display with multiple of those form items, each row has its own operator setting (not visible in this screenshot). But grouped filters with complex forms are a topic on its own in views. 😉

There's a callback - geofield_views_ui_change_proximity_widget(), but that only works with Javascript disabled and also then in limited cases.
Although there's some JS, this can never work, as this form isn't cached. As it's not available from the tempstore, validation for the form token fails.
Same problem occurs, if we'd switch to #ajax - failing form token validation.

The only thing that might work is to switch to an ajax path (not callback) with custom PHP and JS code. But still tricky.
This is a known problem in Drupal 7 which never got resolved.

And in D10 proximity search is substantially different.

A tricky bug.

Workaround

Super silly, but the only way. Whenever you have to change either of the 3 form values:

• Source of Origin Point
• Operator
• Grouped filters

Submit the dialog twice. The first time change the value that should trigger a form change, then open the dialog again, possibly change depending values and submit again.
The double dialog submit is the trick.

Awkward, though.

[indigoxela]

I don't think, I'll get any closer than with #75.

This works for single filter proximity, I see no way to get this working with grouped exposed filters in reasonable time. I already spent waaaay to much time on this problem.

For grouped exposed filters the workaround stays relevant (double dialog submit).

I'd suggest to create a follow-up issue for grouped and link to that from this module's readme under "known issues".

[indigoxela]

One tiny step further, it's now possible to dynamically change the proximity plugin forms inside the draggable table (grouped filters) based on "Source of Origin Point". There's no way to update the form item inside the draggable table based on individual select list changes inside the table, but that's such an exotic use case...
The dom structure in the grouped exposed filters table is super impractical for any JS manipulations.