If a track is Muted and Solo'd at the same time, currently Mute takes priority. I hear nothing.
My workflow would benefit if Solo took priority. Save me a number of mouseclicks every day.
 
In practice I find I often want to solo a muted track.
But I have yet to need to mute a solo'd track.
 
An extension to this is to light up all the Mute buttons if somewhere Solo is on.
Saves me wondering what the heck is going on if I'm scrolled to some other track.
 
...or just light them dimly (like the Take Lane and Automation buttons do),
to indicate it'll be off as soon as the Solo is lifted.

I'm not so sure if this is a very common workflow.   
 
However, I've voted anyway since I actually do the same thing on occasion.   
 

Yes, I would prefer this priority, too! Because on my work I often mute several tracks and want then to listen to one of them.
 

This would indeed be great! Just a personal work flow preference though so not sure how much traction it will get. 

 
What does a traditional desk do in this situation ?
 

Paul P
 
What does a traditional desk do in this situation ?
 

I guess it would equate to pfl,  which generally overrides mute and feeds the signal to monitor source (usually phones) .  Mind you,  in the digital age what analogue desks did has become a bit of a mute point:) 

tenfoot
Mind you,  in the digital age what analogue desks did has become a bit of a mute point:) 

Sonar's Console certainly attempts to emulate one in many respects so if a choice had to be made, I'd go with tradition (if there is/was one).  As time goes by less and less people will have ever touched a real desk but for those that have I think they should get what they expect to get.  I'd also expect what was/is chosen for real desks had some logic behind the decision.

Paul P

tenfoot
Mind you,  in the digital age what analogue desks did has become a bit of a mute point:) 

.I'd also expect what was/is chosen for real desks had some logic behind the decision.

 
I certainly agree Paul,  but it has also been shaped by the limitations of the technology,  many of which we have now surpassed.  In analogue days,  every button,  slider,  input and output had a single function. They were wired to electronics that could only function one way.  By way of contrast now,  on a digital desk you can remap any input or output through almost any fader,  and all controls change contextually depending on menu selection because of computer control. Due to the onboard processing and sound shaping capability of digital mixers,  they are really many devices combined,  and the layout and function must move with this. 
There is a very basic example of this in Sonar.  The advent of the single stereo track has totally changed the function of panning.  We still have a single pan pot on the on the Sonar console,  but in the context of moving and placement of a stereo track on the sound stage,  it is rarely what is needed. You really need 2 panpots to maintain the 'balance of the original stereo sound but still have the ability to move it around in the stereo field.  There are of course the channel tools and many other ways to do this,  but the single pan pot persists solely because that is how it has always been. 

Paul P
What does a traditional desk do in this situation ?

 
From memory (and this was 20 years ago!), the SSL4000 channels functionality was pretty much exactly as Sonar works:
1. SOLO button would mute all other channels not in Solo mode;
2. MUTE button would mute that specific channel
 
So if you had both pressed in the channel would be muted.  Until I read this post I hadn't given it much thought because that was the workflow I had accepted, but in the DAW domain it would be possible to have a 'priority' switch to flip that around either as a global setting on local per channel.  The latter could get confusing though!