{"id":105614,"date":"2022-11-18T03:36:41","date_gmt":"2022-11-18T01:36:42","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/mozilla-nachnyot-prinimat-dopolneniya-na-baze-tretej-versii-manifesta-chrome"},"modified":"2022-11-18T03:36:41","modified_gmt":"2022-11-18T01:36:42","slug":"mozilla-nachnyot-prinimat-dopolneniya-na-baze-tretej-versii-manifesta-chrome","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hu\/blog\/news\/mozilla-nachnyot-prinimat-dopolneniya-na-baze-tretej-versii-manifesta-chrome","title":{"rendered":"A Mozilla elkezdi fogadni a Chrome harmadik verzi\u00f3s manifesztum\u00e1n alapul\u00f3 b\u0151v\u00edtm\u00e9nyeket.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
November 21, the AMO catalog (addons.mozilla.org) will start accepting and certifying extensions with a digital signature that use the third version of the Chrome manifest. These extensions will be testable in the Firefox nightly builds. Support for the third version of the manifest will be incorporated into the stable releases in Firefox 109, scheduled for January 17, 2023. Support for the second version of the manifest will be maintained in the near future, but by the end of 2023, after evaluating the dynamics of the transition to the third version, the possibility of deprecating support for the second version will be considered. <\/p>\n
A Chrome manifestum meghat\u00e1rozza a WebExtensions API haszn\u00e1lat\u00e1val k\u00e9sz\u00fclt kieg\u00e9sz\u00edt\u0151k sz\u00e1m\u00e1ra el\u00e9rhet\u0151 funkci\u00f3kat \u00e9s er\u0151forr\u00e1sokat. Az 57. verzi\u00f3t\u00f3l a Firefox teljesen \u00e1tt\u00e9rt a WebExtensions API haszn\u00e1lat\u00e1ra a kieg\u00e9sz\u00edt\u0151k fejleszt\u00e9s\u00e9ben, \u00e9s megsz\u00fcntette a XUL technol\u00f3gia t\u00e1mogat\u00e1s\u00e1t. A WebExtensions-re val\u00f3 \u00e1tt\u00e9r\u00e9s lehet\u0151v\u00e9 tette a kieg\u00e9sz\u00edt\u0151k fejleszt\u00e9s\u00e9nek egys\u00e9ges\u00edt\u00e9s\u00e9t a Chrome, Opera, Safari \u00e9s Edge platformokkal, egyszer\u0171s\u00edtette a kieg\u00e9sz\u00edt\u0151k portol\u00e1s\u00e1t k\u00fcl\u00f6nb\u00f6z\u0151 webb\u00f6ng\u00e9sz\u0151k k\u00f6z\u00f6tt, \u00e9s lehet\u0151v\u00e9 tette a teljes m\u00e9rt\u00e9k\u0171 t\u00f6bbfolyamat\u00fa m\u0171k\u00f6d\u00e9st (a WebExtensions kieg\u00e9sz\u00edt\u0151k k\u00fcl\u00f6n folyamatokban futhatnak, elszigetelten a b\u00f6ng\u00e9sz\u0151 egy\u00e9b r\u00e9szeit\u0151l). A t\u00f6bbi b\u00f6ng\u00e9sz\u0151vel val\u00f3 kieg\u00e9sz\u00edt\u0151fejleszt\u00e9s egys\u00e9ges\u00edt\u00e9se \u00e9rdek\u00e9ben a Firefox szinte teljes kompatibilit\u00e1st biztos\u00edt a Chrome m\u00e1sodik verzi\u00f3j\u00e1val. <\/p>\n
Currently, work is underway in Chrome to transition to the third version of the manifest, with support for the second version set to end in January 2024. The main goal of the changes made in the new version is to simplify the creation of secure and high-performance extensions while complicating the creation of unsafe and slow extensions. Since the third version of the manifest has faced criticism and will disrupt the functionality of many extensions for blocking unwanted content and ensuring security, Mozilla has decided to move away from ensuring full compatibility with the manifest in Firefox and to implement some changes differently. <\/p>\n
The main complaint about the third version of the manifest is the transition of the webRequest API to read-only mode, which allowed connecting custom handlers with full access to network requests and the ability to modify traffic on the fly. This API is used in uBlock Origin and many other extensions for blocking unwanted content and ensuring security. Instead of the webRequest API, the third version of the manifest proposes a limited capability API, declarativeNetRequest, which provides access to a built-in filtering engine that processes blocking rules independently, does not allow the use of custom filtering algorithms, and does not permit the setting of complex rules that overlap depending on conditions. <\/p>\n
Among the features of the new manifest implementation in Firefox: <\/p>\n
\n
\u00daj deklarat\u00edv API ker\u00fclt bevezet\u00e9sre a tartalom sz\u0171r\u00e9s\u00e9re, de a Chrome-t\u00f3l elt\u00e9r\u0151en nem sz\u0171nt meg a r\u00e9gi blokkol\u00f3 m\u0171k\u00f6d\u00e9si m\u00f3d t\u00e1mogat\u00e1sa a webRequest API-n\u00e1l.\n
A manifesztben meghat\u00e1roz\u00e1sra ker\u00fcl a h\u00e1tt\u00e9roldalak cser\u00e9je Service Worker verzi\u00f3ra, amely h\u00e1tt\u00e9rfolyamatokk\u00e9nt (Background Service Workers) m\u0171k\u00f6dik. A j\u00f6v\u0151beni kompatibilit\u00e1s \u00e9rdek\u00e9ben a Firefox t\u00e1mogatni fogja a Service Workereket, de jelenleg egy \u00faj Event Pages mechanizmust k\u00edn\u00e1l, amely ismer\u0151sebb a webfejleszt\u0151k sz\u00e1m\u00e1ra, nem ig\u00e9nyel teljes \u00e1t\u00edr\u00e1st a b\u0151v\u00edtm\u00e9nyekn\u00e9l, \u00e9s kik\u00fcsz\u00f6b\u00f6li a Service Workerekkel kapcsolatos korl\u00e1toz\u00e1sokat. Az Event Pages lehet\u0151v\u00e9 teszi a megl\u00e9v\u0151 b\u0151v\u00edtm\u00e9nyek h\u00e1tt\u00e9roldalakra val\u00f3 \u00e1t\u00edr\u00e1s\u00e1t a manifeszt harmadik verzi\u00f3j\u00e1nak k\u00f6vetelm\u00e9nyeinek megfelel\u0151en, mik\u00f6zben meg\u0151rzi hozz\u00e1f\u00e9r\u00e9st minden olyan lehet\u0151s\u00e9ghez, amely sz\u00fcks\u00e9ges a DOM-mal val\u00f3 munk\u00e1hoz. <\/li>\n
Az \u00faj granul\u00e1lt jogosults\u00e1gk\u00e9r\u0151 modell - a kieg\u00e9sz\u00edt\u0151 nem aktiv\u00e1l\u00f3dik azonnal minden oldal sz\u00e1m\u00e1ra (elt\u00e1vol\u00edtva a \u00aball_urls\u00bb jogosults\u00e1got), \u00e9s csak az akt\u00edv f\u00fcl kontextus\u00e1ban m\u0171k\u00f6dik, azaz a felhaszn\u00e1l\u00f3nak meg kell er\u0151s\u00edtenie a kieg\u00e9sz\u00edt\u0151 m\u0171k\u00f6d\u00e9s\u00e9t minden egyes webhelyen. A Firefoxban minden weboldaladatokhoz val\u00f3 hozz\u00e1f\u00e9r\u00e9s k\u00e9r\u00e9s\u00e9t opcion\u00e1lisnak tekintj\u00fck, \u00e9s a v\u00e9gs\u0151 d\u00f6nt\u00e9st a felhaszn\u00e1l\u00f3 hozza meg, aki szelekt\u00edven d\u00f6nthet arr\u00f3l, hogy mely kieg\u00e9sz\u00edt\u00e9sek f\u00e9rhetnek hozz\u00e1 az \u0151 adataihoz egy adott webhelyen.\n
A jogosults\u00e1gok kezel\u00e9s\u00e9re az interf\u00e9szben hozz\u00e1adtak egy \u00faj \u00abUnified Extensions\u00bb gombot, amelyet m\u00e1r tesztelni lehet a Firefox \u00e9jszakai buildjeiben. A gomb eszk\u00f6z\u00f6ket biztos\u00edt arra, hogy k\u00f6zvetlen\u00fcl ir\u00e1ny\u00edtsa, hogy mely weboldalakhoz f\u00e9r hozz\u00e1 minden kieg\u00e9sz\u00edt\u0151 - a felhaszn\u00e1l\u00f3 adhatja \u00e9s visszavonhatja a kieg\u00e9sz\u00edt\u0151 hozz\u00e1f\u00e9r\u00e9s\u00e9t b\u00e1rmely webhelyhez. A jogosults\u00e1gok kezel\u00e9se csak a harmadik verzi\u00f3j\u00fa manifestum alap\u00fa kieg\u00e9sz\u00edt\u0151kre vonatkozik, a m\u00e1sodik verzi\u00f3j\u00fa manifestum eset\u00e9n a weboldalakhoz val\u00f3 granul\u00e1lt hozz\u00e1f\u00e9r\u00e9s nem \u00e9rv\u00e9nyes.
<\/center> <\/li>\n
A Cross-origin k\u00e9r\u00e9sek kezel\u00e9s\u00e9nek m\u00f3dos\u00edt\u00e1sa - az \u00faj manifestum \u00e9rtelm\u00e9ben a tartalomfeldolgoz\u00f3 szkriptekre ugyanazok a jogosults\u00e1gi korl\u00e1toz\u00e1sok vonatkoznak, mint az alapoldalra, amelyre ezek a szkriptek be\u00e9p\u00fclnek (p\u00e9ld\u00e1ul, ha az oldal nem f\u00e9r hozz\u00e1 a helymeghat\u00e1roz\u00e1si API-hoz, akkor a kieg\u00e9sz\u00edt\u0151 szkript sem kap hozz\u00e1f\u00e9r\u00e9st). Ez a m\u00f3dos\u00edt\u00e1s teljes m\u00e9rt\u00e9kben megval\u00f3sult a Firefoxban. <\/li>\n
Promise alap\u00fa API. A Firefox t\u00e1mogatja ezt az API-t, \u00e9s a harmadik verzi\u00f3j\u00fa manifestumhoz fogja \u00e1thelyezni a \u00abchrome.*\u00bb n\u00e9vt\u00e9rbe. <\/li>\n
![\"A](\"\/wp-content\/uploads\/2022\/11\/62422c3bf8021866caee67b47e642d5c.jpg\")
<\/center> <\/li>\n