Note that there are some explanatory texts on larger screens.

plurals
  1. POiPad Mobile Safari HTML over Canvas Rendering Bug?
    primarykey
    data
    text
    <p>We're building an HTML 5 WebApp for the iPad using the Full-Screen WebApp view, one of our screens uses Google Maps and we're rendering custom controls and markers over it. I'm seeing a strange behavior and can't figure out what is happening or why, nor any information about it online.</p> <p>We have Google Maps filling the screen, with some HTML menus overlaying it that give the list of results (formatted) with various buttons and controls. It seems that more often than not the lists of results in our overlays render "empty". Inspecting in the web inspector while connected to the mac show the HTML is being rendered and inserted into the proper elements, and all events appear to be firing. The list and box are the right size and even react to touch events, but they just render with blank contents. </p> <p>In addition, sometimes the markers don't render, and that seems to be sporadic too. From what I can tell all the JavaScript is executing, all events are being triggered and handled, and network requests are being made and called back. There's just "something wrong" with the iPad rendering the HTML contents over the Google Maps.</p> <p>It works 100% of the time on desktop-based webkit browsers, but is 100% reproducible on the iPad with this strange behavior. (The iPad simulator has a similar behavior, but renders different parts wrong.)</p> <p>Based on what I've described, has anyone else seen or heard of this behavior, and does anyone have suggestions on what to do to debug/test/fix this? Appreciate it, Thanks.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload