commit 49eecd21d1c32fa8afedd20fe6f520633fd96747
author loislo@chromium.org <loislo@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc> Thu Feb 17 16:13:44 2011 +0000
committer loislo@chromium.org <loislo@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc> Thu Feb 17 16:13:44 2011 +0000
tree d5709fcb6c7752df5f9822ac3ecb8d1688f4b5b1
parent fb9c2de04e0261c11354cca8be621a70d6d44193

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: http://svn.webkit.org/repository/webkit/trunk@78831 268f45cc-cd09-0410-ab3c-d52691b4dbfc