>>It isn't a crusade at all. I simply don't believe that the Fox team needs to spend its time and resources fixing something that is: A well known behavior; Isn't a bug; and Can be easily handled through good coding practices by the developer.
>>
>>Simple as that.
>
>Sorry to come back on this again but i don't beleive its as simple as that I aggree it's not a bug and is a well known behavior, does this mean well known behaviors cant be changed ?
>
>In a past message you said you would like it, and on this message you say you dont.
>
>This simple change from the fox team would remove 40% of the code in my past example, is it a good coding practice to keep the code clear and concise ?
>
Stephane,

I'm not sure what you mean here. Frankly, I don't care if the Fox team changes this or not. I simply don't want them to use resources that could best be directed elsewheres.

What does it mean to me if they change this behavior? Nothing! My code works as it's intended. What does it mean to some one else? Perhaps a lot, since it may break existing code.

I've taken the responsibility to deliver a product that works as I intend. If I use this "feature" who's at fault if it doesn't work the way I want, me or the Fox team?