Response title
This is preview!
How to ask for jQuery Mobile help
in jQuery Mobile
•
9 years ago
The Answer is: "big yellow box, top of the page".
Unfortunately, this is not a forum of mind-readers. If you were referred to this post, it's because your post contained insufficient information for us to give you help.
----
- Start a separate thread for each problem. Do not "piggy back" on another thread, even if it seems to be a similar problem. Often, the problems are *not* the same, and it can get very confusing when different problems are mixed in the same thread.
----
----
- If you are using an unsupported combinations of versions, please try first with a supported combination before posting, and use a supported combination in your example:
jQuery Mobile 1.0 requires jQuery 1.6.4
jQuery Mobile 1.1.1 can use jQuery 1.6.4 through 1.7.2
jQuery Mobile 1.2.1 can use jQuery 1.7 through 1.8.3
jQuery Mobile 1.3.1 can use jQuery 1.7 through 1.9.1
Note: If you are not using one of the above versions of JQM, check the documentation for the version you are using for the jQuery requirement. It's generally been bumped-up for the maintainence releases. For example JQM 1.1.0 can only use jQuery 1.6.4 through 1.7.1.
Please realize that alpha and beta releases are not stable, and meant for testing only. You won't get much love here asking for help for non-current alpha or beta releases (we still get questions about 1.0a1...). They are EXPECTED to have flaws. Upgrade to a stable release.
jQuery Mobile 1.3.1 can use jQuery 1.7 through 1.9.1
Note: If you are not using one of the above versions of JQM, check the documentation for the version you are using for the jQuery requirement. It's generally been bumped-up for the maintainence releases. For example JQM 1.1.0 can only use jQuery 1.6.4 through 1.7.1.
Please realize that alpha and beta releases are not stable, and meant for testing only. You won't get much love here asking for help for non-current alpha or beta releases (we still get questions about 1.0a1...). They are EXPECTED to have flaws. Upgrade to a stable release.
There is conflicting information put out by the jQuery team. It should be considered incorrect. The above is the official position of the jQuery Mobile team as announced in their blogs, and as appears on the very first page of the documentation for any JQM version.
----
Check the compatibility matrix if you are having trouble on particular hardware or a particular browser:
http://jquerymobile.com/gbs/
Some browsers and not fully-supported by jQuery Mobile, and you will have to decide if you are using these browsers if jQuery Mobile is an appropriate solution.
----
Check the compatibility matrix if you are having trouble on particular hardware or a particular browser:
http://jquerymobile.com/gbs/
Some browsers and not fully-supported by jQuery Mobile, and you will have to decide if you are using these browsers if jQuery Mobile is an appropriate solution.
----
- Please stay on-topic. This forum is for discussion related to using jQuery Mobile. There are
other forums on this site for topics related more generally to jQuery, as well as more specific
jQuery-related topics. There are many other places on the Internet where you can discuss
more general Javascript-related questions. Please help keep this forum relevant and on-topic
by restricting topics to those specifically relevant to jQuery Mobile.
---
- Do not expect others to work-out concrete solutions for you. Sometimes, others will provide an example or complete solution to a problem - usually a generalized one that will maximize the benefit to all. Other times, referral to reference or learning resources is more appropriate. Please do not expect others to do your job for you here. If you need help completing a project, there are many outsourcing communities on the Internet where you may hire-out help on your project.
Everyone providing answers here is a volunteer. Please do not abuse their generosity. You will likely find that if you ask repeatedly for others to solve every little problem for you, you will be gently (or not so) guided to reference and learning resources. Eventually, it's likely your questions will simply be ignored.
---
- Please stay on-topic. This forum is for discussion related to using jQuery Mobile. There are
other forums on this site for topics related more generally to jQuery, as well as more specific
jQuery-related topics. There are many other places on the Internet where you can discuss
more general Javascript-related questions. Please help keep this forum relevant and on-topic
by restricting topics to those specifically relevant to jQuery Mobile.
---
- Do not expect others to work-out concrete solutions for you. Sometimes, others will provide an example or complete solution to a problem - usually a generalized one that will maximize the benefit to all. Other times, referral to reference or learning resources is more appropriate. Please do not expect others to do your job for you here. If you need help completing a project, there are many outsourcing communities on the Internet where you may hire-out help on your project.
Everyone providing answers here is a volunteer. Please do not abuse their generosity. You will likely find that if you ask repeatedly for others to solve every little problem for you, you will be gently (or not so) guided to reference and learning resources. Eventually, it's likely your questions will simply be ignored.
---
- Give us a complete example. One way of doing this is to link to a jsfiddle:
http://jsfiddle.net
If you have a website with an example, please provide the URL. Let us know if you update the website with a fix, so that you don't confuse later readers. (It's better to provide a separate URL for the demonstration.)
If you have a website with an example, please provide the URL. Let us know if you update the website with a fix, so that you don't confuse later readers. (It's better to provide a separate URL for the demonstration.)
Otherwise, please provide everything - not just a snippet from the code that you think is the problem. If you knew where the problem was, you wouldn't be asking. Give us everything. It's almost certainly somewhere where you haven't been looking.
----
- Condense your example. Remove irrelevant parts that do not relate to the problem at hand. Be respectful of the time that people put into answering your question or solving your problem. It is difficult to read long examples and to identify the relevant parts. Don't make us read through a form with 100 controls in order to diagnose the one that is acting-up. There is a good chance that - in the process of condensing your example - you will discover the solution.
----
- If you are using IDs in your HTML and JS, please correct this before posting your question.
It is not safe to use IDs in jQuery Mobile except under very carefully considered circumstances.
Use classes instead, and then limit the scope of your queries to a particular page.
The problem is that HTML disallows having multiple elements with the same ID in a document. JQM loads multiple "pages" into a document. (For example, when doing a page transition, both the outgoing and incoming pages are in the document at the same time.)
Browsers do their best to punt when there are multiple elements with the same ID in the document. But they can't read the user's or developer's mind. So, when you write some code to do something with an element that has an ID, and there are more than one element with that ID, it may or may not use the element you were intending.
Personally, I will not answer questions when IDs have been used in the example. It is a waste of time to try to debug such examples, as the problem almost always will turn out to be related to the misuse of IDs. If you want to "optimize" by converting some classes to IDs after you get your code working, do it on your own time, and don't us to help you.
- If you are using IDs in your HTML and JS, please correct this before posting your question.
It is not safe to use IDs in jQuery Mobile except under very carefully considered circumstances.
Use classes instead, and then limit the scope of your queries to a particular page.
The problem is that HTML disallows having multiple elements with the same ID in a document. JQM loads multiple "pages" into a document. (For example, when doing a page transition, both the outgoing and incoming pages are in the document at the same time.)
Browsers do their best to punt when there are multiple elements with the same ID in the document. But they can't read the user's or developer's mind. So, when you write some code to do something with an element that has an ID, and there are more than one element with that ID, it may or may not use the element you were intending.
Personally, I will not answer questions when IDs have been used in the example. It is a waste of time to try to debug such examples, as the problem almost always will turn out to be related to the misuse of IDs. If you want to "optimize" by converting some classes to IDs after you get your code working, do it on your own time, and don't us to help you.
- If you are using $(document).ready() in your code, read this first before posting, and correct your code:
Big yellow box, top of the page.
There are hundreds of posts, and hundreds of the same answer on this forum, about this topic. Please don't add yet another.
----
- Before you post, read this: http://jquerymobile.com/demos/1.2/docs/pages/index.html
Pretty-much all of it, but especially:
If you haven't read this first, you are wasting your own time and ours. You have no hope of using jQuery Mobile effectively if you do not understand it's handling of linking, navigation, and scripting, and it's management of the document.
----
If you are loading different scripts in the <head> section of different pages, read this again, because that won't work:
----
- Learn jQuery. You need to know at least the basics of jQuery - particularly selectors - before you try to use jQuery Mobile. I highly recommend the book "jQuery Pocket Reference" (O'Reilly, David Flanagan). It's inexpensive, available in electronic form, and provides "just enough" jQuery for jQuery Mobile developers. I find it particularly good on selectors.
----
- Understand that the use of jQuery UI widgets in jQuery Mobile projects is unsupported.
jQuery Mobile was not designed to be compatible with jQuery UI. This was a concious decision. Limitations of jQuery UI were one of the reasons for the creation of jQuery Mobile.
Some developers have been successful making some jQuery UI widgets work within the context of jQuery Mobile. It may take no, little, or extensive effort to get any particular jQuery UI widget to work with jQuery Mobile.
---
- Tell us what you are really trying to accomplish. When we are learning to use a new tool, often our internal model of how that tool works is incorrect. We have some idea of how to accomplish some goal, which will turn out to be incorrect, and then we get stuck on some particular fine point. But it may be that it was just not the best way to go about it. If you are finding that some obscure feature doesn't work the way you expect or is actually a non-feature, back-up and tell us what you are really trying to do. Many posts here involve some convoluted work-around for some other problem the poster never told us about.
----
- Please be patient. Users of this forum are everywhere on the globe, and do not check-in here 24/7. It's also a fairly small community. Do not expect an answer within minutes, or even hours. Give your post a couple of days, and please don't post the same question repeatedly. That won't get it answered any faster.
----
- Post on the correct forum. In most cases, that would be this one - jQuery Mobile. The forum "Developing jQuery Mobile" is for discussion about the development of jQuery Mobile itself, not for discussions about using jQuery Mobile to develop your own website or app. It is appropriate, though, if you would like to suggest or discuss a new feature, and have input into the future development of jQuery Mobile.
----
- Post in a language in which you can express your thoughts clearly. While this forum is conducted mainly in English, it has global reach, and there are many here who understand many different languages. While it is helpful if you can write well in English, it is more important to express your thoughts clearly. If you have any doubt, please post first in the language you feel most comfortable expressing yourself in, and then, as a convenience to the majority, you might provide an English translation, either done by yourself or by machine translation.
- Post in a language in which you can express your thoughts clearly. While this forum is conducted mainly in English, it has global reach, and there are many here who understand many different languages. While it is helpful if you can write well in English, it is more important to express your thoughts clearly. If you have any doubt, please post first in the language you feel most comfortable expressing yourself in, and then, as a convenience to the majority, you might provide an English translation, either done by yourself or by machine translation.
----
- If you've read through this, and performed all of the steps suggested, you have probably already solved your problem. Congratulations! Otherwise, you are now prepared to ask a question that will have an excellent chance of being answered quickly and correctly.
6
