i don't think you can know the height of its "content". its physical height is one thing;
what's actually visible at any given time on any given device might not be knowable.
or at least not controllable by you. (technically, you could capture the screen and see
exactly what the user sees, but that's not going to be of any use to you.)
i think you have to approach it from a different angle, i.e., the way a pdf document
does with discrete "pages" whose content is controlled by you. that way, when the
user taps "page down", a knowable page is produced. whether that actually works
on a webview is unclear. in any case, i think you have to generate content that is
guaranteed to fit in a webview viewport. then create pages that can be called as
the user taps the up/down button. you're doing it the other way 'round, ie, starting
with all the content and trying to divide it up into virtual pages (which may or may
not exist). at least that's how it strikes me.
i don't understand what you mean by a webview's "auto hide" scrollbars. as
far as i am aware, they are "auto visible" unless you manually hide them, which can
easily be done.