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 ## Fission
   9
  10 **Affected**: Firefox >= 96
  11 **Workaround**: `fission.webContentIsolationStrategy;0`
  12
  13 With [Fission] enabled, VimFx can't inspect out-of-process iframes.
  14
  15 With Fission, sometimes called *Site Isolation*, VimFx cannot place hint markers
  16 or detect input elements inside iframes from a different domain to the top
  17 document. We will instead enter insert mode whenever such an iframe is active.
  18 Hit Escape or click outside the iframe to let VimFx re-gain control. Setting
  19 `fission.webContentIsolationStrategy` to `0` in `about:config` only disables the
  20 iframe part of Fission, but is available only since Firefox 94. Some Nightly
  21 installations were opted into Fission earlier; set `fission.autostart`
  22 to `false` if the main workaround is unavailable.
  23
  24 <!-- VimFx will probably never support Fission. Its architecture assumes that
  25 all elements can be interacted with from a single point. It would require
  26 revisiting 8a33140f and injecting a script into each frame and postMessage'ing
  27 them instead of directly accessing elements within them. -->
  28
  29 [Fission]: https://wiki.mozilla.org/Project_Fission
  30
  31 ## VimFx behaves broken after installation
  32
  33 **Affected**: all supported versions
  34 **Solution**: restart browser
  35
  36 For some as-of-yet undetermined reason, the addon sometimes breaks after
  37 installation (or upgrade)<!-- possibly Gecko internals changed and the
  38 BootstrapLoader is failing -->. Fastest way to restart Firefox is pressing
  39 `<c-s-j>` to open the browser console, then `<c-a-r>` to restart.