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 ## In-Content Responsive Design Mode
   9
  10 **Workaround**: `devtools.responsive.browserUI.enabled;true`
  11
  12 Launching the (`<iframe mozbrowser>` based) Responsive Design Mode breaks VimFx
  13 for this tab. The only way to recover is to copy-paste the URL into a new tab.
  14
  15 The [next generation RDM] does not have this bug; it can be enabled by switching
  16 `devtools.responsive.browserUI.enabled` to `true` in `about:config` in Firefox
  17 76 or above. There is no workaround for Firefox 68 ESR.
  18 <!-- Note: the pref exists since about fx71, but was only considered good enough
  19 for Nightly 76. -->
  20
  21 [next generation RDM]: https://mail.mozilla.org/pipermail/firefox-dev/2020-March/007397.html
  22
  23 ## Fission
  24
  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`. A [patch is in the works] that
  31 at least prevents VimFx from crashing, but for full OOP-iframe support it is way
  32 too early.
  33 <!-- As of May 2020, not even Firefox' DevTools support it, let alone other Vim
  34 like (web)extensions. Further, I suspect that to avoid a huge rewrite of how
  35 VimFx handles element discovery and interaction, we'd need cross-process-DOM
  36 APIs that just don't exist right now. -->
  37
  38 [Fission]: https://wiki.mozilla.org/Project_Fission
  39 [patch is in the works]: https://github.com/girst/VimFx/tree/fission-v2