@melvincarvalho Thanks for the report. The extension would only mess things up if it is triggered, ie. the user activates it on a web page and some CSS or JS across what the web page loads and what dokieli loads has some conflict somewhere. I believe that's what you're experiencing. If the extension is not triggered, there is no issue here. What was your intention in activating the extension on that webpage? I don't quite understand what "unrelated web pages" mean. Having said that, the dokieli extension is not expected to be fully smooth on all web pages out there. Factoring in all the complexities (for all webpages) is indeed challenging. We're however making the effort to identify what they are as we go, and iron them out as reasonably as possible - more like on a need to basis. It'd be great if you can create an issue on the exact issue you've experienced, URL of the webpage in question, and how to reproduce. Thanks.