we are currently migrating a solution to the web. We have noticed the following issues (so far ):
it seems that the tab order is the wrong way compared to the smart client. I don’t know if there is something like a tab order at all in the web?
HTML Tooltips don’t work (they show the HTML code)
HTML labels also show the code
In a formInDialog that has a tab panel showing a table view, we have one field that has a display/return type value list. Only in the web client we see the ID instead of the display value. The field is not editable.
On our login form there is two globals for name and password. The user name is a text field that we transform into userId etc. Since many browsers remember form inputs, the browser offers us the last name entered. When we choose that name, the login method receives no name, so somehow the value is not really set in the field.
On a date field we use a value list that has dates for every hour. The field is formatted as hh:mm and the smart client shows correctly 09:00, 10:00 etc. In the web we get the full date in the value list, so somehow the formatting is not preserved in the value list.
On our login form there is two globals for name and password. The user name is a text field that we transform into userId etc. Since many browsers remember form inputs, the browser offers us the last name entered. When we choose that name, the login method receives no name, so somehow the value is not really set in the field.
The only way I found to work around this is to enter names directly or, if I erroneously choose a browser suggestion, enter a wrong username, make the search fail and then enter the name manually.
I’ve already created a ticket in the support system and it’s now marked “in progress”, so…
Don’t you think that this is very weird? Text is text, isn’t it? It shouldn’t really matter where it comes from. I am not sure if this problem only occurs in a login form, it could apply to all kinds of different fields!?
patrick:
Don’t you think that this is very weird? Text is text, isn’t it? It shouldn’t really matter where it comes from. I am not sure if this problem only occurs in a login form, it could apply to all kinds of different fields!?
It doesn’t happen on login forms only. It’s a general issue. See my post about valuelist management in WebClient.