View Single Post
Old 08-08-2025, 08:13 AM   #29
Turtle91
A Hairy Wizard
Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.
 
Turtle91's Avatar
 
Posts: 3,369
Karma: 20212733
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
Quote:
Originally Posted by JSWolf View Post
You should never use webkit code. It's not part of ePub. You need to redo your code so there is nothing about webkit present.
I disagree completely. A standards compliant reader/device/app will gracefully ignore anything it doesn't understand. If you include items like webkit selectors the reader will use them if it can, and ignore them if it can't.

Code:
.noBreakAfter {
    -webkit-column-break-after: avoid;
    page-break-after: avoid;
    break-after: avoid;
}
This is simply trying to cover all the bases for all the different types of devices.

You may run into issues where an older automated epub checker could throw a flag saying it isn't an ePub selector, but that wouldn't make the ePub invalid.

If your targeted device/app supports it, and you want/need it to do what you need, then go for it!

Last edited by Turtle91; 08-08-2025 at 08:17 AM.
Turtle91 is offline   Reply With Quote