The tabs.Tab object properly sets the value of the highlighted property. The tabs.highlight API accepts an array of tab indices that should be selected. The tabs.onHighlighted event now handles multiple selected tabs in Firefox. In concert with this user-facing change, extensions are also gaining support for multi-select tabs in Firefox 63. It is a very convenient feature that power users will appreciate. This allows you to easily highlight a set of tabs and move, reload, mute or close them, or drag them into another window. One of the big changes coming in Firefox 63 is the ability to select multiple tabs simultaneously by either Shift- or CTRL-clicking on tabs beyond the currently active tab. 
Support for the more general clipboard.read() and clipboard.write() API are awaiting clarity around the W3C spec and will be added in a future release. In addition, the text versions of the API are the only ones available in Firefox 63. This preserves the same use conditions as document.execCommand(“paste”).
There currently is no way to expose the clipboard.readText API to web content since no permission system exists for it outside of extensions.
clipboard.readText is available to extensions only and requires the clipboardRead permission. This preserves the same use conditions as document.execCommand(“copy”). Extensions can request the clipboardWrite permission if they want to use clipboard.writeText outside of a user-initiated event callback. clipboard.writeText is available to secure contexts and extensions, without requiring any permissions, as long as it is used in a user-initiated event callback. When using the clipboard, extensions can use standard the WebAPI to read and write to the clipboard using () and (). Starting with this release, parts of the official W3C draft spec for asynchronous clipboard API is now available to extensions. Having to use execCommand() to cut, copy and paste always felt like a workaround rather than a valid way to interact with the clipboard. Less Kludgy Clipboard AccessĪ consistent source of irritation for developers since the WebExtensions API was introduced is that clipboard access is not optimal. I’ve tried to link to MDN where possible, and more information will appear in the weeks leading up to the public release of Firefox 63. Note: due to the large volume of changes in this release, the MDN documentation is still catching up. We are humbled and grateful for your support of Firefox and the open web. Volunteer contributors landed over 25% of all the features and bug fixes for WebExtensions in Firefox 63, a truly remarkable effort. 
Firefox refresh page addon upgrade#
All told, this is the biggest upgrade to the WebExtensions API since the release of Firefox Quantum.Īn upgrade this large would not have been possible in a single release without the hard work of our Mozilla community. There are some important new API, some major enhancements to existing API, and a large collection of miscellaneous improvements and bug fixes. Firefox 63 is rolling into Beta and it’s absolutely loaded with new features for extensions.
0 kommentar(er)
