Nope it isn't.  Current (2.4.4p4) behavior is this.

There is a patch floating around to address it though. I seem to remember it being on hold until 2.5 plans firm up though.

Reply via email to