Sorry, this fell through the cracks... I'm activity working on bug 1593937 which will get rid of this code. Similar issue might happen in the new code, so it would be handy to better understand what is wrong here. Now that I read the exception more carefully `"currentContext.getChildren is not a function"` `currentContext` isn't undefined, but it is rather the `getChildren` attribute which is. I'm wondering if Nicolas only hit a rebase issue, when testing Firefox in between two builds when `getChildren` has been renamed to `children`. If that is that, the issue may not be related to this code after all. Mike, Morgan, are you seeing any error in your terminal? Or in the Browser Console?
Bug 1615412 Comment 13 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Sorry, this fell through the cracks... I'm activity working on bug 1593937 which will get rid of this code. Similar issue might happen in the new code, so it would be handy to better understand what is wrong here. Now that I read the exception more carefully `"currentContext.getChildren is not a function"` `currentContext` isn't undefined, but it is rather the `getChildren` attribute which is not defined. I'm wondering if Nicolas only hit a rebase issue, when testing Firefox in between two builds when `getChildren` has been renamed to `children`. If that is that, the issue may not be related to this code after all. Mike, Morgan, are you seeing any error in your terminal? Or in the Browser Console?