View Single Post
Old 04-10-2024, 03:46 PM   #37
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,567
Karma: 7043711
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by JSWolf View Post
It doesn't work correctly in Thorium Reader for Windows.
You must have made a mistake. It DOES work in Thorium:

Click image for larger version

Name:	Image1.png
Views:	54
Size:	44.6 KB
ID:	207487

and also in ADE 4.x:

Click image for larger version

Name:	Image2.png
Views:	51
Size:	35.1 KB
ID:	207488

It works everywhere that supports flex-box.

But the point is not that. The point is that one can employ "fancy" code for simple layouts, so users with a proper device can get the best reading experience, and since you also have included fallback code, users with old device will get a suboptimal output. With flex-box, you'll get all perfectly spaced, no need to calc margins, no need to worry about anything. And all always perfect no matter if the font-size is increased. As I said, you can't get that with only css2 properties (of course, you'll have to employ them because of the fallback code, but the result won't be so good for all of them with old devices).
RbnJrg is offline   Reply With Quote