New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to close dialog within a UIWebView on iOS #2190

Closed
josh-h opened this Issue Aug 2, 2011 · 35 comments

Comments

Projects
None yet
7 participants
@josh-h

josh-h commented Aug 2, 2011

The 'X' button, and 'data-rel="back"' links in a dialog are ignored when running in an embedded browser on iOS devices. When running from Safari the close button works fine, but when running from a UIWebView the X button is ignored.

Using the latest build "92ceadf138379eed3583d58994886b94fcf227ea Date: Tue Aug 2 07:25:13 2011 -0700" I am able to reproduce this with a clean test. The offending html is:

<!DOCTYPE html> 
<html> 
    <head>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1"> 
    <title>jQuery Mobile Framework - Dialog Example</title> 
    <link href="http://code.jquery.com/mobile/latest/jquery.mobile.css" rel="stylesheet" type="text/css" />
    <script src="http://code.jquery.com/jquery-1.6.2.js"></script>
    <script src="http://code.jquery.com/mobile/latest/jquery.mobile.js"></script>
    </head> 
<body> 

<div data-role="page">
        <div data-role="header">
            <h1>iOS Dialog Test</h1>
        </div>

        <div data-role="content">
            <a href="#dialog-inline" data-role="button" data-rel="dialog" data-close-btn-text="foobar">open inline dialog</a>
        </div>
</div>

<div data-role="page" id="dialog-inline">
    <div data-role="header">
        <h1>Dialog inline</h1>
    </div>

    <div data-role="content">
        <p>This is a dialog. When running in an iOS UIWebView the Close button does nothing.</p>
        <a href="dialog.html" data-role="button">Page Navigation</a>
        <a href="#" data-role="button" data-rel="back">close</a> <!-- Link is broken -->
    </div>
</div>

</body>
</html>

You can download an Xcode project (tested in Xcode 3.2 and 4.1), the project creates a UIWebView and loads the above html. http://dl.dropbox.com/u/47403/DialogTest.zip

@toddparker

This comment has been minimized.

Show comment
Hide comment
@toddparker

toddparker Aug 2, 2011

Contributor

This button just moves you back in the history stack so can you do some digging to see where it's going wrong? Is the click/tap event even being fired? If so, do buttons in general work with a history -1 setup? Etc.

Contributor

toddparker commented Aug 2, 2011

This button just moves you back in the history stack so can you do some digging to see where it's going wrong? Is the click/tap event even being fired? If so, do buttons in general work with a history -1 setup? Etc.

@josh-h

This comment has been minimized.

Show comment
Hide comment
@josh-h

josh-h Aug 2, 2011

The events appear to be propagated, my conclusion is based on seeing the icon highlights during taps.

It appears that JQM is doing something that interferes with how a UIWebView handles history. For example, history.length always returns 1. If I follow a link with 'rel="external"' then I see that the history.length is incremented.

Creating links that call 'history.back()' did not move the page back either.

I now see that the issue is history tracking within a UIWebView, and independent of dialogs.

josh-h commented Aug 2, 2011

The events appear to be propagated, my conclusion is based on seeing the icon highlights during taps.

It appears that JQM is doing something that interferes with how a UIWebView handles history. For example, history.length always returns 1. If I follow a link with 'rel="external"' then I see that the history.length is incremented.

Creating links that call 'history.back()' did not move the page back either.

I now see that the issue is history tracking within a UIWebView, and independent of dialogs.

@toddparker

This comment has been minimized.

Show comment
Hide comment
@toddparker

toddparker Aug 7, 2011

Contributor

Alright. I just updated the title to be clearer. We'll take a look when we can but if you find a fix or more details, please let us know.

Contributor

toddparker commented Aug 7, 2011

Alright. I just updated the title to be clearer. We'll take a look when we can but if you find a fix or more details, please let us know.

@ghost ghost assigned johnbender Aug 7, 2011

@josh-h

This comment has been minimized.

Show comment
Hide comment
@josh-h

josh-h Aug 11, 2011

I found a workaround to this problem. Simply create a UIWebView instance, when the view loads direct it to a non JQuery Mobile page that immediately redirects to a JQM page. At this point the browser history works correctly.

I suspect the root cause might be related to how JQM overrides page navigations. If UIWebView never receives acknowledgement that the first page loaded successfully then the UIWebView may not completely initialize it's history tracking.

josh-h commented Aug 11, 2011

