Beta testing calibre 4

[Geremia]

ebook-viewer's interface font is tiny on high DPI screens, and the window is stuck on full-screen even when I click "Exit Full Screen". It doesn't remember changes in min font size or zoom step size. Also is there no page-wise scrolling anymore? thanks

[gbm]

Originally Posted by rashkae

Comments on 3.99.4

I don't know if it can be fixed, but I observe that height in proportion to the screen no longer work, (ex: height: 100% or max-height: 100%)

Also, the inspector in the Book viewer doesn't seem to work. Data doesn't populate into the bottom half of the inspector pane.. but it works perfectly in the Editor.

Originally Posted by gbm

Edit:



Use full screen inspector will be on the right, if you are not using full screen then undock inspector and move it.

bernie

I see what you mean, the popup tool-tip appears to be working.

bernie

[kovidgoyal]

Originally Posted by rashkae

Comments on 3.99.4

I don't know if it can be fixed, but I observe that height in proportion to the screen no longer work, (ex: height: 100% or max-height: 100%)

No it cant be fixed, use viewport units instead. 100vh will do the trick.

Also, the inspector in the Book viewer doesn't seem to work. Data doesn't populate into the bottom half of the inspector pane.. but it works perfectly in the Editor.

Yeah this is a result of sandboxing in the viewer (the book contents are rendered in a sandboxed iframe). You can still inspect the HTML but not the CSS. Seems to be a limitation of devtools in webengine.

[kovidgoyal]

Originally Posted by Geremia

ebook-viewer's interface font is tiny on high DPI screens, and the window is stuck on full-screen even when I click "Exit Full Screen". It doesn't remember changes in min font size or zoom step size. Also is there no page-wise scrolling anymore? thanks

What OS do you see tiny fonts on? Works for me in linux. I also cannot reproduce it not exiting full screen. And it remembers those settings for me. Are you running the current beta version 3.99.4?

[kovidgoyal]

Originally Posted by kovidgoyal

Yeah this is a result of sandboxing in the viewer (the book contents are rendered in a sandboxed iframe). You can still inspect the HTML but not the CSS. Seems to be a limitation of devtools in webengine.

I was wrong, this was a bug in the viewer. Will be fixed in the next beta.

[JSWolf]

Originally Posted by kovidgoyal

No it cant be fixed, use viewport units instead. 100vh will do the trick.

Can't it be programed to do this when it imports the eBook? There will be a lot of eBook that will break because of this.

[kovidgoyal]

Originally Posted by JSWolf

Can't it be programed to do this when it imports the eBook? There will be a lot of eBook that will break because of this.

It does it automatically for full screen images that are based on the recommended full screen image markup. For the rest, there is no way to know when 100% refers to the viewport height or not.

[JSWolf]

Originally Posted by kovidgoyal

It does it automatically for full screen images that are based on the recommended full screen image markup. For the rest, there is no way to know when 100% refers to the viewport height or not.

100% should never be used other then images. It's very sloppy coding if 100% is not used for images.

[rashkae]

Originally Posted by kovidgoyal

It does it automatically for full screen images that are based on the recommended full screen image markup. For the rest, there is no way to know when 100% refers to the viewport height or not.

Umm, what *is* the recommended full screen image markup?

Ediy, erm, I guess you mean the SVG code that calibre uses with the full screen image option

Unfortunately, the Adobe RMSDK epub reader does not work with vh units,,, (it's being more strict on the CSS v2.1) It does seem to work fine if the book is loaded on Kobo as Kepub, or on Kindle as AZW3. A more universal solution would be to wrap the element in a 100vh div.

[kovidgoyal]

Originally Posted by rashkae

Umm, what *is* the recommended full screen image markup?

Ediy, erm, I guess you mean the SVG code that calibre uses with the full screen image option

Unfortunately, the Adobe RMSDK epub reader does not work with vh units,,, (it's being more strict on the CSS v2.1) It does seem to work fine if the book is loaded on Kobo as Kepub, or on Kindle as AZW3. A more universal solution would be to wrap the element in a 100vh div.

Or just use the recommended SVG markup that calibre uses, it works everywhere, including the new reader.

[theducks]

Warning [2 / 2]
OPS/package.opf (line: 194 column: 0)
The resource pointed to by this link does not exist. You should either fix, or remove the link.
Remove all references to OPS/cover.xml from the HTML and CSS in the book
< is this supposed to fix the bogus Guide section in the OPF?

----
OPF
<reference href="cover.xml" title="Cover Image" type="cover"/>

[JSWolf]

Originally Posted by kovidgoyal

Or just use the recommended SVG markup that calibre uses, it works everywhere, including the new reader.

So in order to read with full screen images that use 100% we have to edit them to work in the new Calibre viewer? Cannot the view be written to convert 100% to 100vh when it passes the code to the renderer?

[kovidgoyal]

@theducks: that should be flagged and fixed by another check

@JSWolf: That question has already been answered

[theducks]

Originally Posted by kovidgoyal

@theducks: that should be flagged and fixed by another check

@JSWolf: That question has already been answered

I will try another
It was flagged. I clicked fix. the OPF did not change (usually fix updates code view)

[theducks]

Nope
The guide still has the bogus entry that was flagged after I clicked remove all references (and then fix all after that did not work and I had re run the check)