Naïve question: is there any possibility to build from bleed in CSS Paged Media Module Level 3. Unless authors and RSs share a set of building blocks somehow “à la AMP”, which could be entirely overridable, I must admit don’t see how. I’ve been wondering if this complex issue can be fixed for months now. Maybe this is opinionated but in practice, this is the root of one evil. To be honest, if I were a RS developer, I would refuse to implement it until some popular authoring solutions fix their CSS output. I’ve already shared my fear about that a few months ago but I can see authoring software declaring this metadata by default and then RS just ignoring it-or even not implementing it in the first place because they can foresee the abuse. Metadata to request that RS not override ebook styles? Once you throw the CSS in a RS, nasty stuff can happen so we tried to make it compatible with a selection of Reading Systems, which basically translates to “it doesn’t break shit in there” (especially user settings). It just makes it more predictable for authors, on their side. Obviously, it doesn’t solve all of the authors’ nor Reading Systems’ problems. What about resets and frameworks like Blitz px fails because for some reason Amazon Kindle or android apps have a viewport in physical pixels (and not 2x or 3x), % may become huge depending on the container (which can almost be the size of the screen) or play not very nicely with outside list-type for instance.įor the record, I tried to hack my way at some point, the idea was to get decreasing/increasing horizontal margins depending on the current font-size.Īnd yeah I know you could probably abuse max-width, margin-left: auto and padding-left (to emulate a min-margin-left) but you’re still dealing with px or %. You can't make any assumption about the RS config. Maybe even an "!important-in-JS" apocalypse.īest practices for units (a common problem is for margins in ems causing massive problems on small screens) I’m kinda cool with the idea Reading Systems may ignore some “layout” styles if needed ( margins, padding and stuff) but how do you build a solid cascade if you can’t style body and let that to RSs? All of a sudden you have to use bloated selectors or add styles to an awful amount of elements, which might even worsen the overrides and user settings issues to some extent.Īuthors will simply overqualify selectors or use obscure proprietary CSS props to get around this limitation-it is already the case because !important doesn't work. No author styles for html and body elements? To be honest, it’s very difficult for me to imagine Apple (for instance) doing the latter since it looks like they’re not even willing to fix their implementation for media queries (it’s been 2 and a half year the issue is open). My biggest concern is about the following though:ĮPUB reading systems typically display author content inside a div or frame, with unknown styling applied both outside and inside the frame.Īs I can see it, from the outside, it’s either implementing the stuff using awful hacks to make it happen or “refactoring” the RS to accommodate it. I’ve found a bunch of nasty bugs lately and it seems to me this is becoming a real huge barrier which makes evolution super painful. Idea of page float necessary for text to continue normally before/after image otherwise there could be huge gaps before imageĪlready kind of possible with a good old float in current RSs, but can impact pagination in awful ways, especially when CSS multicol is used-the spec/implementations probably need updating by the way, since it is very hostile to modern layout specs (flexbox, grid, etc.). Again, just thinking about what CSS currently has to offer for dealing with this. Object-position should do the trick as well. It’s not currently supported in EdgeHTML but development has started.Ĭontrols for both vertical and horizontal alignment? The easiest solution probably lies in object-fit ( cover, contain, scale-down, etc.) on the authors’ side (and perhaps on the RS’ side as well). What happens when the image doesn't exactly fit the screen? Aspect ratio must be preserved (always?) Or maybe set the rule that -epub-bleed overrides it so that it can serve as a fallback (because we’ll need one). Sure this would be “another context” but I guess it would be a lot easier to get rid of that and let RS developers deal with the height when -epub-bleed is used. In practice, I’m currently using an arbitrary 99vh in reflow because 100vh tends to overflow on the next page in a lot of RS, even with box-sizing: border-box. One should note 100vh has been problematic on mobile, especially because of browsers’ chrome.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |