Created attachment 115465 [details] [review]
Patch

I'm pretty sure that was an intentional change; the -set properties are not meant to be used like that. Kris, correct me if I'm wrong.

(In reply to comment #2)
> I'm pretty sure that was an intentional change; the -set properties are not
> meant to be used like that

All other *-set properties seems to work as I expect.

It was certainly never intended that setting a *-set property to TRUE
would give you a predictable result.

The whole point of them is to be able to set them to FALSE to reset
back to the default unset state.

(In reply to comment #4)
> It was certainly never intended that setting a *-set property to TRUE
> would give you a predictable result.
> 
> The whole point of them is to be able to set them to FALSE to reset
> back to the default unset state.

If the result of setting that property to TRUE is undefined, why don't you define it? That will not break API, but will give more consistency.