Metadata
- Source
- ENGAGE-300
- Type
- Bug
- Priority
- Critical
- Status
- Closed
- Resolution
- Fixed
- Assignee
- James Yoon
- Reporter
- James Yoon
- Created
2010-01-27T10:59:43.000-0500 - Updated
2010-02-03T11:24:30.000-0500 - Versions
- N/A
- Fixed Versions
-
- 0.3b
- Component
-
- Mobile
Description
Proper behaviour should be that the the user remains within the chromeless setting.
Comments
-
Colin Clark commented
2010-02-01T17:49:06.000-0500 Here's a thread from fluid-work describing the technical issues involved with chromeless home screens on the iPhone:
http://old.nabble.com/Chromelessness-in-Engage-0.3-td27388098.html
Note that Android phones don't really have this problem because the browser is, by default, mostly chromeless.
-
Colin Clark commented
2010-02-01T17:52:40.000-0500 This issue was resolved for all current top-level pages in Engage 0.3 at r9221.
-
Colin Clark commented
2010-02-01T17:53:28.000-0500 James, I'll give you the pleasure of closing this one after you've had a chance to test it.
Presumably then we'll file a new bug about the fact that users can't go back because there's no navigation bar yet. 😉
-
James Yoon commented
2010-02-03T11:24:30.000-0500 Works as advertised!