search

Letractively / flot

Automatically exported from code.google.com/p/flot
MIT License
0 stars 0 forks source link

minor issue running in iOS Safari & UIWebView component #625

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
jQuery flot runs perfectly in safari on all platforms--and even plays nice with 
JQuery Mobile--on a desktop browser, but there is a minor issue when displaying 
graphs in iOS Safari and in an embedded UIWebview in an Objective C application 
that hosts the RIA.

I have a JQuery Mobile/HTML5 RIA project that has several flot graphs. Its 
intended for internal use on company iPads. The graphs work perfectly in any 
browser that supports HTML5 on desktop--and runs nicely on the browsers on 
Android tablets that we tested, but not on iOS devices--which the majority of 
our user base will be using. We will have very few using a version on Android 
Tablets but that is expected to expand. Both Apps will be using the same 
embedded RIA hosted on an Extranet server.

This problem seems to be limited to iOS Safari, and we are stuck with it as the 
application makes use of the UIWebview (webkit) component in a larger App.

The graphs do display, but the data-labels do not display correctly. Understand 
that the application is hosted on a webserver with the correct headers and that 
all else is run pretty much "by the book".

I can't debug much in the embedded host or even much in the mobile safari, and 
although I have great debugging tools for desktop client side--the issue 
doesn't exist in that environ.

Original issue reported on code.google.com by rshermanfl@gmail.com on 4 Nov 2011 at 3:11

Attachments:

GoogleCodeExporter commented 9 years ago 
I also have this problem but it appears only on iOS5.
I'm developing an app using jQueryMobile, Flot and wrapped with Phonegap.
Flot works fine on all iOS except iOS5.
I've attached an image of my problem!

Original comment by aki.ilu...@gmail.com on 8 Dec 2011 at 3:04

Attachments:

GoogleCodeExporter commented 9 years ago 
Is there a fix for this or has anyone figured out a workaround?

Original comment by RodrigoM...@gmail.com on 3 Jan 2012 at 9:09

GoogleCodeExporter commented 9 years ago

Original comment by dnsch...@gmail.com on 8 May 2012 at 7:41