No results behavior hides entire view

Thanks for the quick response @jerdavis! Yes, I have a simple "Global: Text area" no results behavior on the view. I take it you can't reproduce the bug on your end?

I just ran lando composer require drupal/viewfield:3.x-dev. Then removed my contrib modules and ran lando composer install which seems to put me at commit aef60a6, but I'm seeing the same thing. I must have an error in one of my templates. I'll do a little more digging and close the loop here when I find something.

Oh also, I forgot to mention that the viewfield is on a paragraph that is being placed on the node. That might be an important detail.

Another nonstandard thing I'm doing is setting the form action value for the exposed filters. Basically when using an exposed filter it was sending me to the path specified in the page display for the view, however I wanted to stay on the current node where the paragraph (with the viewfield) was placed. I accomplished that like this:

/**
 * Implements hook_form_alter().
 */
function mymodule_form_alter(&$form, $form_state, $form_id) {
  if ($form["#form_id"] == 'views_exposed_form') {
    $current_path = \Drupal::service('path.current')->getPath();
    $form["#action"] = $current_path;
  }
}

The no results behavior does indeed work if I comment that out and allow the exposed filters to send me to the path specified in views. Is there a better way to accomplish the behavior of staying on the node where the paragraph (containing the viewfield) is placed? Would using a block display instead of a page display work by default? This is for a migration project, so I was simply trying to recreate what previously existed in D7, which was using page displays. Thanks!

AJAX was turned off, enabling it throws a TypeError: offset is undefined error in the console and doesn't narrow results.

The exposed filters are part of the view itself, not a separate block.

I believe it's error with enabling AJAX, more specifically ajax_view.js. It doesn't happen when setting "Use AJAX" to "no" in the view settings. I pasted the full browser console errors below.

Chrome:

ajax_view.js?v=8.6.17:125 Uncaught TypeError: Cannot read property 'top' of undefined
    at Drupal.AjaxCommands.viewsScrollTop (ajax_view.js?v=8.6.17:125)
    at ajax.js?v=8.6.17:435
    at Array.forEach (<anonymous>)
    at Drupal.Ajax.success (ajax.js?v=8.6.17:433)
    at Object.success (ajax.js?v=8.6.17:234)
    at Object.t.success (jquery.form.js:278)
    at i (jquery.min.js?v=3.2.1:2)
    at Object.fireWith [as resolveWith] (jquery.min.js?v=3.2.1:2)
    at A (jquery.min.js?v=3.2.1:4)
    at XMLHttpRequest.<anonymous> (jquery.min.js?v=3.2.1:4)

Firefox:

TypeError: offset is undefinedajax_view.js:125:9
    viewsScrollTop ajax_view.js:125
    success ajax.js:435
    forEach self-hosted:266
    success ajax.js:433
    success ajax.js:234
    jQuery 5
    success
        i
        fireWith
        A
        c

Good call, yes we did override the views-view.html.twig template. I still couldn't get the {{ attributes }} working properly though - possibly something we're messing up in preprocess with custom code.

I tried using a block display instead of a page display on the view, but then the exposed filters no longer appeared so I switched back to a page display.

Solution: Finally I noticed that I had not configured the viewfield's display settings correctly on the paragraph. So under "Manage Display" if you click the gear icon to the right of your field, just tick the "Always build output" checkbox, update and save. Hopefully that helps someone!

Thanks for all the help debugging @jerdavis! This is all set for us :)