People will disabilities that rely on screen-readers don't love it. There is no such a problem with HTML/CSS which should be the norm for internet documents.
> With PDF, everyone sees the same thing.
Yes, provided you can see at first place...
It should be. But meanwhile everybody seems to think it is perfectly ok that there is a bunch of JavaScript that needs to run before the document will display any text at all and how that text makes it into the document is anybody's guess.
My bashful take is that nobody told the rest of the web development world that they aren't Facebook, and they don't need Facebook like technology. So everyone is serving React apps hosted on AWS microservices filled in by GraphQL requests in order to render you a blog article.
I am being hyperbolic of course, but I was taken completely off guard by how quickly we ditched years of best practices in favour of a few JS UI libraries.
Why would I want document type that can't even refloat on display size to represent any longer written text that is supposed to be consumed on digital device?
And as a format, it's much more sane than, say, Word or Excel.
Even if the focus on "where do I put this glyph" means the original text isn't in there by default.
FWIW this is not a technical barrier; it would be absolutely trivial to associated blocks of non-flowed text with the layed out text.
[1] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Im...