2017.5 Recording Take Lane Selection Issue?

I posted this topic in the problem report forum, but I thought I would post here as well to hear some opinions...
 
First let me say that I love the new lane saving paradigm to use existing lanes prior to creating new (when available)...
...and also I might add that I rarely use the Lane Mute button... ...and I work almost exclusivey in Sound On Sound Mode (Not Comping)
 
...but yesterday I thought it was expedient to use the Lane Mute.  ...and it was......... until I began new recording.
 
I discovered that it will use the empty area of a lane even if the lane is muted. This is very counter-intuitive as it took me a moment to realize why I didn't hear the take, and then had to change back to clip muting instead of Lane and of course switch the lane muting back on afterwards (after moving the needed take(s)) so that their' images disappeared from the track view...
 
A lot of extra work... Anyone else have any take on this (excuse the unintended pun)...
 
For me? If a clip is muted either way (clip or lane) it should not appear in the track view (which still needs better definition to make it more obviously NOT a Lane when Lanes are open)... and  Muted Lanes should NOT be used for new recordings? this just seems foolish?
 
My rant for now... Sorry... thanks...
 

Sorry, Keni.  I rarely ever use Take Lane mute, preferring clip mute instead, so this isn't something I'd come across.
 
I do get your point though.  I do wonder if it's practical for SONAR to choose a lane in real-time based on available area and mute status, and all the possible combinations.