K4iOS & Night Mode Media Queries

[mattmc]

I got my Kindle Oasis yesterday, and tried out the MQ on it. Looks good. It actually has exactly the same dimensions as the Voyage, apparently:

http://ebookfriendly.com/kindle-oasis-2016/

Nevertheless, it was good to test it to be sure.

[Hitch]

Originally Posted by mattmc

I got my Kindle Oasis yesterday, and tried out the MQ on it. Looks good. It actually has exactly the same dimensions as the Voyage, apparently:

http://ebookfriendly.com/kindle-oasis-2016/

Nevertheless, it was good to test it to be sure.

Yo! Not to thread-jack, but does it have that same image rendering bug? The "image-is-greater-than-50%-of-the-screen-so-it-blows-the-hell-up" bug?

Hitch

[mattmc]

Originally Posted by Hitch

Yo! Not to thread-jack, but does it have that same image rendering bug? The "image-is-greater-than-50%-of-the-screen-so-it-blows-the-hell-up" bug?

Hitch

Not super familiar with that, because I didn't have a Voyage until today. Do you have an appropriate sample file you want to send my way?

[Hitch]

Originally Posted by mattmc

Not super familiar with that, because I didn't have a Voyage until today. Do you have an appropriate sample file you want to send my way?

I'm sure I can find one and send it on, but it's uber-easy to test: set ANY image that's typically meant for slightly larger than half the width of the screen to 50% or greater (width) and see if it blows up.

The Voyage has a persistent bug. If you use (for example) a chapter head image, and it's wide-ish, but not meant to be full-width, you end up with full width. Any width: X% class that you set at 50% or greater blows up to the full width of the screen. I have had discussions with Amazon--they weren't aware of it when we first reported it, but I haven't been advised of any progress on it.

Hitch

[Notjohn]

How awful. Will 49% work?

I'm beginning to appreciate Wm Buckley's credo: to stand athwart Progress and yell "Stop!"

[Hitch]

Originally Posted by Notjohn

How awful. Will 49% work?

I'm beginning to appreciate Wm Buckley's credo: to stand athwart Progress and yell "Stop!"

Hi:

At our last test, yes, 49% works. But there are just SOME items that need to be, say, 60% or 70%, etc. It's very frustrating.

Hitch

[dgatwood]

Originally Posted by mattmc

I would say it certainly compares. My experience with a Kepub and their wack rendering engine is that it eviscerated my book. Normal page-break CSS doesn't even work: https://github.com/kobolabs/epub-spec/issues/18

To me, that's actually far worse than stripping out your embedded fonts.

In terms of the user experience, yes, at least for now, but it is also a bug that they'll eventually fix, as opposed to modifying the content in a way that will make it be forever broken, which makes it less bad at least in the long term.

Incidentally, I find the spec linked from that page to be fascinating. What it tells me is that on iOS and Android, they used the native rendering engines (either WebKit or Blink, which is based on WebKit), but used something else on other platforms for some baffling reason. Whatever that "something else" is, it apparently isn't a fully functioning CSS layout engine. I'd imagine if I fed it my content on Windows in KePUB mode, it would keel over and die.

Or I could be wrong, and they might have used WebKit, but hacked together the pagination in some custom way rather than using it in paged media output mode like you'd use if you were printing. Hard to say which.

[mattmc]

Originally Posted by dgatwood

Incidentally, I find the spec linked from that page to be fascinating. What it tells me is that on iOS and Android, they used the native rendering engines (either WebKit or Blink, which is based on WebKit), but used something else on other platforms for some baffling reason. Whatever that "something else" is, it apparently isn't a fully functioning CSS layout engine. I'd imagine if I fed it my content on Windows in KePUB mode, it would keel over and die.

Or I could be wrong, and they might have used WebKit, but hacked together the pagination in some custom way rather than using it in paged media output mode like you'd use if you were printing. Hard to say which.

Based on this thread they use the NetFront ACCESS browser (substantiated here) which I had never heard of before I ran across that thread. Seems like it might be based on Blink?

@Hitch, sorry I haven't been able to test the 50% thing on my Oasis yet--been up to my eyeballs, but it is in the back of my mind.

[Hitch]

Originally Posted by mattmc

@Hitch, sorry I haven't been able to test the 50% thing on my Oasis yet--been up to my eyeballs, but it is in the back of my mind.

Hell, we have so many other Amazon weirdnesses going on that to tell you the truth, I'd spaced that the damn thing even EXISTED, much less might have the same issue (as the V).

When you can is more than soon enough. I appreciate it, though. I do.

Hitch