Dygraphs: graph is clipping out of the diagramm - android

I'm using dygraphs to print a range selector diagramm in android. My problem is that the graph is going over the end of the diagramm div. This can be seen in the following picture.
On icanuse and different websites it says that android supported clip-path until 3.0. Since then clip-path isn't supported (I even tested it on LG G3 with android 5).
My question: Is there any workaround to prevent my graphs from clipping? Or do you have some ideas, which I could test?
Related Links:
https://code.google.com/p/dygraphs/issues/detail?id=200
http://dygraphs.com/tests/range-selector.html
https://github.com/danvk/dygraphs/commit/971870e5232350812bf91dc7b555332a8993efda

Related

How to remove tap highlight color in Android 4.4.2/chrome

I've read many posts and answers with regard to the question above, but as yet, I haven't come up with an answer that works.
This is my current code:
* {
-webkit-tap-highlight-color:rgba(0,0,0,0);
outline:none;
}
I've also used 'transparent' in place of rgba.
As I pointed out - I'm using Android 4.4.2 on a HTC one, now using Chrome 42.
Nothing I have done has resulted in removing the green overlay. I came across a bug report that implied that the webkit engine is no longer used on this Andriod/Chrome version (probably true as it was on the official site), but if that is the case, how do I remove it?
I can't believe I'm the only one with this issue.
This CSS tweak worked perfectly for me using a Galaxy Tab S running 5.0.2. and Moto G phone running 5.1. You might have a conflict in your CSS. Hopefully by you got it worked out.
Thanks for the post John!

Android stock browser on Xperia Z does not render html correctly

I have an HTML page which is displayed correctly in all devices and all browser except the stock Android browser in Xperia Z.
On this particular device running Android 4.2.2, I am using jQuery v1.7.2, and using $('div').slideUp and $('div').slideDown methods only, and it results in text distortion (it is in English, so I suppose it is not related to any specific font), the text appears as horizontal lines as they would appear for a fraction of a second while sliding up/ down.
I have tried turning the debug mode ON by about:debug in the stock browser, and the javascript console shows no error/ warning messages.
I tried changing the user agent string to iPhone, and to my surprise, the text is rendered as expected.
I have searched for similar issue, and came across Android stock browser crashing, it points to jQuery bug where slideUp/ slideDown have problems in Android stock browser (please note that jQuery and Android versions are different in the reported bug).
My questions are:
Is this a known issue?
Has anyone faced similar problem before?
Is there a workaround to resolve it?
I'd really appreciate if anyone could point me in the right direction.

Camera preview shows unwanted tiles only on Android 4.2.2 (S4, full HD screen)

My app runs with many devices but 2 users have send me simular images as below.
As far as I know the behaviour is only seen on Android 4.2.2 (Samsung S4).
On the full HD screen there seem to be 3 compressed tiles of 160x600 pixels.
I have tried an AVD with full HD screen but that fails to start.
On 4.03 devices I don't see this. I don't use tiles.
Does anybody have a hint what or where this goes wrong ?
This looks like a possible bug in the Android platform on Samsung's S4 devices with that particular Android version. My experience tells me that it's a very real possibility. It could also be that you do something wrong in your app that only causes actual problems on that version (and maybe even only on that device), but there is no indication of that from what you tell. Android 4.2.2 should be backwards compatible with 4.0.3, so in general it should work on the later version too, of course.
I would advice you (or anyone in the same situation) to try it out on other devices with the same Android version if possible. Also, double check that you're not violating anything in the Android API documentation.
Please add more info about what you're doing and how if you need more detailed answers. I guess you've probably found a solution or workaround by now, but still adding my answer here.

legend not working in afreechart in tablet android

I am using Afreechart to create charts for my android app. In emulator legend is visible but in android tablet legend is not showing up. Previously it was working properly but when i add some other activities to my app,its not working. am using afreechart-0.0.4.jar.my minSdkversion 3 and target is 15.
I found the solution for my question..
The thing that pointed me in the right direction was the fact that the graphs would behave perfectly on the emulator, independently from what version of Android the emulator was running. That made me think that maybe the hardware acceleration (which if I am not mistaken was introduced with HoneyComb) had something to do with this. A little more googling showed me that other graphics libraries had similar issues on ICS and JellyBean, so I tried switching off the hardware acceleration for the chart view:
chartView.setLayerType(View.LAYER_TYPE_SOFTWARE, null);
Now the graphs and the legends show up just as expected on any device. Hope it helps someone....

Why is this android device enlarging text?

The website is tavistockrestaurants.com. We are trying to make this design work well in popular mobile devices. A particular android device seems to be enlarging the text, and I am unsure why. This causes the "contact" link in the top to wrap, and causes unecessary line breaks throughout our website. Notice the form is getting pushed below the images in this screenshot? It's supposed to have white space on the bottom!
We do have -webkit-text-size-adjust: none in place for all elements (using asterisk *). Is there an android equivelant? Has anyone experienced this on any android devices?
This behavior does not occur on all android devices. We have only seen this on Android 4.x, but I cannot reproduce it with my android 4.0 emulator.
What it currently looks like:
What it should look like:
(I do not have the specific device model used in the screen cap)
In CSS, pixels are not pixels.
Or rather, 1 CSS pixel does not always map to 1 hardware pixel. On certain high-DPI Android devices, one CSS pixel can be 1.5 or 2 hardware pixels. The Opera guys have a good overview on the topic.
Samuels answer is correct.
There is a workaround though. You can target specific devices and change the styles for that device specifically using classes or stylesheets. If you are using PHP you should be able to parse the "User-Agent" and determine which device the client is using and add a class to the body tag (and use that class to target that specific device in your CSS).
There are also services that will allow you to send users to a different version of the site depending on the device they are using. Here is a site that does the work for you.
There may also be device specific CSS being generated on loading the page. Using a CSS reset may also help your site be more cross-browser compatible.

Categories

Resources