About page-break - Page 4

JSWolf · 01-16-2026, 12:19 PM

Quote:

Originally Posted by icearch

And with some testing, div and p do have different attributes, that is p have margin-block-start and margin-block-end with both 1em, which div does not have.

You set the margins and other tributes for p in CSS

icearch · 01-16-2026, 01:28 PM

And for record, I'm posting two pics of codes, one with class and one without.

To my eyes (maybe just because I have stared this for months), the one with class looks cleaner than the one without.

jackie_w · 01-16-2026, 03:18 PM

Quote:

Originally Posted by JSWolf

And one other thing I forgot to post is I use the patch that turns on hyphenation in KePub.

... which will be using -webkit-hyphens:auto to turn on kepub hyphenation. Read the patch's Description if you don't believe me.

JSWolf · 01-16-2026, 05:25 PM

Quote:

Originally Posted by jackie_w

... which will be using -webkit-hyphens:auto to turn on kepub hyphenation. Read the patch's Description if you don't believe me.

But what I was saying is not to use webkit code inside an ePub as it's no valid ePub code. Using webkit to turn on hyphenation outside or an ePub is OK.

I'm trying to keep the ePub valid which it won't be with webkit code on the inside.

JSWolf · 01-16-2026, 05:27 PM

Quote:

Originally Posted by icearch

And for record, I'm posting two pics of codes, one with class and one without.

To my eyes (maybe just because I have stared this for months), the one with class looks cleaner than the one without.

To my eyes, the classless sample looks better. The rule of thumb is to keep it as simple as possible. That works when you don't have classes you don't need.

Falkor · Yesterday, 05:07 AM

Quote:

Originally Posted by JSWolf

You need to stop with the webkit code that's not valid ePub code. If the program being used needs the webkit code, then it's broken and needs to be fixed.

You keep saying that, but I don't get any errors in EpubCheck by including prefixed properties. It’s valid.

JSWolf · Yesterday, 08:31 AM

Quote:

Originally Posted by Falkor

You keep saying that, but I don't get any errors in EpubCheck by including prefixed properties. It’s valid.

Please show me any set of ePub specs that show webkit code as part of the specification. Thanks.

Turtle91 · Yesterday, 09:52 AM

Quote:

Originally Posted by JSWolf

Please show me any set of ePub specs that show webkit code as part of the specification. Thanks.

ePub 3.3 standard:

Quote:

6.3.1.3 Prefixed properties

Earlier version of EPUB included prefixed CSS properties, as many CSS features related to world languages were not yet mature. To ensure backwards compatibility for content authored using these prefixes, they have been retained in this specification. Unless otherwise noted, prefixed properties and values behave exactly as their unprefixed equivalents as described in the appropriate CSS specification. The prefixed properties are documented in E. Prefixed CSS properties.

Granted, it does continue with a caution that you should use the unprefixed css as much as possible because there is no telling how long they will stay supported… but, as of now, they are…

Also, even if the device/app does NOT support them, they are required to degrade gracefully…. In other words - ignore it.

RbnJrg · Yesterday, 10:07 AM

Quote:

Originally Posted by Turtle91

ePub 3.3 standard:

Quote:

6.3.1.3 Prefixed properties

Earlier version of EPUB included prefixed CSS properties, as many CSS features related to world languages were not yet mature. To ensure backwards compatibility for content authored using these prefixes, they have been retained in this specification. Unless otherwise noted, prefixed properties and values behave exactly as their unprefixed equivalents as described in the appropriate CSS specification. The prefixed properties are documented in E. Prefixed CSS properties.

Granted, it does continue with a caution that you should use the unprefixed css as much as possible because there is no telling how long they will stay supported… but, as of now, they are…

Demolisher!!

JSWolf · Yesterday, 10:24 AM

Quote:

The Working Group recommends that EPUB creators currently using these prefixed properties move to unprefixed versions as soon as support allows, as the Working Group does not anticipate supporting them in the next major version of EPUB.

They will become invalid. So you'd have to fix your ePub to work without. So you may as well do that now instead of later.

Turtle91 · Yesterday, 10:27 AM

Quote:

Originally Posted by JSWolf

Then they will become invalid. So you'd have to fix your ePub to work without. So you may as well do that now instead of later.

Again, no.

They would degrade gracefully… in other words - ignore it.

JSWolf · Yesterday, 10:28 AM

Quote:

Originally Posted by Turtle91

Again, no.

They would degrade gracefully… in other words - ignore it.

That does not sound like degrade gracefully at all. That says stop working. Meaning one day it's allowed, then it's not. No inbetween.

jhowell · Yesterday, 11:20 AM

Quote:

Originally Posted by Turtle91

ePub 3.3 standard:

6.3.1.3 "Prefixed properties"
...
The prefixed properties are documented in E. Prefixed CSS properties.

While I agree with your stance on property names that begin with "-webkit-" and other prefixes, if you look at the cited appendix it becomes clear that "Prefixed properties" in this case refers to property names that begin with the "-epub-" prefix.

icearch · Yesterday, 12:23 PM

If something works now and does no harm if not working, than just use it.

Human olds eventually, should one start to riding wheelchair instead of walking at their 20s, because they will need that eventually?

Turtle91 · Yesterday, 02:53 PM

Quote:

Originally Posted by JSWolf

That does not sound like degrade gracefully at all. That says stop working. Meaning one day it's allowed, then it's not. No inbetween.

Using that logic then you MUST use only ePub3 because eventually ePub2 will no longer be supported!!

01-16-2026, 01:28 PM	#47
icearch Connoisseur Posts: 67 Karma: 10 Join Date: Nov 2025 Device: none	And for record, I'm posting two pics of codes, one with class and one without. To my eyes (maybe just because I have stared this for months), the one with class looks cleaner than the one without. Attached Thumbnails

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
page-break-before: always;	avresbo	Kobo Reader	1	03-02-2023 09:30 AM
Do you use page-break-after and page-break-inside?	fluoresce	ePub	14	05-24-2017 02:57 AM
No page break for H2	RickAltman	Calibre	2	06-25-2012 12:02 PM
PAGE BREAK	JFS-NMF	Recipes	0	03-04-2011 10:15 AM
Page break before <b>	flowoeB	Calibre	14	04-12-2009 04:05 PM

Yesterday, 12:23 PM	#59
icearch Connoisseur Posts: 67 Karma: 10 Join Date: Nov 2025 Device: none	If something works now and does no harm if not working, than just use it. Human olds eventually, should one start to riding wheelchair instead of walking at their 20s, because they will need that eventually?

Advert

Advert