Come on, this is not fixed, since the bug exists in version 208 which is the latest version and was released in 2014. (See comment 4)
Come on, this is not fixed, since the bug exists in version 208 which is the latest version and was released in 2014. (See comment 4)