Android renders blank pages in monospaced text colored with Prism

[rkwright]

When the WebGL-enabled EPUB (insert link here) is rendered on Android (Readium 0.22.2) the first page in chapter 2 is fine but subsequent text pages in that chapter are blank - only the buff background is rendered but no text. The text is being context-colored using the Prism.js library so perhaps that has something to do with it. There is a report of a Readium problem with Prism, but that was on readium.js, but perhaps that is misleading and the problem is in shared-js?

[rkwright]

Confirmed that the problem is related to prism.js. I created another EPUB that did not use prism and the text is rendered without problems. The second test file is here.

Note that this problem ONLY occurs on Android. Works fine on all other platforms tested.

[rkwright]

Here's another odd data point. If you go to page 1 of chapter 2 on Android the next page (reached by using the navigation buttons) is blank, i.e. only the buff-colored background is rendered. BUT if you go to page 1 of chapter 2 and then touch the screen and slide sideways (towards the right) the whole page slides over part way and the rendered text for page 2 can be seen. So it looks like prism is doing something funky with columns or divs and that is confusing the browser.

[sharak16]

Hi,
we want to integrate our code into SDK-Launcher ios in Swift.And objective
c written code is accessible in swift by creating Header-bridge.
My question is if we go ahead with swift then will be able to aceess
required functions or not .Please also suggest if any issue exist with
Swift .

Regards
Rakesh

On Thu, Feb 25, 2016 at 12:34 AM, Ric Wright notifications@github.com
wrote:

Here's another odd data point. If you go to page 1 of chapter 2 on Android
the next page (reached by using the navigation buttons) is blank, i.e. only
the buff-colored background is rendered. BUT if you go to page 1 of chapter
2 and then touch the screen and slide sideways (towards the right) the
whole page slides over part way and the rendered text for page 2 can be
seen. So it looks like prism is doing something funky with columns or divs
and that is confusing the browser.

—
Reply to this email directly or view it on GitHub
#226 (comment)
.

[rkwright]

@sharak16 Please do not insert random comments or questions in the middle of issues about other subjects. If you have questions, please open a new issue or send your question directly to the readium-dev mailing list or ask in Slack. See the Readium communication page here.