I found a workaround to this problem. Simply create a UIWebView instance, when the view loads direct it to a non JQuery Mobile page that immediately redirects to a JQM page. At this point the browser history works correctly.

I suspect the root cause might be related to how JQM overrides page navigations. If UIWebView never receives acknowledgement that the first page loaded successfully then the UIWebView may not completely initialize it's history tracking.

@Zero3

This comment has been minimized.

Show comment
Hide comment
@Zero3

Zero3 Oct 14, 2011

I'm suffering from what looks to be the same bug, but on Android. The result is worse though: My PhoneGap app silently closes as soon as a dialog X button or a data-rel="back" button in a dialog is pressed.

One guess is that, for some reason, JQM doesn't properly go a page back, but the back call is sent all the way back to the webview which closes itself because JQM was the first and only page in history. Or something like that.

I've tested with b1, b2 and rc1. All same. Works in Google Chrome though. I can try to put together a test case if wanted.

Zero3 commented Oct 14, 2011

I'm suffering from what looks to be the same bug, but on Android. The result is worse though: My PhoneGap app silently closes as soon as a dialog X button or a data-rel="back" button in a dialog is pressed.

One guess is that, for some reason, JQM doesn't properly go a page back, but the back call is sent all the way back to the webview which closes itself because JQM was the first and only page in history. Or something like that.

I've tested with b1, b2 and rc1. All same. Works in Google Chrome though. I can try to put together a test case if wanted.

@toddparker

This comment has been minimized.

Show comment
Hide comment
@toddparker

toddparker Oct 15, 2011

Contributor

Have you guys tried disabling the pushState global option to see if that helps? The behavior can be a bit flaky on some browers/situations and since you don't have a URL bar, it's better to shut this feature off, might help.
http://jquerymobile.com/test/docs/api/globalconfig.html

Contributor

toddparker commented Oct 15, 2011

Have you guys tried disabling the pushState global option to see if that helps? The behavior can be a bit flaky on some browers/situations and since you don't have a URL bar, it's better to shut this feature off, might help.
http://jquerymobile.com/test/docs/api/globalconfig.html

@Zero3

This comment has been minimized.

Show comment
Hide comment
@Zero3

Zero3 Oct 17, 2011

