On Tue, Oct 15, 2013 at 11:46 PM, Chris McMahon <[email protected]>wrote:
> There is another case that I believe happens in Chrome 29 but not Chrome 30 Since Chrome updates magically in the background, is there a reason to invest time in investigating bug that happens only in a previous version of Chrome? Do you think it could also happen in Chrome 30? Željko
_______________________________________________ QA mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/qa
