[MAGNOLIA-2566] Make Magnolia authoring work on iPhone Created: 21/Jan/09 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Boris Kraft | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | iphone | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
Magnolia authoring "nearly" works on iPhones. The one issue I have identified right now is that the way we size adminCentral and the dialogs doesn't allow to scroll the content on an iPhone. To clarify: if you open up adminCentral on on iPhone, the content area is sized such that it fits within the screen real estate. But no scroll bar will be shown. Thus, if you open a tree, it will not be displayed in its entirety, in other words, you cannot reach some of the branches. (workaround: use search) The second issue is that if you do open a dialog, it shows exactly the same behavior. If the dialog contains more fields than fit on the screen, you cannot scroll and thus you cannot edit the fields that are not displayed. I have no workaround for that. |
| Comments |
| Comment by Brian Bowman [ 20/Feb/09 ] |
|
Not sure if mobile Chrome/Safari are both built on WebKit as well, but I experience the same exact problems on Android. |
| Comment by Boris Kraft [ 20/Feb/09 ] |
|
yes, they are both built with webkit |
| Comment by Magnolia International [ 20/Feb/09 ] |
|
Hmm, maybe if I somehow got offered a device to test this I'd be able to fix it? |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |