documentation/known-bugs.md

   1 # Known Bugs
   2
   3 Given that VimFx operates outside the bounds of what Mozilla supports, there
   4 are some things that VimFx doesn't play along with well. This page lists
   5 problems that affect VimFx when run on versions of Firefox we support
   6 (latest *Release* and *ESR* versions).
   7
   8 ## Responsive Design Mode
   9
  10 **Affected**: Firefox <= 78
  11 **Workaround**: `devtools.responsive.browserUI.enabled;true`
  12
  13 Launching the (old) Responsive Design Mode breaks VimFx for this tab. The only
  14 way to recover is to copy-paste the URL into a new tab.
  15
  16 The [new RDM] does not have this bug; it can be enabled by switching
  17 `devtools.responsive.browserUI.enabled` to `true` in `about:config` in Firefox
  18 78 ESR. There is no workaround for Firefox 68 ESR.
  19
  20 [new RDM]: https://mail.mozilla.org/pipermail/firefox-dev/2020-March/007397.html
  21
  22 ## Fission
  23
  24 **Affected**: (future versions)
  25 **Workaround**: `fission.autostart;false`
  26
  27 With [Fission] enabled, VimFx can't inspect out-of-process iframes.
  28
  29 Fission is not (yet) turned on by default, but can be disabled by switching
  30 `fission.autostart` to `false` in `about:config`. With Fission, VimFx cannot
  31 place hint markers or determine whether an editable element is active in iframes
  32 from a different domain to the top document. We will instead enter insert mode
  33 whenever such an iframe is active (so input elements are usable; click outside
  34 the iframe to let VimFx re-gain control).
  35
  36 <!-- For full OOP-iframe support it is way too early.
  37 As of May 2020, not even Firefox' DevTools support it, let alone other Vim
  38 like (web)extensions. Further, I suspect that to avoid a huge rewrite of how
  39 VimFx handles element discovery and interaction, we'd need cross-process-DOM
  40 APIs that just don't exist right now. -->
  41
  42 [Fission]: https://wiki.mozilla.org/Project_Fission
  43
  44 ## VimFx behaves broken after installation
  45
  46 **Affected**: all supported versions
  47 **Solution**: restart browser
  48
  49 For some as-of-yet undetermined reason, the addon sometimes breaks after
  50 installation (or upgrade)<!-- possibly Gecko internals changed and the
  51 BootstrapLoader is failing -->. Fastest way to restart Firefox is pressing
  52 `<Ctrl-Shift-j>` to open the browser console, then `<Ctrl-Alt-r>` to restart.
  53 Alternatively, navigate to `about:profiles` and hit the *Restart normally*
  54 button.