The browser and web development fields are always evolving, and if any issues pop up affecting Mod&Dot, I'll add them to this document.
If you spot any other issues, let me know at email@example.com!
Browser Extension Compatibility
- Chrome: Working great in all recent versions and Canary.
- Firefox: The Mod&Dot browser extension is built using the web extensions standard and polyfill, but Firefox has yet to implement 2 key APIs required to listen for CSS changes (onResourceContentCommitted & getResources). So, we're just waiting on Firefox to implement them, and we'll be ready to support a Firefox extension soon after. Unfortunately the Firefox team has given no ETA.
- Safari: Unfortunately Safari does not follow the web extensions standard, so there are no plans to create a Mod&Dot Safari extension.
Actively working on fixes for these issues! Included workarounds where I have them.
- Error in DevTools Console with Mod&Dot Chrome extension installed: "DevTools failed to parse SourceMap...". This is a bug in Chrome where source maps are not loaded from extensions. Chrome only recently began reporting failure to load source maps (See chromium bug #1052872), which exposed the issue that source maps don't load from chrome extension urls (chromium bug #1053535). The error is annoying but doesn't interfere with Mod&Dot functioning properly.
- Web App Minor UI Issues:
- New comment text input doesn't autofocus
- Newly submitted comment disappears until page refresh
- ✅Fixed in Chrome extension v1.0.2! | New CSS style declarations: Chrome DevTools is placing new CSS style rules inside a separate, newly created Stylesheet. Mod&Dot currently isn't listening for that Stylesheet and might not record new style rules. Workaround: avoid writing new rules with the "+" button in the DevTools Styles panel.
- ✅Fixed in Chrome extension v1.0.2! | Chrome extension 'Continue Editing' screen, 'Delete' link does not work. The delete link leads to an infinite loading indicator. Workaround: click the 'Continue Editing' button, and once the extension shows 'Recording Edits', click 'Delete'.
- ✅Fixed in Chrome 80.0.3987.149 and up | React.js Apps: React can inject CSS using the CSSStyleSheet API, and Chrome DevTools currently has read-only access to styles injected using this method. Because of that, Mod&Dot might not record all CSS edits to React apps. More on Stack Overflow.