I've just got into this entire world of creating eBooks and I'm stupefied as to why we have the codability to create such dynamic web pages and yet we can't seem to make eReaders capable of handling dynamic yet relatively fixed content.
Here is a quick example of how a dynamic yet relatively fixed content would look like:
(Edited: version 10 uses "vh" and 11 uses "vw". All positioning is absolute by top and left percent. All sizing is dynamic by percent.)
(Edited: Working Prototype)
(Edited: "position: relative" design with working "onload" function. Will NOT throw errors in epubcheck:)
The ONLY issue here is that the font-size: *vw; DOESNT work in eReaders! We could have reflowable content in a jiffy if we just made a specification that allowed for dynamic viewports (that actually worked) and then setting the font size to this native css "vh" and "vw" font sizes.
I am stupefied as to why this is so complicated. That little jsfiddle could EASILY be automated to take in parameters from programs like Indesign or even .doc files and grab the fundamental percent distances of those regions, grab the text frames available and then style the content accordingly.
...WITH page numbers.
So again, just want to reiterate that if and only if the text is able to be fixed in its volume-fill of the container through dynamic font-sizing then this jsfiddle example would NEVER have text overflow regardless of the viewing window's size. Which that is really the problem with eReaders. They don't allow for viewport to be set to "device-width" and "device-height". You can only put in a static pixelated resolution. This is just wrong. There is no reason why something like this shouldn't be allowed.