Change inview completion to top

[swashbuck]

Subject of the issue

This component is almost always used as a bookend to a page. In certain cases when the plugin is not set to optional, the component is not fully scrolled into view. A use case that we found involved a screen reader user using keyboard navigation on a laptop viewed at 150% zoom level. The Trickle would autoscroll to the Page Nav block. However, because the entire Page Nav was not scrolled into view, the "next" button remained disabled. The user needed to disable the virtual cursor and manually scroll down to enable register inview completion which then enabled "next" button.

Suggest changing inview completion to require that only the top of the Page Nav comes into view.

It would also be helpful to include the default _isOptional value in the example.json as a reminder to developers that it needs to be reviewed. We typically will set this to 'false' but it defaults to 'true' like other presentation components.

Screenshots

Here, the Page Nav has not come fully into view. So, the "next" button is not enabled. This can cause issues with keyboard navigation.

[github-actions]

🎉 This issue has been resolved in version 3.1.7 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