I can confirm that the issue is still there even with pushState disabled :(. At least on Android...

Zero3 commented Oct 17, 2011

I can confirm that the issue is still there even with pushState disabled :(. At least on Android...

@jblas

This comment has been minimized.

Show comment
Hide comment
@jblas

jblas Oct 17, 2011

Contributor

@toddparker

Did you mean to close this bug?

Contributor

jblas commented Oct 17, 2011

@toddparker

Did you mean to close this bug?

@johnbender

This comment has been minimized.

Show comment
Hide comment
@johnbender

johnbender Oct 17, 2011

Contributor

Adding a quick note here that a clean phonegap project built against ios 4.3 doesn't have this problem but I can indeed reproduce the back issue with the provided project.

Contributor

johnbender commented Oct 17, 2011

Adding a quick note here that a clean phonegap project built against ios 4.3 doesn't have this problem but I can indeed reproduce the back issue with the provided project.

@johnbender

This comment has been minimized.

Show comment
Hide comment
@johnbender

johnbender Oct 17, 2011

Contributor

@josh-h

Can you try the same with a fresh phonegap project?

http://www.phonegap.com/start/#ios-x4

The fact that I can't reproduce this with phonegap makes me wonder what the difference is and I know very little about native ios development.

Contributor

johnbender commented Oct 17, 2011

@josh-h

Can you try the same with a fresh phonegap project?

http://www.phonegap.com/start/#ios-x4

The fact that I can't reproduce this with phonegap makes me wonder what the difference is and I know very little about native ios development.

@johnbender

This comment has been minimized.

Show comment
Hide comment
@johnbender

johnbender Oct 20, 2011

Contributor

@josh-h

I've got an email into the Nitobi crew so hopefully they'll be able to tell me what makes PhoneGap's UIWebView different from the vanilla web view.

Contributor

johnbender commented Oct 20, 2011

@josh-h

I've got an email into the Nitobi crew so hopefully they'll be able to tell me what makes PhoneGap's UIWebView different from the vanilla web view.

@shazron

This comment has been minimized.

Show comment
Hide comment
@shazron

shazron Oct 25, 2011

One thing I can see the difference is, in PhoneGap we duck-punch a few built in functions like document.addEventListener and window.addEventListener - see https://github.com/callback/callback-ios/blob/master/PhoneGapLib/javascripts/core/phonegap.js.base

We also have a hidden iframe that we use for the JavaScript->Obj-C communication.

shazron commented Oct 25, 2011

One thing I can see the difference is, in PhoneGap we duck-punch a few built in functions like document.addEventListener and window.addEventListener - see https://github.com/callback/callback-ios/blob/master/PhoneGapLib/javascripts/core/phonegap.js.base

We also have a hidden iframe that we use for the JavaScript->Obj-C communication.

@johnbender

This comment has been minimized.

Show comment
Hide comment
@johnbender

johnbender Oct 26, 2011

Contributor

@shazron

Brilliant! I'll take a look at this tomorrow.

Contributor

johnbender commented Oct 26, 2011

@shazron

Brilliant! I'll take a look at this tomorrow.

@johnbender

This comment has been minimized.

Show comment
Hide comment
@johnbender

johnbender Oct 31, 2011

Contributor

@shazron

It's entirely possible that my acking and skimming skills have failed me but I can't seem to find anything that might help/alter the window.history.back in the JavaScript. Any other ideas?

Contributor

johnbender commented Oct 31, 2011

@shazron

It's entirely possible that my acking and skimming skills have failed me but I can't seem to find anything that might help/alter the window.history.back in the JavaScript. Any other ideas?

@shazron

This comment has been minimized.

Show comment
Hide comment
@shazron

shazron Nov 8, 2011

I tested this in PhoneGap as well with the OP's posted source, and I can't recreate the issue. I did not include PhoneGap's phonegap.js so this is running entirely in the UIWebView without any PhoneGap bits (besides the native code).

shazron commented Nov 8, 2011

I tested this in PhoneGap as well with the OP's posted source, and I can't recreate the issue. I did not include PhoneGap's phonegap.js so this is running entirely in the UIWebView without any PhoneGap bits (besides the native code).

@johnbender

This comment has been minimized.

Show comment
Hide comment
@johnbender

johnbender Nov 8, 2011

Contributor

@shazron

That's why I wanted to loop you guys in because I have no clue (zero obj-c/ios dev exp) what the difference might be in the native code but I would like to provide an answer here for future reference. Any help you can provide in that capacity if greatly appreciated,

Contributor

johnbender commented Nov 8, 2011

@shazron

That's why I wanted to loop you guys in because I have no clue (zero obj-c/ios dev exp) what the difference might be in the native code but I would like to provide an answer here for future reference. Any help you can provide in that capacity if greatly appreciated,

@shazron

This comment has been minimized.

Show comment
Hide comment
@shazron

shazron Nov 8, 2011

@johnbender
I'm confused - based on my testing the issue is a "no repro"?

shazron commented Nov 8, 2011

@johnbender
I'm confused - based on my testing the issue is a "no repro"?

@Zero3

This comment has been minimized.

Show comment
Hide comment
@Zero3

Zero3 Nov 9, 2011

I just noticed that the Android part of this bug is fixed in PhoneGap 1.2.0.

Zero3 commented Nov 9, 2011

I just noticed that the Android part of this bug is fixed in PhoneGap 1.2.0.

@toddparker

This comment has been minimized.

Show comment
Hide comment
@toddparker

toddparker Nov 9, 2011

Contributor

So can this issue be closed as fixed or no repro? I'm not sure where we're at.

Contributor

toddparker commented Nov 9, 2011

So can this issue be closed as fixed or no repro? I'm not sure where we're at.

@johnbender

This comment has been minimized.

Show comment
Hide comment
@johnbender

johnbender Nov 10, 2011

Contributor

@shazron

It's a no repro on phonegap. That's why I was hoping you could provide some insight into what specifically is difference about the native UIWebView instance that you use in your iPhone implementation so that vanilla UIWebView user's know what do to when working with jQuery Mobile.

@Zero3

This isn't a phonegap issue.

[edit] referenced myself instead of @shazron :/

Contributor

johnbender commented Nov 10, 2011

@shazron

It's a no repro on phonegap. That's why I was hoping you could provide some insight into what specifically is difference about the native UIWebView instance that you use in your iPhone implementation so that vanilla UIWebView user's know what do to when working with jQuery Mobile.

@Zero3

This isn't a phonegap issue.

[edit] referenced myself instead of @shazron :/

@Zero3

This comment has been minimized.

Show comment
Hide comment
@Zero3

Zero3 Nov 13, 2011

@johnbender

Maybe not, but i thought it was worth mentioning anyway :).

Zero3 commented Nov 13, 2011

@johnbender

Maybe not, but i thought it was worth mentioning anyway :).

