![]() See ( Firefox bug 1855763 and Firefox bug 390936) for more details. The non-standard CSS zoom property is enabled in the Nightly release and lets you magnify an element similar to the transform property, but it affects the layout size of the element. You can alternatively use the scroll() functional notation with animation-timeline to indicate that a scrollbar axis in an ancestor element will be used for the timeline.įor more information, see Firefox bug 1807685, Firefox bug 1804573, Firefox bug 1809005, Firefox bug 1676791, Firefox bug 1754897, and Firefox bug 1737918. The longhand and shorthand properties are both available behind the preference. When using the scroll-timeline shorthand property, the order of the property values must be scroll-timeline-name followed by scroll-timeline-axis. The scroll timeline can then be associated with an animation by setting the animation-timeline property to the name value defined using scroll-timeline-name. The scroll-timeline-name and scroll-timeline-axis properties (and the scroll-timeline shorthand property) allow you to specify that a particular scrollbar in a particular named container can be used as the source for a scroll-driven animation. ![]() Persistent background scripts remain loaded for the lifetime of the extension.Earlier called "scroll-linked animations", a scroll-driven animation depends on the scroll position of a scrollbar instead of time or some other dimension. These scripts can be persistent or non-persistent. This example is in the webextensions-examples repository.īackground scripts enable an extension to monitor and react to events in the browser, such as navigating to a new page, removing a bookmark, or closing a tab. We use the notify-link-clicks-i18n extension example to illustrate the debugging features relevant to background scripts. It occasionally contains more detailed information about errors reported to your extension. This console contains messages from the whole browser, including your and other extensions. Log messages not associated with an extension script, such as the stderr output of the nativeMessaging APIĬan only be viewed via the Browser Console. Log messages from content scripts can be viewed in the developer tools of the tab where the content script runs instead of about:debugging, see: The Developer tools toolbox at about:debugging shows log messages from extension scripts. Log messages can usually be viewed via the Console of the context where the script runs. with the Console API or by triggering (uncaught) errors. Your extension can generate log messages, e.g. You can now drag the toolbox tab to a separate window, so you can place it alongside the window where you're executing the extension. You do this using the split console, press esc to activate this mode. There is an overview of all relevant places to look for messages at Viewing log output.įor much of the debugging work, it's useful to be able to view Console with Inspector or Debugger. This console shows messages from your background script and extension pages other logs may appear elsewhere. Storage to view details of data stored by the extension. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |