Add 'auto-submit' functionality to the exposed form

1. +++ b/js/auto_submit.js
   @@ -0,0 +1,105 @@
   +      // The change event bubbles so we only need to bind it to the outer form.
   ...
   +        .filter('form, select, input:not(:text, :submit)')
   +        .once('bef-auto-submit')
   +        .change(function (e) {
   +          // don't trigger on text change for full-form
   +          if ($(e.target).is(':not(:text, :submit, .bef-auto-submit-exclude)')) {
   +            triggerSubmit.call(e.target.form);
   +          }
   +        });
   

   In an ideal world I would have written an object doing that kind of stuff, rather than just putting the entire logic into an behaviour

2. +++ b/src/Plugin/views/exposed_form/BetterExposedFilters.php
   @@ -539,6 +571,17 @@ Off|No
   +      $form = array_merge_recursive($form, array('#attributes' => array('class' => array('bef-auto-submit-full-form'))));
   +      $form['actions']['submit']['#attributes']['class'][] = 'bef-auto-submit-click';
   

   This stuff should not use classes but rather data attributes. Classes are meant for styling purposes. At least this is what core is doing now more and more.

Thank you for the patch, @amateescu, and the review, @dawehner!

Setting to NW based on #3. I'll try to find time this week to make those changes but will happily commit if someone beats me to it!

Would love to see that feature also. Looking forward!

Addresses #3.2 (moves JS interactions from classes to data attributes). Would love to have another set of eyes look/test this as I don't have the bandwidth for more complete testing at the moment.

Speaking of which, were there any automated tests for this in D7's CTools? I'm guessing not...

I'll look into #3.1 later today but I'm not opposed to committing this without that change as there are a few other BEF bits that could use a similar refactor.

I'll look into #3.1 later today but I'm not opposed to committing this without that change as there are a few other BEF bits that could use a similar refactor.

Sure we can always do that later.
One follow up which could be open is to provide some form of javascript test coverage.

Committed. Thank you!

Opened #2776801: BEF needs automated Javascript tests as a followup.