Select2 does indicate its support for desktop browser version to be: IE8+, Chrome 8+, Firefox 10+, Safari 3+, Opera 10.6+
However, I cannot find anything regarding Mobile & Tablet support.
Is there any official statement I have missed?
Simply quoting from the same question I asked on the Github project
Select2 3.5.x should work well in all of the latest mobile devices.
It's used in many large websites and we've appeared to have ironed out
many of the old issues.
Select2 4.0.0 has not yet been released, but Beta 3 has been tested to
work with Android devices without any real issues. We don't have any
iOS devices to test on, but more than likely they work well on iOS as
well.
Quoting from same question, for version 4.0.3 ( current stable release )
Yes, this version is more stable. Tested on Android 6.0.1 and iPhone 6.
Related
The app is a Xamarin.Forms PCL app running version 2.3.4.231 after an upgrade from Xamarin.Forms v2.2.0.31. The app works just fine on my iPhone 6s running version 10.2.1, however the app crashes on the ListView page when running on my iPad Mini 2 running version 7.1.2. More importantly, neither Xamarin Insights or HockeyApp catches the error.
The app worked just fine with the old version of Xamarin.Forms when both Windows 10 and my Mac Book was running this version of the software. https://releases.xamarin.com/stable-release-cycle-6-service-release-4/
I just upgraded both Windows 10 and my Mac Book to this version of the software. https://developer.xamarin.com/releases/vs/xamarin.vs_4/xamarin.vs_4.4/
I'm now getting this error in the iOS properties section.
It might be important to note that I'm using this in the ListView page. Both packages are installed in the Portable and iOS Projects.
Xamarin.FFImageLoading v2.0.5
Xamarin.FFImageLoading.Forms v2.0.5
I'm just assuming this has something to do with ListView, but I have no idea other than this is where the app is crashing. Any help is much appreciated. Let me know if you need to see some code.
iOS 7 and 8 are no longer supported according to this link. https://github.com/xamarin/Xamarin.Forms/pull/630
If you are using the latest version of Xamarin.Forms 2.3.4 or newer, versions older than iOS 7 are no longer supported. You can see the official documentation here, under "Other Changes"
https://releases.xamarin.com/stable-release-xamarin-forms-2-3-4-224/
It does appear iOS 8 and newer are still supported however.
IDE: Eclipse
Desktop OS: Mac
Device : Android 4.0.4
Hi,
last week i sent a new android build to the server, and it updated the jar files i have on my Mac, then i installed the app on LG android 4.0.4 device that i tested before, and was surprised to find some pages display all black.
After investigating a little, i discovered that when i use tabs on any form the form will be displayed black only on android, no problem on simulator nor IOS iPhone 6S.
I looked at the forum and i found similar problem happened a year ago , and the solution was to use "android.asyncPaint=false" temporarily . now this removed the black, but messed all the rendering while navigating between tabs.
So my question is why this happened now? the past three months i was developing and deploying on android without any problem. Did the newest update corrupt something?
Thanks
Sam
Using the android.asyncPaint flag is discouraged as it will fallback into a relatively slow compatibility mode. We are currently investigating some regressions in some rendering optimizations that affect some devices and are in the process of deploying a solution for that.
Please let us know if the issues persist.
Can the applications developed for desktop browsers using ExtJS 4.2.1 will work fine in the mobile/touch devices with out any resolution issues. Please suggest do we need to do any changes for running the application in mobile browsers.
Extjs 4 and below is not optimised for use on mobile devices, so I doubt this is much you can do to overcome your resolution issues.
Extjs 5 is targeted for both desktop and high end tablet devices such as iPad and Galaxy Tab.
Sencha Touch offers the best support for the most number of mobile devices whilst still working on HTML5 supported desktop browsers.
Note - they have announced they are merging ExtJs and Touch. More details to follow at their upcoming SenchaCon event.
ExtJS 4 can work OK on tablet devices.
For mobile browsers or hybrid mobile apps consider work in Sencha Touch.
So I have a website and I mean to make 2 version of it, the desktop version (with full features) and mobile version (simplification of the desktop version). I'm using media query in CSS to adjust the style. It works well in native browser. When I open my web using native browser it will show the mobile version style. But somehow when I open my web using Opera Mini, it keeps showing the desktop version instead.
I have googled it and didn't found any clue. Any idea how does it happen?
Thanks!
I finally found what's wrong with it. Turns out I was stupidly using #media screen only and Opera Mini doesn't seem handle it well. I've googled it for hours. Someone said actually Opera Mini supports #media screen but other people said that the right media property for Opera Mini is #media handheld. Well, I tried to play safe by simply changing it to #media all. And it works!
There are a number of reasons why Opera Mini is showing the desktop version of the site. The most likely is that your website is not properly detecting Opera Mini as a mobile site and is not returning the correct content. If you're using some plugin or other piece of software that is automatically handling the routing of desktop vs. mobile for you, that might be the culprit. Also, it's possible that this is happening by design, because of how Opera Mini works.
Opera Mini runs web content through Opera's own proxy servers and attempts to 'optimize' the content before delivering it to the user. That is, content is rendered first on the proxy server and then delivered to the device. This of course creates all kinds of complications for someone who is trying to deliver a consistent mobile web experience to their users. Fortunately, Opera provides a development guide to help give you a better sense of what's going on and how to cope with it.
Opera Mini is, in my experience, a very difficult browser to work with. At the Wikimedia Foundation, we server a very limited Wikipedia (and sibling project) experience when we detect someone's using Opera Mini.
You should definitely read through the opera mini development guide and make sure that any device detection you're doing is correctly recognizing opera mini as a mobile browser. If you're just using media queries, you may either want to reconsider a more robust approach to mobile detection, or adjust your design accordingly to work for opera mini. Good luck!
Hi I am developing a mobile version of my WordPress site using WP Touch Pro, are there any good emulators so I can see the results on different platforms?
yup:
http://www.electricplum.com/dlsim.html
will show you ipad and iphone simulations.
If you're on a Mac, you can use the free iOS SDK which includes an iOS Simulator. Android also has one; it takes a few extra steps to setup, but it's also free and cross-platform. Blackberry has one as well, pretty much all platforms do. I develop mobile sites all the time and these are the tools I use, and they're invaluable.
This has a few different emulations available: http://mobiletest.me/
This is a great extension for chrome , User-Agent Switcher for Chrome