@josh-h

This comment has been minimized.

Show comment
Hide comment
@josh-h

josh-h Nov 17, 2011

I had a few cycles to look into this again. I can still reproduce with a base UIWebView directly loading a JQM page. If you look at the UIWebView's 'canGoBack' property you'll find that it always returns false.

@johnbender Do you guys do something that might tell the browser to cancel loading a page? I wonder, if that happens on a UIWebView's first page then it seems that the UIWebView's history management doesn't get initialized correctly and the back behavior breaks.

Fortunately we have an easy enough workaround, first load a non-JQM page in the UIWebView. In Phonegap's case I believe their iframe does the trick, in my codebase a 'start.html' that redirects to the JQM page works.

josh-h commented Nov 17, 2011

I had a few cycles to look into this again. I can still reproduce with a base UIWebView directly loading a JQM page. If you look at the UIWebView's 'canGoBack' property you'll find that it always returns false.

@johnbender Do you guys do something that might tell the browser to cancel loading a page? I wonder, if that happens on a UIWebView's first page then it seems that the UIWebView's history management doesn't get initialized correctly and the back behavior breaks.

Fortunately we have an easy enough workaround, first load a non-JQM page in the UIWebView. In Phonegap's case I believe their iframe does the trick, in my codebase a 'start.html' that redirects to the JQM page works.

@ghost ghost assigned johnbender Dec 15, 2011

@toddparker

This comment has been minimized.

Show comment
Hide comment
@toddparker

toddparker Feb 22, 2012

Contributor

Hi all - is this still and issue with the latest build in master?

Contributor

toddparker commented Feb 22, 2012

Hi all - is this still and issue with the latest build in master?

@mmm3bbb

This comment has been minimized.

Show comment
Hide comment
@mmm3bbb

mmm3bbb Apr 30, 2012

Yes, this is still an issue with JQM 1.1. In my case, I'm loading the uiwebview from a string so I guess I'll try the workaround suggested by Josh - write out a local file and load redirect html to that into uiwebview.

Seems like a lot of people would run into this problem.

mmm3bbb commented Apr 30, 2012

Yes, this is still an issue with JQM 1.1. In my case, I'm loading the uiwebview from a string so I guess I'll try the workaround suggested by Josh - write out a local file and load redirect html to that into uiwebview.

Seems like a lot of people would run into this problem.

@johnbender

This comment has been minimized.

Show comment
Hide comment
@johnbender

johnbender Jun 14, 2012

Contributor

@josh-h @mmm3bbb

I still can't sort out why the UIWebView isn't enabling history for hash changes or complete page reloads. I'm going to keep looking around the iOS docs but the basics aren't working .

Contributor

johnbender commented Jun 14, 2012

@josh-h @mmm3bbb

I still can't sort out why the UIWebView isn't enabling history for hash changes or complete page reloads. I'm going to keep looking around the iOS docs but the basics aren't working .

@mmm3bbb

This comment has been minimized.

Show comment
Hide comment
@mmm3bbb

mmm3bbb Jun 14, 2012

Thx. Actually I tried josh-h's approach and it worked (thank you so much for that!). But the way my system works, I have to take in-memory html content that I normally just load into the UIWebView and instead, at runtime write it out to a file and then load another bundled file that does a redirect to the file I just wrote. It works but it would be nice to clean that up.

mmm3bbb commented Jun 14, 2012

Thx. Actually I tried josh-h's approach and it worked (thank you so much for that!). But the way my system works, I have to take in-memory html content that I normally just load into the UIWebView and instead, at runtime write it out to a file and then load another bundled file that does a redirect to the file I just wrote. It works but it would be nice to clean that up.

@johnbender

This comment has been minimized.

Show comment
Hide comment
@johnbender

johnbender Jun 14, 2012

Contributor

@josh-h @mmm3bbb

It appears to work fine when the everything is loaded externally.

