Pager breaks exposed filter on taxonomy reference field

A view with a pager and an exposed filter for a field that is a taxonomy term causes issues after clicking on a link in the pager to go to another page. When visiting the second or other pages the filter stops working and the filter displays the value of "Array".

To recreate on a fresh install of 8.0.5:

1. Install the devel and devel_generate modules (easiest way to create enough testing records to easily see the effect, feel free to do it by hand if you are in the mood)
2. Create a vocabulary named Foo
3. Add a few terms to Foo.
4. Edit the fields for a content type. Use Basic Page for simplicity.
5. Add a term reference field to the content type. Make sure it only accepts one value. and is restricted to the Foo vocabulary
6. Run devel generate to populate a few (100 will be more than enough) basic page nodes
7. Create a new view of content of type basic page and create a page for it. Unformatted list is fine. Display fields. make sure there is a pager and set the number of results to 10.
8. Add a filter to the view. Select the field that is a taxonomy term reference. Do not use "Has taxonomy term" or "Has taxonomy term with depth" but select the field itself. Make the filter exposed and a autocomplete.
9. save the view and look at the page for it.
10. Now in the autocomplete start typing one of the terms you created and select it to set the filter.
11. Click apply.
12. Everything works as expected. Take a look at the URL and the argument for the filter is something like 'field_name_target_id=term_name (3)' (after being url_decoded)
13. In the pager click on page 2.
14. Suddenly value displayed in the filter now says "Array" and the filtering is no longer working.
15. Take a look at the url of the page and look at the argument for the filter and you will see it is something like 'field_name_target_id[0][target_id]=3' (after being url_decoded)

If anyone needs more information I will be happy to provide it.