Do to lack of complaints from customers, and the fact that this behavior is actually "correct" in v1.1, we decided as a team that fixing this bug would be more trouble than it is worth.
Do to lack of complaints from customers, and the fact that this behavior is actually "correct" in v1.1, we decided as a team that fixing this bug would be more trouble than it is worth.