- (void)viewDidLoad
{
    [super viewDidLoad];
    NSString *fullURL = @"http://jquerymobile.com/test/docs/pages/page-dialogs.html"; 
    NSURL *url = [NSURL URLWithString:fullURL]; 
    NSURLRequest *requestObj = [NSURLRequest requestWithURL:url]; 
    [webView loadRequest:requestObj];    
}
Contributor

johnbender commented Jun 14, 2012

@josh-h @mmm3bbb

It appears to work fine when the everything is loaded externally.

- (void)viewDidLoad
{
    [super viewDidLoad];
    NSString *fullURL = @"http://jquerymobile.com/test/docs/pages/page-dialogs.html"; 
    NSURL *url = [NSURL URLWithString:fullURL]; 
    NSURLRequest *requestObj = [NSURLRequest requestWithURL:url]; 
    [webView loadRequest:requestObj];    
}
@mmm3bbb

This comment has been minimized.

Show comment
Hide comment
@mmm3bbb

mmm3bbb Jun 14, 2012

The html that I need to load is dynamically generated, so it makes more sense to write it out to device and load. However, when I just loaded the local file into the webview, it didn't work... which is why I to load the redirect file.

If I understand you correctly, then this problem only exists if a file is loaded from the device.

On Jun 14, 2012, at 1:31 PM, John Bender wrote:

@josh-h @mmm3bbb

It appears to work fine when the everything is loaded externally.

- (void)viewDidLoad
{
   [super viewDidLoad];
   NSString *fullURL = @"http://jquerymobile.com/test/docs/pages/page-dialogs.html"; 
   NSURL *url = [NSURL URLWithString:fullURL]; 
   NSURLRequest *requestObj = [NSURLRequest requestWithURL:url]; 
   [webView loadRequest:requestObj];    
}

Reply to this email directly or view it on GitHub:
#2190 (comment)

mmm3bbb commented Jun 14, 2012

The html that I need to load is dynamically generated, so it makes more sense to write it out to device and load. However, when I just loaded the local file into the webview, it didn't work... which is why I to load the redirect file.

If I understand you correctly, then this problem only exists if a file is loaded from the device.

On Jun 14, 2012, at 1:31 PM, John Bender wrote:

@josh-h @mmm3bbb

It appears to work fine when the everything is loaded externally.

- (void)viewDidLoad
{
   [super viewDidLoad];
   NSString *fullURL = @"http://jquerymobile.com/test/docs/pages/page-dialogs.html"; 
   NSURL *url = [NSURL URLWithString:fullURL]; 
   NSURLRequest *requestObj = [NSURLRequest requestWithURL:url]; 
   [webView loadRequest:requestObj];    
}

Reply to this email directly or view it on GitHub:
#2190 (comment)

@johnbender

This comment has been minimized.

Show comment
Hide comment
@johnbender

johnbender Jun 14, 2012

Contributor

@josh-h @mmm3bbb

Bam!

- (void)viewDidLoad
{
    [super viewDidLoad];
    NSString *fullURL = [[NSBundle mainBundle] pathForResource:@"dialog" ofType:@"html"];
    NSURL *url = [NSURL fileURLWithPath:fullURL]; 
    NSURLRequest *requestObj = [NSURLRequest requestWithURL:url]; 
    [webView loadRequest:requestObj];
}
Contributor

johnbender commented Jun 14, 2012

@josh-h @mmm3bbb

Bam!

- (void)viewDidLoad
{
    [super viewDidLoad];
    NSString *fullURL = [[NSBundle mainBundle] pathForResource:@"dialog" ofType:@"html"];
    NSURL *url = [NSURL fileURLWithPath:fullURL]; 
    NSURLRequest *requestObj = [NSURLRequest requestWithURL:url]; 
    [webView loadRequest:requestObj];
}

@johnbender johnbender closed this Jun 14, 2012

@mmm3bbb

This comment has been minimized.

Show comment
Hide comment
@mmm3bbb

mmm3bbb Jun 14, 2012

Is Bam! a good thing or bad thing?

On Jun 14, 2012, at 1:48 PM, John Bender wrote:

@josh-h @mmm3bbb

Bam!

- (void)viewDidLoad
{
   [super viewDidLoad];
   NSString *fullURL = [[NSBundle mainBundle] pathForResource:@"dialog" ofType:@"html"];
   NSURL *url = [NSURL fileURLWithPath:fullURL]; 
   NSURLRequest *requestObj = [NSURLRequest requestWithURL:url]; 
   [webView loadRequest:requestObj];
}

