index.rst (6319B)
1 ================ 2 Deprecated tools 3 ================ 4 5 Over the course of DevTools development, we have added several experimental panels to try out new ideas. Not all of these have had wide adoption, and due to the cost of maintenance, seldom used panels are eventually removed. 6 7 We have created this list of deprecated or removed panels. This page documents the deprecated panels and the bugs that track their removal. Although these panels have been removed, you still have access to the old code, and there are alternative webextensions that you can try to get similar functionality. 8 9 When we deprecate a panel, we begin by getting feedback from the community to determine the impact of removing that panel. Once we have decided to remove the panel, we will provide a warning message, and finally, we will remove the panel from the codebase. 10 11 You may see a warning message, as in the following image, when trying to activate a deprecated panel: 12 13 .. image:: devtool_settings_deprecated_notice.png 14 :class: border 15 16 In addition, if you open the panel for one of these tools, you will also see a warning message about its removal. 17 18 .. image:: deprecated_tool_notice.png 19 :class: border 20 21 22 Scratchpad 23 ********** 24 25 Scratchpad was removed in Firefox 72 (`bug 1519103 <https://bugzilla.mozilla.org/show_bug.cgi?id=1519103>`_). 26 27 28 Description 29 ----------- 30 31 Scratchpad provided an environment for experimenting with JavaScript code. You can write, run, and examine the result of code that interacts with the web page. 32 33 .. image:: screen_shot_2019-08-26_at_08.08.11.png 34 :alt: Screenshot of the Scratchpad window with a deprecation message 35 36 37 Alternatives 38 ------------ 39 40 You can write multi-line JavaScript code in the Web Console Editor Mode, making it similar to the Scratchpad. The Editor Mode can be triggered clicking on the icon on the right of the console input, or with :kbd:`Ctrl` + :kbd:`B` (:kbd:`Cmd` + :kbd:`B` on macOS) 41 42 43 .. image:: editor_mode_toggle_icon.png 44 :alt: Screenshot of the Webconsole in inline mode, with the editor mode icon displayed on the right of the console input 45 46 When in Editor Mode, the :kbd:`Enter` key adds a new line in the input, and you can evaluate the expression using :kbd:`Ctrl` + :kbd:`Enter` (:kbd:`Cmd` + :kbd:`Enter` on macOS). 47 48 .. image:: screen_shot_2019-08-26_at_08.18.26.png 49 :alt: Screenshot of the Webconsole multiline input, showing an evaluation with a Syntax Error and another, correct one. 50 51 When evaluating, the input isn't cleared, which makes it possible to quickly iterate over a snippet of code. 52 53 The results are displayed in the console output, to the right of the input, providing immediate feedback. Unlike in Scratchpad, errors are properly displayed in the output with an expandable stacktrace, making it easier to debug the code you're currently writing. 54 55 You can import a Javascript file content in the console input with :kbd:`Ctrl` + :kbd:`O` (:kbd:`Cmd` + :kbd:`O` on macOS), as well as saving the console input content to a file using :kbd:`Ctrl` + :kbd:`S` (:kbd:`Cmd` + :kbd:`S` on macOS). 56 57 58 WebIDE and Connect page 59 *********************** 60 61 WebIDE was removed as of Firefox 71 (`bug 1539462 <https://bugzilla.mozilla.org/show_bug.cgi?id=1539462>`_). 62 63 64 Description 65 ----------- 66 67 WebIDE allowed you to connect the Firefox Developer Tools to remote browsers, such as Firefox for Android. It was also intended to support application development for Firefox OS. 68 69 .. image:: webide_68.png 70 71 72 Alternatives 73 ------------ 74 75 Remote debugging is available in about:debugging. Features not ported to about:debugging are: WiFi debugging for Firefox for Android, application development. Features that are planned but not ported yet: remote browser screenshots and edit remote browser configuration. More details on the `mailing-list thread <https://groups.google.com/forum/#!topic/mozilla.dev.developer-tools/aWA7JJ-TpRw>`_. 76 77 Wireless debugging over Wi-Fi is possible and documented at :ref:`about-colon-debugging-connecting-to-android-over-wi-fi`. 78 79 80 Canvas debugger 81 *************** 82 83 Bugzilla issue: `bug 1403938 <https://bugzilla.mozilla.org/show_bug.cgi?id=1403938>`_ 84 85 Removed as of Firefox 67 86 87 88 Description 89 ----------- 90 91 Canvas Debugger allowed users to inspect the canvas element and see how frequently a given function is called. It was deprecated due to lack of use. 92 93 We do not have dedicated documentation for the Canvas Debugger. 94 95 .. image:: canvas_tool.png 96 97 98 Alternatives 99 ------------ 100 101 `Spector.js <https://addons.mozilla.org/en-US/firefox/addon/spector-js/#&gid=1&pid=2>`_ is a WebExtension that can provide these features with 3D contexts.</span> 102 103 104 Web Audio editor 105 **************** 106 107 Bugzilla issue: `bug 1403944 <https://bugzilla.mozilla.org/show_bug.cgi?id=1403944>`_ 108 109 Removed as of Firefox 67 110 111 112 Description 113 ----------- 114 115 The Web Audio Editor allowed you to examine an audio context constructed in the page and provided a visualization of its graph. This gave a high-level view of its operation, and enabled you to ensure that all the nodes are connected in the way you expect. It was possible to edit the AudioParam properties for each node in the graph. Some non-AudioParam properties, like an OscillatorNode's type property, were displayed and editable as well. It was deprecated due to lack of use. 116 117 More details about the :doc:`Web Audio Editor <../web_audio_editor/index>` 118 119 .. image:: webaudio_tool.png 120 :class: border 121 122 123 Alternatives 124 ------------ 125 126 Alternatives include the `AudioN <https://github.com/google/audion>`_ and https://github.com/spite/WebAudioExtension WebExtensions. 127 128 129 Shader editor 130 ************* 131 132 Bugzilla issue: `bug 1342237 <https://bugzilla.mozilla.org/show_bug.cgi?id=1342237>`_ 133 134 Removed as of Firefox 67 135 136 137 Description 138 ----------- 139 140 The Shader Editor allowed users to examine and edit the source of the WebGL vertex and fragment shaders. It was deprecated due to low usage and maintenance costs. 141 142 :doc:`Shader Editor <../shader_editor/index>` 143 144 .. image:: shadereditor_tool.png 145 :class: border 146 147 148 Alternatives 149 ------------ 150 151 An alternative to this panel is this extension: https://github.com/spite/ShaderEditorExtension, or `Spector.js <https://addons.mozilla.org/en-US/firefox/addon/spector-js/#&gid=1&pid=2>`_ also supports a Shader Editor that requires a library to use a shader reloader hook. Currently only the Babylon library does.