(In reply to comment #37) > Can someone explain why almost 2 years later this still isn't fixed?
See comment #23.
(In reply to comment #37)
> Can someone explain why almost 2 years later this still isn't fixed?
See comment #23.