Triaging latest Safari test failures.

Triaging latest Safari test failures.

Just re-ordering and removing bug #'s from expected supported failures.

A number of the new failures seem odd and I'm having trouble reproducing many of them. Specifically the fileapi_test appears to be failing on tests that I didn't think would be executed at all, and the performance_api_test/peformance test should only fail if it does not throw an exception.


BUG=

Committed: https://code.google.com/p/dart/source/detail?r=17421

[Emily Fortuna, 2013-01-22 20:34:28]

https://codereview.chromium.org/12051018/diff/2001/tests/html/html.status
File tests/html/html.status (left):

https://codereview.chromium.org/12051018/diff/2001/tests/html/html.status#old...
tests/html/html.status:150: # TODO(ahe, efortuna): These tests need to be
retriaged now that we're testing
Huh. I told someone in AAR to remove this TODO a long time ago in their previous
CL when they actually deleted a bunch of the Safari 5 suppressions when we
switched to Safari 6.

[Emily Fortuna, 2013-01-22 20:34:33]

lgtm