Form Behavior on Google Chrome and Mozilla Firefox

Form Behavior on Google Chrome and Mozilla Firefox

  

Hi Guys,

Just want to ask if you encounter this behavior and how did you address the issue.

I have a webscreen(Create and Edit) with below settings. I have a field called client type with default value is null on New Record. Depending on the Client Type choosen some fields will hide/show.


NOTE: This record has not been save yet so no record will be retrieve from the database.

Google Chrome Behavior when you refresh the page (F5). If you look at the screenshot below when I hit F5 the value of client type was reset to null (correct behavior)


Firefox Behavior(Version 62.0.3) when you refresh the page. If you look at the screenshot below the value was retain.

The firefox behavior causes confusion since it is still showing CONSUMER but the other fields that is suppose to be visible when this value is choosen was hidden. When I try to debug the client type field it is null, that is why some fields was hidden.


Is there a way to reset this back to null using FORM? 



Hi,

I think it's a bug on firefox that preserves the form values. Possible related with autocomplete.

You could try to use the fields outside of the wiget form or just use local records instead of the form widget and check if it has the same behaviour.


Regards,

Sérgio 

Hello Michael,

This is a know behaviour in Firefox. It just try to keep data on F5 (Ctrl+F5 should work), and he gets this information from cache, instead of going to the server (than the inconsistences). 

A search in google have a possible solution: to add the attribute autocomplete="off" to the inputs (you can use the Extended Properties section for that).
 
Another possible solution is to disable the cache in the page (you have to add some headers to the page), this will make the browser fetch a fresh page from server on a F5 press.

Be careful with possible "side effects"...

Cheers.

Sérgio Neto wrote:

Hi,

I think it's a bug on firefox that preserves the form values. Possible related with autocomplete.

You could try to use the fields outside of the wiget form or just use local records instead of the form widget and check if it has the same behaviour.


Regards,

Sérgio 

Hi Sergio,

The OutSystems Form is not really a form. It is just a DIV with some JavaScript bound.
It is enough to have a single input in a page, o the platform, when building the page, to add a Form around the page. So, all pages with at least one input have a form on it, and the inputs are inside it. 

Other than the facilitation to group inputs (the Record, the validation, CSS), the OutSystems form does not really have much impact in the behaviour of the inputs.

Cheers.