Mickaël Menu

> To be honest, the more I think about it, the more I believe the easiest (less bug-prone) solution would be to shrink the actual viewport (out of process iframe,...

> This also means the number of visible columns won’t be constrained, and up to the app to manage. Would you mind explaining what does that entail?

How would an app hide the extra visible columns in this case? If it's displaying a blank view above them, that might be an issue for the page-turn animations (scrolls...

@akoehn Did you find a workaround? I have the same issue with JitPack but can't find a way to circumvent it in my `build.gradle` https://jitpack.io/com/github/readium/r2-navigator-kotlin/upgrade-gradle-2.0.0-g8d72a08-22/build.log ``` 35. ------------------------------------------------------------ 36. Gradle...

I "solved" it by disabling JitCI altogether: Settings > Stop building button at the bottom. With this the JitPack build is successful. We're using GitHub actions for our CI and...

@ettore Yes definitely, I added this as a comment to "How to display page numbers?"

When choosing a specific font, as a rule of thumb we should fall back on one of the known font stacks, e.g. ```css --USER__fontFamily: "SF Mono" var(--RS__monospaceTf); ```

@JayPanoz > We discussed about this in private so for the benefit of everyone, here is a recap on the concept of type scale, its purpose and use cases. Thanks...

An issue related to Readium CSS, but to be fixed on the native side: Some books won't change their font size unless publisher's styles are disabled (note to self: 9782081418011.epub)....

> Each navigator should be able to claim which publication it supports, whatever profile it conforms to, if any. I like this idea, testing a queue of navigator implementations until...