Tickets :: [#6281] Why force iPhone to mimp/mobile mode?

6.0.0-beta1

7/4/25

Summary	Why force iPhone to mimp/mobile mode?
Queue	Horde Framework Packages
Queue Version	FRAMEWORK_3
Type	Enhancement
State	Resolved
Priority	1. Low
Owners
Requester	eric.rostetter (at) physics (dot) utexas (dot) edu
Created	02/18/2008 (6346 days ago)
Due
Updated	09/30/2012 (4660 days ago)
Assigned
Resolved	02/27/2008 (6337 days ago)
Milestone
Patch	No

09/30/2012 04:15:29 PM	ccrowley (at) cecaroof (dot) com	Comment #9	Reply to this comment
Same problem only on iPad2 is preventing me from accessing my incoming mail. Can send fine, just can't receive now.

09/30/2012 04:15:02 PM	ccrowley (at) cecaroof (dot) com	Comment #8	Reply to this comment
Same problem only on iPad2 is preventing me from accessing my incoming mail. Can send fine, just can't receive now.

02/27/2008 11:34:43 PM	Chuck Hagenbuch	Comment #7 State ⇒ Resolved	Reply to this comment
Okay. ~~Request 6332~~ created, and I'll close this one.

02/27/2008 11:21:12 PM	Jan Schneider	Comment #6	Reply to this comment
Not sure, the update was rather regarding the view switch link in mimp, though this should have been a new ticket. Since we consider browsers mobile for any small device, i.e. PDAs, I think we should do the same for iPhone. With the view switch users still have the option to use anything else.

02/27/2008 08:43:34 PM	Chuck Hagenbuch	Comment #5	Reply to this comment
Jan, since you moved this out of feedback, what's the resolution here?

02/24/2008 12:44:59 PM	Jan Schneider	State ⇒ Accepted

02/19/2008 07:30:16 PM	Chuck Hagenbuch	Comment #4	Reply to this comment
I don't think a link or two to different modes is going to be the killer here...

02/19/2008 05:45:58 AM	Michael Slusarz	Comment #3	Reply to this comment
An alternate solution would be to allow the mimp login screen (template/mobile.php I think) to allow them to select the interface (traditional, dynamic, mobile), defaulting to mobile, so they could overturn the default mail interface (if for some reason, the above change isn't appropriate). I do not agree with this idea, FWIW. The mobile login page should always be as basic as possible.

02/18/2008 11:46:44 PM	Chuck Hagenbuch	Comment #2 State ⇒ Feedback	Reply to this comment
I'm guessing MIMP should offer switching to other modes on its login screen regardless of what we decide about the iPhone in particular. Could you please create a separate MIMP ticket for this? If someone wanted to give me an iPod touch I'd promise to work on good mobile Safari support. ;) But seriously: I can go either way on this. It is a mobile device, but I guess what that means is fuzzy. Can you bring it up on the mailing list (horde or dev, I think) to get input from people about what we should default mobile safari too? And if we decide to not mark it as mobile, should we do that for all mobile safari versions, or just the iPhone/iPod touch?

02/18/2008 07:32:02 PM	Eric Rostetter	Comment #1 Priority ⇒ 1. Low State ⇒ New Queue ⇒ Horde Framework Packages Summary ⇒ Why force iPhone to mimp/mobile mode? Type ⇒ Enhancement	Reply to this comment
horde/framework/Browser/Browser.php forces the iPhone to mobile mode, hence defaulting to mimp instead of imp. While the iPhone is mobile, it has a more-or-less full Safari which works fine in non-mobile mode. My iPhone users all want the imp and not mimp interface, and the mimp login screen doesn't let them choose the interface the way the imp login screen does. I patched it with the following overly long patch to not mark the iPhone as mobile: 494a495,501 if (strpos($agent, 'iPhone' ) !== false && strpos($agent, 'Safari' ) !== false && strpos($agent, 'Mobile' ) !== false ) { // Exclude the iPhone -- EJR $this->_mobile = false; } It would be better probably to just except the "iPhone" pattern in the "if" statement above that though. I don't know of any other implications of doing this for other apps. No one has reported any problems at least... An alternate solution would be to allow the mimp login screen (template/mobile.php I think) to allow them to select the interface (traditional, dynamic, mobile), defaulting to mobile, so they could overturn the default mail interface (if for some reason, the above change isn't appropriate).