URL: https://www.wunderlist.com/webapp#/lists/inbox
Browser / Version: Firefox 74.0
Operating System: Windows 10
Tested Another Browser: Yes Edge
Problem type: Site is not usable
Description: Page not loading correctly
Steps to Reproduce:
Firefox Developer v74 suddenly starting to give just a blank page for signed in lists or account settings pages on Wunderlist.com. Used to work fine. Looking at Page Sourcecode there is HTML being sent back to browser but BODY tag is completely empty of content. No such issue at the same time using Edge Chromium v80. I did clear cookies in Firefox and then re-login to Wunderlist, but still same behaviour.
View the screenshot

Browser Configuration
_From webcompat.com with ❤️_
Thanks for the report!
I'm able to reproduce the issue.
Tested with:
Browser / Version: Firefox Nightly 75.0a1 (2020-02-16)
Operating System: Windows 10 Pro
Moving to Needsdiagnosis.
ooooh! interesting
Console displays this error message: TypeError: n.toSource is not a function
which is tied to this line…
c = i.env.isFirefox() ? '(' + n.toSource() + ')()' : '(' + n.toString() + ')()';
and indeed… very recently toSource has been removed.
https://bugzilla.mozilla.org/show_bug.cgi?id=1565170
I'm pretty sure a mozregression would turn this out.
So let's move this to… contactready
in #15679 in the past they had been responsive.
@schlubbi could you help us find the right person at wunderlist that could fix the javascript for Firefox. This will hit production release in a couple of weeks, and will result in blank pages for wunderlist users.
Thanks for letting us know :heart: I'll forward this internally and hope to get it fixed ASAP.
Fix has been deployed. Confirmed the fix on Firefox 74.0b7. Thanks again for letting us know!
Thanks a lot for this swift and quick action on fixing it. appreciated <3
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue at https://webcompat.com/issues/new if you are experiencing a similar problem.
Most helpful comment
Fix has been deployed. Confirmed the fix on Firefox 74.0b7. Thanks again for letting us know!