version

To tłumaczenie jest niepełne. Pomóż przetłumaczyć ten artykuł z języka angielskiego

Typ String (ciąg znaków)
Obowiązkowe Tak
Przykład 
"version": "0.1"

Wersja rozszerzenia, sformatowana jako liczby i znaki ASCII oddzielone kropkami. Szczegółowe informacje na temat formatu wersji znajdują się na stronie Format Wersji.

Pamiętaj, że składnia zdefiniowana dla version w Chromie jest bardziej restrykcyjna niż ta używana w  przeglądarce Firefox:

  • wartości version ważne w Chrome zawsze będą ważne w Firefox
  • wartości version ważne w Firefox mogą nie być ważne w Chrome

Przykład

"version": "0.1"

Zgodność z przeglądarkami

Update compatibility data on GitHub
DesktopMobile
ChromeEdgeFirefoxOperaFirefox for Android
versionChrome Full support Yes
Notes
Full support Yes
Notes
Notes Valid Chrome versions are a subset of valid Firefox versions.
Edge Full support 14Firefox Full support 48Opera Full support YesFirefox Android Full support 48

Legend

Full support  
Full support
See implementation notes.
See implementation notes.
Powiązane tematy
  1. Browser extensions
  2. Getting started
    1. What are extensions?
    2. Your first extension
    3. Your second extension
    4. Anatomy of an extension
    5. Example extensions
    6. What next?
  3. Concepts
    1. Using the JavaScript APIs
    2. Content scripts
    3. Match patterns
    4. Working with files
    5. Internationalization
    6. Security best practices
    7. Content Security Policy
    8. Native messaging
  4. User interface
    1. User Interface
    2. Accessibility guidelines
    3. Toolbar button
    4. Address bar button
    5. Sidebars
    6. Context menu items
    7. Options page
    8. Extension pages
    9. Notifications
    10. Address bar suggestions
    11. Developer tools panels
  5. How to
    1. Intercept HTTP requests
    2. Modify a web page
    3. Insert external content
    4. Add a button to the toolbar
    5. Implement a settings page
    6. Work with the Tabs API
    7. Work with the Bookmarks API
    8. Work with the Cookies API
    9. Work with contextual identities
    10. Build a cross-browser extension
    11. Onboard, upboard, and offboard users
  6. Porting
    1. Firefox differentiators
    2. Porting a Google Chrome extension
    3. Porting a legacy Firefox extension
    4. Comparison with the Add-on SDK
    5. Comparison with XUL/XPCOM extensions
    6. Differences between API implementations
    7. Chrome incompatibilities
    8. Differences between desktop and Android
  7. Firefox workflow
    1. Developer tools
    2. Choose a Firefox version
    3. User Experience
    4. Prompt users for data and privacy consents
    5. Temporary Installation in Firefox
    6. Debugging
    7. Testing persistent and restart features
    8. Test permission requests
    9. Developing for Firefox for Android
    10. Getting started with web-ext
    11. web-ext command reference
    12. Extensions and the Add-on ID
    13. Request the right permissions
    14. Best practices for updating your extension
  8. JavaScript APIs
    1. Browser support for JavaScript APIs
  9. Manifest keys
    1. description
    2. manifest_version
    3. name
    4. version
  10. Distribution Options
  11. Themes
  12. Browser themes
    1. Browser theme concepts
    2. Using the AMO theme generator
  13. Publishing and Distribution
  14. Publishing add-ons
    1. Developer accounts
    2. Signing and distribution overview
    3. Package your extension
    4. Submit an add-on
    5. Source code submission
    6. Resources for publishers
    7. Creating an appealing listing
    8. Make money from browser extensions
    9. Promoting your extension or theme
    10. Add-on policies
    11. Developer agreement
    12. Featured add-ons
    13. Retiring your extension
  15. Distributing add-ons
    1. For sideloading
    2. For desktop apps
    3. For an enterprise
  16. Community and Support
  17. Channels
    1. Add-ons blog
    2. Add-on forums
    3. Stack Overflow
    4. Contact us