Quote:
Originally Posted by graycyn
Could you have BOTH instructions, or would that cause issues? Like so:
Code:
break-after: avoid;
break-after: avoid-column; /* This is for ereaders that employ multi-column to display pages */
-webkit-column-break-after: avoid; /* This is for ereaders that employ multicolumn to display pages */
I'm just wondering if there are apps that might prefer one instruction over the other, and therefore, both might be needed? |
No issue at all; you can employ those properties because if an ereader doesn't support one of them, it will ignore it. But in my tests, I discovered that those ereaders that support -webkit-column-break-after|before|inside", they also support "break-after|before|inside".
Today, virtually all epub3 readers mimic pagination using multi-columns, making the use of the "break-after|before: avoid-column" or "break-after|before: column" property (to force a break) almost indispensable. Of course, you also have the Webbit alternative.