Wednesday, December 11, 2019
1 change · master
Resolved issues and error corrections
This fix prevents the web client from reacting to page navigation changes before its initial user information has finished loading. It improves startup reliability and avoids a timing issue that caused automated click-through testing to fail.
Original PR description
Before this commit, after the introduction of OWL, for some reason, maybe because the session is ready earlier or later, the webclient is opening the first app sightly earlier than before, making it too early. The click_all failed actually because, in the initialization of the webclient, * it does a read on read user, protected by a drop_previous * it tries to start the first applictaion, when this happens, the hash changes ==> because the hash changes, it tries to open an application, with is also protected by the same drop previous, this discarding the result of the read and preventing the then callbacks of the read to happen. After this commit, the handler that listen to the hash changes is added after the read is done. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr