Skip to main content

Page is not found by the Iphone simulator when using ajax /Jquery Mobile-PhoneGap



I am creating a webapp for iPhone using jQuery Mobile and PhoneGap. Everything works fine in Safari for Mac and Chrome for Windows.





When I go to the iPhone Simulator the problems begin. Every button with a link to any page works fine except for one called "Article.html". The only way to open this page from the app is to turn off ajax by doing rel="external".





I have done everything in order to get it work. I have deleted the file and brought it back via add -> existing file with not luck. The content of the page "Article.html" is very simple and I don't think that is the problem because it doesn't even load the page. The loading symbol stays there for ever.







<!DOCTYPE html>

<html>

<head>

<!--jquery and css files are being loaded in another page-->

<title>This Date in History</title>

</head>

<body>

<div data-role="page" class="type-interior" id="Article" data-add-back-btn="true" data-dom-cache="false">

<div data-role="header" data-theme="a" data-position="fixed">

<h1></h1>

<a href="home1.html" data-icon="home" data-iconpos="notext" data-direction="reverse" class="ui-btn-right jqm-home" data-prefetch>Home</a>

</div><!-- /header -->

<div data-role="content">

<h4 id="title"></h4>

<h5 id="date"></h5>

<div style="text-align:center;">

<img id="img" style="max-height: 138px; max-width: 200px; overflow: hidden;" src=""/>

</div>

<p id="milestone_text"></p>



<a href="" id="more" data-role="button" data-icon="forward" rel="external">More about this event</a>

</div><!-- /content -->

<div data-role="footer" class="footer-docs" data-theme="a">

<center><h5> Archives</h5></center>

</div><!-- /footer -->

</div><!--Page ends here-->

</body>







ANY SUGGESTION WOULD BE APPRECIATED..


Comments

  1. <a href="home1.html" data-icon="home" data-iconpos="notext" data-direction="reverse" class="ui-btn-right jqm-home" data-prefetch>Home</a>


    please give the full path in href for home1.html

    ReplyDelete
  2. I found the answer by testing line by line.

    For some reason, this line was giving problems:

    <a href="" id="more" data-role="button" data-icon="forward" rel="external">More about this event</a>


    As you can see, href is blank. I just put a bogus url

    <a href="www.google.com" id="more" data-role="button" data-icon="forward" rel="external">More about this event</a>


    and that solved the problem.

    Weird but it works.

    Thanks for your help.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex