I am working on RWD application which was developed using jQuery Mobile 1.3. We have decided to upgrade jQuery Mobile from version 1.3 to 1.4. Our concern is how well jQuery Mobile works in Microsoft Edge on Windows 10. The jQuery site does not mention anything about Microsoft Edge.
jQuery Mobile is developed around standards and common conventions, as is Microsoft Edge, Google Chrome, Mozilla Firefox, Safari, and other browsers. You should not run into any serious issue when using any of these modern browsers.
There are currently 271 open issues on GitHub for jQuery Mobile. A cursory search didn't reveal anything serious with Microsoft Edge. If you do happen to run into issues, please file them on Github, and share them here so that we can help you identify temporary work-arounds.
Internet Explorer versions 8 through 11 received an A in jQuery Mobile's Graded Browser Support. Considering the fact that Microsoft Edge has received thousands of bug fixes more than Internet Explorer 11, I would say it's safe to assume you should have a wonderful experience using jQuery Mobile along with Microsoft Edge.
Related
Reading about Ant Design I am getting confused about which library to use for mobile web development. There are two libraries, antd and antd-mobile. While it is clear that antd-mobile supports react-native on iOS and Android, it is unclear which one is best suited for plain mobile (non-native / SPA) web development.
Reading the antd introduction you see statements like "Ant Design which is specially created for internal desktop applications, ...", while reading the antd-mobile introduction you will see "Support Web / iOS / Android platform (Based on React Native)"
From this I would think that ant is somehow not very suitable for web development other than web based desktop (i.e. Elektron) apps.
But trying to build a normal web app with ant-mobile I couldn't get it to work. For example the Button is showing but DatePicker is not. Switching to ant everything seems to work fine.
Am I right to assume that for any non-native mobile development you need to use ant instead of ant-mobile?
If so, what is this supported "Web" platform that antd-mobile is mentioning?
From my experience:
Antd:
Intended for full browser web only (or electron) development, they are no mobile first design, some cases you have to tweak to make you web page look good in mobile.
Antd-mobile:
Antd mobile exports 2 versions of components, the web one (which uses DOM) and the react native version (uses View, Text etc...)
Web version: You can think it's like jQuery Mobile, Sencha Touch etc, it's intended to build pure mobile web page/application, the application that you are going to see in a mobile browser. example, go and open facebook.com, amazon.com with a mobile browser (they look really different then the desktop one).
React Native version: You will use this to build a Mobile App (a hybrid app) that sits in Google Play store/App Store, an app that needs to be installed.
Hope it helps.
If I made mistakes please let me know.
I am working with a client who maintains their public facing websites with Sharepoint. They are admittedly out of date and still using Sharepoint 2007 for the most part.
Example Page: http://www.kellerisd.net/Pages/default.aspx
With the recent release of iOS8 their website navigation is now broken in mobile safari and Chrome. I have seen numerous posts regarding the changes to the JS engine for browsers with iOS8 (http://9to5mac.com/2014/06/03/ios-8-webkit-changes-finally-allow-all-apps-to-have-the-same-performance-as-safari/)but have no other means to explain the loss of functionality overnight.
I am working with them to update to SP 2013 which should alleviate the issue but I am looking to repair their site to keep them functional until the migration is possible.
Don't expect SharePoint 2013 to help if they are using Windows Authentication... Windows Authentication is broken in iOS 8 Safari. (Works OK in Chrome though.)
In Design perspective, when displaying my html main file, in the palette view, the jquery mobile widgets does not show in Worklight studio 6.1.
It doesn't work with any version of jQueryMobile greater than 1.3.0. But It's ok with one application over 4 using version 1.3.0.
Here is the pop-up error message:
An internal error occurred during: "Discoverying jQuery Mobile widgets for /MyProject/apps/MyApp/common/MyApp.html".
java.lang.NullPointerException
How to solve the issue?
thanks
Please mention in the question the jQuery Mobile version you are using.
Worklight Studio's RPE (Rich Page Editor) will not work with jQuery Mobile 1.4, may fail with 1.3.2. It will work with 1.3.1.
You can continue using any version you'd like, but if using the RPE, take note of the above.
There is no workaround.
If your issues are different, then please, be more descriptive when asking questions.
"sometimes works, sometimes doesn't" is not helpful.
I'm building one project for Cross Platforms like ios, Android, Windows Mobile using Rhostudio.
I'm using jQueryMobile to get a nice look and feel.
All the stuffs going well untill, Windows Mobile comes to play.
As there is no support for jquerymobile in windows mobile, i'm not getting the proper Ui output for it.
Is their any other way we can get the same looks and feels for the windows mobile as like Android or ios ?
Thanks,
Ashis
According to http://jquerymobile.com/gbs/, there is A-grade support for jQM on Windows Mobile.
If you want a native look and feel, you can try a theme developed specifically to emulate the Windows look and feel, such as http://sgrebnov.github.com/jqmobile-metro-theme/samples/jqm-public-demo/index.html.
we developed one asp.net application , that is compatible for ie6 . now our client want to compatible of that application to ie8. so what i need to change in our application so that it can be compatible for ie8.
please let me know if any body know solution for this
Actually, IE6 is the one that has compatibility problems. IE8 complies to a large part of current web standards, and those are well documented. If you don't need to support IE6 anymore, just look up the standards and code against them.
Other than that, there is hardly any other way than test against the real thing. The recommended way of doing so (since you can't have multiple versions of IE on the same OS install) is to install one virtual machine per version. Microsoft offers free OS images (with time-limited activation) for this particular purpose.
If you need to support both IE6 and IE8, your best bet are conditional comments: see http://msdn.microsoft.com/en-us/library/ms537512%28VS.85%29.aspx for documentation. They allow you to show content for selected versions of IE only, and hide it for the rest (including non-IE browsers).
IE8 also adds a few security measures that could bite you, so be sure to test thoroughly.