Pending Review
Last Updated: 04 Mar 2019 12:03 by ADMIN
Created by: Anders Mad.
Comments: 1
Category: ComboBox
Type: Bug Report


You prob. already know this, but in Chrome attribute autocomplete should be "disabled" instead of "off" for e.g. combobox - then we don't get the auto fill.

Even thought it has no id nor name - I think it looks at the lavbel - in my case its "Name" and the combobox get a big Chrome auto fill from the address book. Setting it from "off" to "disabled" will disable both auto complete AND auto fill.

The same goes for the AJAX Combobox - will you notify that team too? Current hotfix for that is `$(".rcbInput").attr("autocomplete", "disabled");`



Last Updated: 25 Apr 2019 11:25 by ADMIN

I have attached a simplified version of my app that reproduces the issue of infinite valueMapper requests.  

Reproduction steps:

  1. Open the example htm file 
  2. Open the browsers dev tools to the network tab and clear any request that have been logged.
  3. Click "Add New Load Stop." Result: A row will added to the list view that contains a combo box and one request to the Orders endpoint will be made.
  4. Set a value for the combo box that was added. Result: No additional request will be made if selecting from first few items in the list.
  5. Click "Add New Load Stop." Result: A second row will be added to the list view that also contains a combo box, a query to the Orders endpoint will be made, and an infinite number of requests will be made to the ValuMapper endpoint.

This is reproducible in both Edge and Chrome browsers.


Thank you for your help,