Revert 2.5 CLs that relate to pulling Extension port management out of messaging.js.
The first is 1be16298: "Clear the onMessage and onDisconnect listeners when their Extension Port is destroyed." which was a fix to the original patch. The second, original patch is 32b3a84b: "Move the Extension Port implementation out of messaging.js into its own file port.js." This is the key patch, which has caused no end of trouble. The goal was noble: to fix the myriad of bugs which messaging has due to being written in JS not C++. It appears that the moral of the story is: this is impossible, and the hole we've dug in over the last 5 years cannot be recovered from (without a complete rewrite, I suppose). The last .5 of a patch was one of the tests added in b9dca054 which will no longer pass. BUG=486715,477323,475536 R=rockot@chromium.org Review URL: https://codereview.chromium.org/1131043003 Cr-Commit-Position: refs/heads/master@{#329571}
Showing
Please register or sign in to comment