Relax call count check in `FrameObserver` tests
An `onDocumentReady` test was failing in current versions of Chrome, with the callback being invoked twice with the same error instead of once. This can happen with this sequence of events: 1. Watched frame fires an "unload" event. This starts a polling timer. 2. The timer fires and the callback is invoked with a cross-origin error 3. Frame fires "load" event, and the callback is invoked a second time with a cross-origin error 4. The test's "load" event handler is run It is not a problem for current callers of `onDocumentReady` if the callback fires twice, so just relax the check in the tests.
Showing
Please register or sign in to comment