2011-02-17 Ilya Tikhonovsky <loislo@chromium.org>
authorloislo@chromium.org <loislo@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Thu, 17 Feb 2011 16:13:44 +0000 (16:13 +0000)
committerloislo@chromium.org <loislo@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Thu, 17 Feb 2011 16:13:44 +0000 (16:13 +0000)
commit5d2d124918d44a9e2e98805477ac2880812b041f
treed5709fcb6c7752df5f9822ac3ecb8d1688f4b5b1
parent5cd03f2713bb92e932cd7d67cdcf365059f5be90
2011-02-17  Ilya Tikhonovsky  <loislo@chromium.org>

        Reviewed by Yury Semikhatsky.

        Web Inspector: [Chromium] inspector/elements/mutate-unknown-node.html test is flaky.
        https://bugs.webkit.org/show_bug.cgi?id=54635

        It was a race condition. Sometimes Inspector was loaded before domContentLoaded event but sometimes not.
        As result it receives second setDocument and got new ids for the DOM elements.

        * http/tests/inspector/elements-test.js:
        (initialize_ElementTest.InspectorTest.dumpDOMAgentTree):
        (initialize_ElementTest):
        * inspector/elements/mutate-unknown-node-expected.txt:
        * inspector/elements/mutate-unknown-node.html:

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@78831 268f45cc-cd09-0410-ab3c-d52691b4dbfc
LayoutTests/ChangeLog
LayoutTests/http/tests/inspector/elements-test.js
LayoutTests/inspector/elements/mutate-unknown-node-expected.txt
LayoutTests/inspector/elements/mutate-unknown-node.html