(In reply to comment #71)
> There is still no reaction from any developer for the complete buggy behavior
> introduced in 2.0.0.0rc1
Do you mean (b) or (c) (or both) from comment 70? (b) looks like old behavior to me, but I could be misremembering; I don't recall (c) being a problem.
I don't see either issue in 2.0 final.
(In reply to comment #71)
> There is still no reaction from any developer for the complete buggy behavior
> introduced in 2.0.0.0rc1
Do you mean (b) or (c) (or both) from comment 70? (b) looks like old behavior to me, but I could be misremembering; I don't recall (c) being a problem.
I don't see either issue in 2.0 final.