Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop using the html selects for selecting things like Request Type, Status, Priority etc. #2

Open
edchat opened this issue May 20, 2013 · 1 comment
Assignees

Comments

@edchat
Copy link
Owner

edchat commented May 20, 2013

The html select does not work well for mobile apps, I will change it to use a mobile opener with a selection list. This should make it look and function better.

@ghost ghost assigned edchat May 20, 2013
@edchat
Copy link
Owner Author

edchat commented May 24, 2013

This is partially fixed, it is using an opener with a selection list, but it should be cleaned up more by using a custom widget for these fields for a couple of reasons.

  1. To make it easier to keep track of the value vs. displayed value, currently a lot of code is involved in trying to get the store id or key and to display the store label or description, a custom widget could handle that in a consistent way.
  2. We should change the html/css for these fields so that they look more like a RoundRectList item instead of a readonly TextBox, that way people will know what they are.
  3. These fields currently work with "click" but not with keypress for enter, so that also should be added via a custom widget.
  4. It may also be possible to know when the value is not set and to set the readOnlyHidden class when the field is not set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant