Default type of filter is reseted when selecting value from a database list

How to reproduce

To avoid steps the first two steps, and having to create data for the livetable, you can import bugReport_02112023.WebHome.xar

1. Create a Live Data on a class which has a database list property (called myList after)
2. Configure the Live Data to filter myList with operator "equals" instead of the default "contains", as in the example code below

{{liveData
  id="bugReport_02112023"
  properties="doc.title,myList"
  source="liveTable"
  sourceParameters="className=bugReport_02112023.databaseListClass"
}}{
  "query": {
    "filters": [
      {
        "property": "myList",
        "constraints": [
          {
            "operator": "equals"
          }
        ]
      }
    ]
  }
}
{{/liveData}} 

1. Open the filter panel (button with vertical "..." >> Filter...)
2. View that myList has a default "Equals" operator for the filter, like in the following screenshot
3. Select one of the values in the list to the right
4. See that the operator changed back to "Contains", like in the following screenshot
5. 

Expected behaviour

The operator should be kept to its configured default value after the select instead of switching to "Contains".

The expected behaviour happens with text properties.