When I try to visit jquerymobile.com/test page with Nokia 1680 c-2 (which is a Series 40 5th Edition phone) it at first loads the bare html page and then says it is processing the page. Then all content disappears and a white page is displayed.
When i test with http://jquerymobile.com/demos/1.1.0/ page loads normally.
Series 40 has a proxy browser if I am not mistaken, so that might cause the problem.
What version of jQuery core are you using?
Can you open those two test pages on your device and post the true/false values you get to see?
1.1.1 + core 1.7.2: http://jsbin.com/uwaxaj/41
latest + core 1.8.2: http://jsbin.com/uwaxaj/42
Related issue: #5005
I forget to mention that Symbian Series 40 should get C-grade experience (no JS, basic HTML). Still an issue if there is only a blank page.
On our project we are currently using jquery core v1.7.1. which causes the same problem with jquerymobile.com/test page which is using v1.8.2.
When I open the test pages you asked:
http://jsbin.com/uwaxaj/41: Displays the page and the values are not set.
http://jsbin.com/uwaxaj/42: Displays the page for a short period of time and I can see that the values are not set then the content disappears.
Yes C-grade with basic HTML would be fine but apparently something prevents any content to be displayed at all.
We don't have a series 40 device to test so could you please try this adjusted version of the test?
http://jsbin.com/uwaxaj/43 does not have this problem. It displays basic HTML just fine.
What are the test results (true/false)? http://jsbin.com/uwaxaj/53
Test values are not set in http://jsbin.com/uwaxaj/53.
I'm asking to understand, Isn't this expected in C-grade with no js ?
Part of the JQM JS are the support tests. Based on the results of some of those tests we define A, B or C-grade. The first thing we do on init is checking if it is C-grade and if so we don't continue with enhancing the page. This is what we mean by "no JS".
It looks like your Series 40 device fails to run the support tests. This is most probably because it has a proxy browser, which means the JS is not executed on the device but on a proxy server.
You reported a white page so I think the problem is that class ui-mobile-rendering is not removed. That class sets everything to visibility: hidden; and is removed when we are done initializing the page. There is a fallback that removes the class anyway after 5 secs, but it looks like this is not working. Strange thing is that we already did it that way in 1.1.0 and you don't have the problem in that version. I am looking into it.
Based on @arschmitz his comment I changed the test page to use an alert.
@Hamdiakoguz - Can you test those pages and let me know what the alert shows and if you get a white page or not? Thanks!
Test page latest code: http://goo.gl/iWt1c
Test page latest code with possible fix: http://goo.gl/v2dkK
I can not see the alert and get a white page in both links.
Is there anything I can do to help for this issue ?
I did some more testing hoping it will help and I realized that the device I'm testing (Nokia 1680 c-2) is a Series 40 5th Edition phone. And this issue exists only on Series 40 5th Edition.
I tested this issue with following emulators provided by Nokia:
and this problem does not exist on these emulators.
But with Nokia 6267 emulator (Series 40 5th Edition) I can reproduce the same issue with my device.
Thanks a lot for the additional info and your offer to help.
We just discussed this, and other Symbian issues, during our team meeting. We have to do more test to find out what is causing this. That is something I am going to look into with @gabrielschulhof next week. Would be great if you could help us with running the tests we come up with. Stay tuned!
We are really looking forward for a fix for this issue. Meanwhile we decided to use jqm 1.1.1 + core 1.7.2 for all nokia phones since it is hard to match the user agent of Series 40 phones.
Using this ticket for all Series 40 and Symbian^3 loading and enhancement issues (I changed the title).
Closed tickets #3203 #4454 and #5005
Results of earlier investigation (copy of my comment here #5005 (comment) ):
We support Symbian^3 OS as B-grade. Older versions of this OS use the same Nokia/Symbian Browser 7.x which supports media queries (Nokia E52 is running Series 60 3rd Edition with Nokia browser 7.2).
The test showed that the Nokia E52 is even A-grade instead of B-grade.
We can fix this by making a change in this line:
ua.indexOf( "Series60/5" ) > -1 should become ua.indexOf( "Series60" ) > -1 so it also includes "Series60/3".
If there are still too many issues with Ajax disabled we have to look into making sure the older Symbian versions become C-grade.
Nokia series 40 is a different story. Its browser only supports CSS 2.1 so it shouldn't pass the media query test and get a C-grade experience.
We recently got a bug report from a customer stating that browser crashes while loading page. The problem seems to be the same stated in issue #4454.
I was able to reproduce the issue with emulators of Nokia 5230 and C6-00 which are S60 5th Edition devices.
Please let me know if I can be of any further help.