Debugging, good news and bad news
3 views
Skip to first unread message
Ean Schuessler
May 18, 2017, 2:34:24 PM5/18/17
to FilterBubbler Dev
In the FBBL-WE-5 branch I've gotten things basically running in Chrome. The good news is that SourceMaps work and you can successfully set breakpoints. The bad news is they only seem to work for UI popups and you don't even get console log output for background scripts. This is in version 58.0.3029.81. I need to try nightly chrome builds and see how they work.
Since Firefox gives you console output from background scripts this seems to mean that it is actually the better choice for doing WebExtensions development at this time. Since it looks like I'm not going to get a sourcemapped debugging environment either way I rolled up my sleeves and started sprinkling debug statements into my code and the Redux-WebExt bridge. That output gave me a better understanding of what the bridge is trying to do (even though I don't know if it entirely makes sense) and I changed the way the Redux-Form actions get bridged from the pop-up to the background context. This got things working the way we would expect them to.
So, hooray! I'm actually back to writing core FilterBubbler logic instead of wrestling with basic plumbing. We now have a functional React/Redux platform in WebExtensions space with the Material UI look and feel. I'm going to get the basic bayes classifier working again and then merge branch 5. I believe I can also close issue 6.
I'll get this all written up in a blog entry in the next day or so. It should provide material for one or maybe several great blog articles. If you want any more detail please feel free to fire some questions off here.
Reply all
Reply to author
Forward
0 new messages