While working with embedded dashboard filters, I encountered an unexpected result and wanted some feedback.

Here is a simple example to illustrate what I found.  I created a simple dashboard on opportunities with a List Filter on Name and a chart of count that is Won.  

The Opportunity Name filter is set to Single Selection (required), which is where the unexpected results occur.  I do not have a start value assigned to the List Filter.

I embedded the dashboard into a Lighting Page on Accounts.  I also set a filter with the new syntax - {'datasets':{'opportunity':[{'fields':['Name'], 'filter':{'operator': 'matches', 'values':['$Name']}}]}}

When viewing an Opportunity, the List Filter is set to the first Opportunity based on alphabetical sort.  When this is a different Opportunity than the first one listed alphabetically, no results are found.  

It seems the filter condition is being applied after the first item in the list is selected, rather than filtering and selecting the first option.

The filter works as expected when the new filter is used as a selection rather than a filter - {'datasets' : {'opportunity': [ {'fields': ['Name'], 'selection': ['$Name']}]}}

While I understand why this occurs, it seems like the filter should be smart enough to apply the condition from the Lighting page before make a selection.

Screen shots with both filter and selection attached - top is filter, bottom is selection.