search

palimadra / iui

Automatically exported from code.google.com/p/iui
MIT License
0 stars 0 forks source link

Display hangs on return from mailto link in OS 3.x #147

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1. My code is:<li><a href="mailto:someone@isp.com" target="_self">xyz 
email</a></li>

2. Going to mail to send works fine under 2.0 or 3.0

3. Returning from mail or canceling mail will result in a display hang (neither 
browser back 
button or iui previous button works) upon return. This hang can be released by 
clicking the + 
button and canceling with the iPhone 3GS. Returning from mail works fine, and 
as expected, with 
the original iPhone and 2.0 software (both browser back button and iui previous 
button work 
correctly.

This possibly could be a bug in the iPhone 3.0 software.

What version of the product are you using? On what operating system? Using iui 
.13

Original issue reported on code.google.com by GRWi...@gmail.com on 3 Jul 2009 at 10:51

GoogleCodeExporter commented 9 years ago 
I have the same problem with iui 0.20 and an iPhone 3G (Firmware 3.0). On my 
side
this problem is reproducible with firmware 3.0 only. I spend a whole day with 
fixing
it but I still have no success. Does anybody have an idea how to fix it?

Original comment by i...@dreier-it.de on 21 Jul 2009 at 1:26

GoogleCodeExporter commented 9 years ago 
I have the same issue right now, everything is blocked after returning from 
mail.
Problem on iPhone firmware 3.0 and 3.1.

Original comment by charles....@gmail.com on 28 Sep 2009 at 9:02

GoogleCodeExporter commented 9 years ago 
Same problem with iui 0.30 and iPhone 3G S (Firmware 3.1.2)

Original comment by rogersp...@yahoo.com on 19 Oct 2009 at 4:02

GoogleCodeExporter commented 9 years ago 
Issue 206 has been merged into this issue.

Original comment by msgilli...@gmail.com on 3 Jan 2010 at 4:38

GoogleCodeExporter commented 9 years ago 
Thanks to rsprik for finding more information on this issue and for reporting 
that Issue 206 and Issue 147 
appear to be the same.

Original comment by msgilli...@gmail.com on 3 Jan 2010 at 4:42

GoogleCodeExporter commented 9 years ago 
For handy reference, here are the links that rsprik posted to Issue 206:

http://discussions.apple.com/thread.jspa?threadID=2126836&tstart=0
http://code.google.com/p/jqtouch/issues/detail?id=45
http://code.google.com/p/jqtouch/issues/detail?id=75

Original comment by msgilli...@gmail.com on 3 Jan 2010 at 4:44

GoogleCodeExporter commented 9 years ago 
A potential workaround might be to set:
iui.animOn = false;

This would also help narrow the issue.  Will someone please try it and report 
back here?

Original comment by msgilli...@gmail.com on 3 Jan 2010 at 4:47

GoogleCodeExporter commented 9 years ago 
Tried setting iui.animOn = false

Sorry, still hanging after return from mailto link

Original comment by rogersp...@yahoo.com on 3 Jan 2010 at 5:16

GoogleCodeExporter commented 9 years ago 
Interesting behavior... try a mailto link, return to hung iui page. Click on 
two or three unresponsive links. Close 
the iphone Safari browser (press Home button)... immediately open the browser 
back up... it "catches" up with 
the links you pressed and seems to return to normal.

Original comment by rogersp...@yahoo.com on 3 Jan 2010 at 5:23

GoogleCodeExporter commented 9 years ago 
Has anyone had any further luck with this one?

Original comment by brentmca...@gmail.com on 18 Mar 2010 at 10:33

GoogleCodeExporter commented 9 years ago 
Has this been logged at Apple?

Original comment by rene%wrk...@gtempaccount.com on 22 Mar 2010 at 11:51

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Someone at http://discussions.apple.com/thread.jspa?threadID=2126836 suggests 
"rewriting the stackLayout 
Javascript and transforming the webkit transitions into keyframe transitions".

That's way beyond what I'm capable of.

Any chance of success?

Original comment by rene%wrk...@gtempaccount.com on 23 Mar 2010 at 12:09

GoogleCodeExporter commented 9 years ago 
I haven't submitted it to Apple, René do you want to do that?

Original comment by msgilli...@gmail.com on 23 Mar 2010 at 12:17

GoogleCodeExporter commented 9 years ago 
Alex Zylka presents code for a workaround on this thread:
http://groups.google.com/group/iphonewebdev/browse_thread/thread/12b86039e961da1
c

I  haven't  tried it yet.

Original comment by msgilli...@gmail.com on 23 Mar 2010 at 2:08

GoogleCodeExporter commented 9 years ago 
I still haven't tried Alex's workaround, but I did spend some time adding 
logging statements to iui.js and 
trying to figure out where in the code the problem occurs -- I did the testing 
with animOn = false.  I was 
testing in the simulator with the link-types.html test page and after touching 
the mailto: link (and then 
touching cancel)

I found that the callback from the setTimout in iui.showPage() was never being 
called.  When I changed the 
code to call iui.showPage immediately, the setInterval() call in slidePages1 
did not seem to work.

So perhaps something in the mailto: handling is breaking timers?

Original comment by msgilli...@gmail.com on 23 Mar 2010 at 7:48

GoogleCodeExporter commented 9 years ago 
Additional info posted to the iPhoneWebDev thread on this issue:
http://groups.google.com/group/iphonewebdev/browse_thread/thread/12b86039e961da1
c

Original comment by msgilli...@gmail.com on 24 Mar 2010 at 8:32

GoogleCodeExporter commented 9 years ago 
OK, I've reported this to Apple with Bug ID# 7790652 just to be sure they've 
got it.

Original comment by msgilli...@gmail.com on 24 Mar 2010 at 11:09

GoogleCodeExporter commented 9 years ago 
Sean, what do you plan to do with issues like this that are older than a few 
years, and affect an older OS?  Are a lot of these same issues lingering around 
in new iOS versions?  Should we make a sweep through this list of 2 year old + 
issues and do some cleanup?

Original comment by dko...@gmail.com on 7 Aug 2012 at 11:56

GoogleCodeExporter commented 9 years ago 
Yeah, I've been doing some of that.  You wanna help with cleanup?  :)

For this one, can you find what Apple has done with Bug ID# 7790652?  If we 
want to be thorough we should report what that resolution was here (i.e. Fixe 
in iOS 4) make sure this use case works on recent iOS and close this issue.

Original comment by msgilli...@gmail.com on 11 Aug 2012 at 5:43

GoogleCodeExporter commented 9 years ago

Original comment by msgilli...@gmail.com on 11 Aug 2012 at 5:55

GoogleCodeExporter commented 9 years ago 
Ok, so to clarify, do we need to support legacy iOS?  I think for Android, it 
makes sense to support Androids that are within the significant volume of 
shipping or installed base (google reports these numbers quarterly).  For iOS, 
the question is do you care about old iPhones or iPods that can't run iOS 4+ ?  
Depending on the answer, we go back and fix for iOS 3.0, or just verify that it 
was fixed in iOS 4.0.

Original comment by dko...@gmail.com on 7 Oct 2012 at 9:30

GoogleCodeExporter commented 9 years ago 
I'd like to support iOS 3.0 if there is an issue and it is not too much work.  
If it's an Apple bug without a workaround, there's not much we can do.

Original comment by msgilli...@gmail.com on 8 Oct 2012 at 11:10

GoogleCodeExporter commented 9 years ago 
I went to look at Apple Bug ID# 7790652 and they had requested more 
information, which I never provided :(

So they just closed out the bug.

Maybe we should just close out this issue  -- nobody has reported it recently.  
It would have been nice if Apple had marked it as fixed, though.

Original comment by msgilli...@gmail.com on 8 Oct 2012 at 11:12