| Summary | wrong default view when using a mobile device |
| Queue | MIMP |
| Queue Version | 1.1 |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | agerhard (at) usp (dot) br |
| Created | 8/22/08 (6440 days ago) |
| Due | |
| Updated | 8/24/08 (6438 days ago) |
| Assigned | |
| Resolved | 8/24/08 (6438 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
login.php, not only
configuration or prefs files. I think this is a conceptual "bug". If I
implement a Webmail
service that is mainly used by normal computer users, but also
considering the possibility
of mobile device use, I expect that the default behavior in the mobile
case is to use
a rendering compatible with mobile devices, not the default rendering
for normal computers.
like to set the configuration values.
State ⇒ Not A Bug
to set the configuration values.
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ MIMP
Summary ⇒ wrong default view when using a mobile device
Type ⇒ Bug
State ⇒ Unconfirmed
"view" (as defined by force_view and select_view = false) is dimp,
which is not appropriate (it renders badly). With I really want is that
when using a mobile device, the default/forced view is mimp. But only
if the user access from a mobile device.
If I define "select_view" as true, then I have to choose the view in
the login page, with the possibility of annoying users if they choose
the view incorrectly.
The point is that I am obliged to define a view (by the variable
"force_view") . I would like instead to have a default view for mobile
devices and other default view for normal computers.
I think that this problem occurs because the variables select_view and
force_view are coupled. Maybe the
way to solve this is to have two "force_view" variables, one for
mobile and another for normal use.
Then, I could have, for example, "force_view_mobile" = mimp and
"force_view" = dimp. The decision
of using one or another is then made by the detection routines (isMobile()).