fix chrome 35 polymer status

fix chrome 35 polymer status
also mark one test passing on ie9 now

One test is failing due to 35 having buggy custom elements, and I guess the newest polyfill removed the workaround(s)

For now I marked status as failing, though bots will go red unfortunately when Chrome does update. I left the comment there to make it obvious to whoever sees that later.

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

[Jennifer Messerly, 2014-06-24 02:04:47]

TBR

[Jennifer Messerly, 2014-06-24 02:04:59]

Committed patchset #1 manually as r37635 (presubmit successful).

[Siggi Cherem (dart-lang), 2014-06-24 02:06:27]

lgtm

https://codereview.chromium.org/333223011/diff/1/pkg/pkg.status
File pkg/pkg.status (right):

https://codereview.chromium.org/333223011/diff/1/pkg/pkg.status#newcode402
pkg/pkg.status:402: polymer/test/entered_view_test: Fail # Chrome 35
add also entered_left_view_test ?

[Jennifer Messerly, 2014-06-24 02:10:09]

On 2014/06/24 02:06:27, Siggi Cherem (dart-lang) wrote:
> lgtm
> 
> https://codereview.chromium.org/333223011/diff/1/pkg/pkg.status
> File pkg/pkg.status (right):
> 
> https://codereview.chromium.org/333223011/diff/1/pkg/pkg.status#newcode402
> pkg/pkg.status:402: polymer/test/entered_view_test: Fail # Chrome 35
> add also entered_left_view_test ?

Hmmm. I wasn't seeing that one fail when I ran locally.