This is an edge case that needs to be addressed.
When the read-along web component is embedded in a site which has a fixed menu or navigation bar - the type element, which takes up "X" pixles of the top of the viewport, high z-index so content scrolls underneath it - and it contains a page that requires vertical scrolling, the scrolling logic being unaware of this design pushes the component under the navbar, this degrades the user experience, since the user has to constants manual scroll the component into "view" as the read-along progresses.
Conditions:
This is an edge case that needs to be addressed.
When the read-along web component is embedded in a site which has a fixed menu or navigation bar - the type element, which takes up "X" pixles of the top of the viewport, high z-index so content scrolls underneath it - and it contains a page that requires vertical scrolling, the scrolling logic being unaware of this design pushes the component under the navbar, this degrades the user experience, since the user has to constants manual scroll the component into "view" as the read-along progresses.
Conditions:
page with a navbar that floats (high z-index) and lets the content scroll underneath. It must use up some of the viewport's top "real estate".
Read-along with vertical scrolling pages