Ticket #277 (closed defect: fixed)

Opened 7 months ago

Last modified 2 months ago

Selecting null in selection-control causes dependent selection-control to call wrong url

Reported by: sdm Owned by: freya
Priority: major Milestone: 0.4
Component: modules/kauri-forms Version: trunk
Keywords: Cc:

Description

I have 2 selection-controls A and B in my form. B depends on A, so if A changes, B should change too. Both selection-controls have the nullable: true option.

Initially, the selected value in A is null. This causes B to call the following url:

http://localhost/abc/getB/byA/

Then I change the value of A to eg. 2. Logically, B now calls this url:

http://localhost/abc/getB/byA/2

But when I then change the value of A back to null, B still calls the same url:

http://localhost/abc/getB/byA/2 instead of http://localhost/abc/getB/byA/

This causes B to still have available select-options, while it should actually be empty, because no value in A is selected.

Attachments

Change History

Changed 2 months ago by freya

  • owner changed from mpo to freya
  • status changed from new to assigned

actions: 1. change logic in field.js (240) 2. provide callback function (clear options) in case of error after ajax call to get options

Changed 2 months ago by freya

  • status changed from assigned to closed
  • resolution set to fixed

fixed in r1577

Add/Change #277 (Selecting null in selection-control causes dependent selection-control to call wrong url)

Author


E-mail address and user name can be saved in the Preferences.


Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.