Reply to this email directly or view it on GitHub:
#2190 (comment)

mmm3bbb commented Jun 14, 2012

Is Bam! a good thing or bad thing?

On Jun 14, 2012, at 1:48 PM, John Bender wrote:

@josh-h @mmm3bbb

Bam!

- (void)viewDidLoad
{
   [super viewDidLoad];
   NSString *fullURL = [[NSBundle mainBundle] pathForResource:@"dialog" ofType:@"html"];
   NSURL *url = [NSURL fileURLWithPath:fullURL]; 
   NSURLRequest *requestObj = [NSURLRequest requestWithURL:url]; 
   [webView loadRequest:requestObj];
}

Reply to this email directly or view it on GitHub:
#2190 (comment)

@johnbender

This comment has been minimized.

Show comment
Hide comment
@johnbender

johnbender Jun 14, 2012

Contributor

Since it's not obvious what I did, I loaded with loadRequest using a file system url and not loadData. Problem solved.

Contributor

johnbender commented Jun 14, 2012

Since it's not obvious what I did, I loaded with loadRequest using a file system url and not loadData. Problem solved.

@mmm3bbb

This comment has been minimized.

Show comment
Hide comment
@mmm3bbb

mmm3bbb Jun 14, 2012

Ooooooh. Let me see if that works for me.

On Jun 14, 2012, at 1:51 PM, John Bender wrote:

Since it's not obvious what I did, I loaded with loadRequest using a file system url and not loadData. Problem solved.


Reply to this email directly or view it on GitHub:
#2190 (comment)

mmm3bbb commented Jun 14, 2012

Ooooooh. Let me see if that works for me.

On Jun 14, 2012, at 1:51 PM, John Bender wrote:

Since it's not obvious what I did, I loaded with loadRequest using a file system url and not loadData. Problem solved.


Reply to this email directly or view it on GitHub:
#2190 (comment)

@mmm3bbb

This comment has been minimized.

Show comment
Hide comment
@mmm3bbb

mmm3bbb Jun 14, 2012

Bam! Although perversely this actually adds 2 lines of code for me over the redirect I have. And I still have the gymnastics of writing out and loading a file instead of just loading the html string into the uiwebview... but this certainly works well enough for me.

Thanks, ...Michael

On Jun 14, 2012, at 1:51 PM, John Bender wrote:

Since it's not obvious what I did, I loaded with loadRequest using a file system url and not loadData. Problem solved.


Reply to this email directly or view it on GitHub:
#2190 (comment)

mmm3bbb commented Jun 14, 2012

Bam! Although perversely this actually adds 2 lines of code for me over the redirect I have. And I still have the gymnastics of writing out and loading a file instead of just loading the html string into the uiwebview... but this certainly works well enough for me.

Thanks, ...Michael

On Jun 14, 2012, at 1:51 PM, John Bender wrote:

Since it's not obvious what I did, I loaded with loadRequest using a file system url and not loadData. Problem solved.


Reply to this email directly or view it on GitHub:
#2190 (comment)

@toddparker

This comment has been minimized.

Show comment
Hide comment
@toddparker

toddparker Jun 15, 2012

Contributor

Mind adding a note about this to the phone gap page Bender?

On Jun 14, 2012, at 4:51 PM, "John Bender" reply@reply.github.com wrote:

Since it's not obvious what I did, I loaded with loadRequest using a file system url and not loadData. Problem solved.


Reply to this email directly or view it on GitHub:
#2190 (comment)

Contributor

toddparker commented Jun 15, 2012

Mind adding a note about this to the phone gap page Bender?

On Jun 14, 2012, at 4:51 PM, "John Bender" reply@reply.github.com wrote:

Since it's not obvious what I did, I loaded with loadRequest using a file system url and not loadData. Problem solved.


Reply to this email directly or view it on GitHub:
#2190 (comment)

@johnbender

This comment has been minimized.

Show comment
Hide comment
@johnbender

johnbender Jun 15, 2012

Contributor

@toddparker

Hmm, well it's not a phonegap issue, but rather for people running entirely custom Obj-c UIWebViews. I'll see if I can fit it in there.

Contributor

johnbender commented Jun 15, 2012

@toddparker

Hmm, well it's not a phonegap issue, but rather for people running entirely custom Obj-c UIWebViews. I'll see if I can fit it in there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment