{"id":100307,"date":"2021-05-28T16:22:45","date_gmt":"2021-05-28T14:22:45","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/mozilla-obobshhila-plany-po-podderzhke-v-firefox-tretej-versii-manifesta-chrome"},"modified":"2021-05-28T16:22:45","modified_gmt":"2021-05-28T14:22:45","slug":"mozilla-obobshhila-plany-po-podderzhke-v-firefox-tretej-versii-manifesta-chrome","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hu\/blog\/news\/mozilla-obobshhila-plany-po-podderzhke-v-firefox-tretej-versii-manifesta-chrome","title":{"rendered":"A Mozilla \u00f6sszefoglalta a Firefox Chrome harmadik verzi\u00f3j\u00e1nak t\u00e1mogat\u00e1s\u00e1ra vonatkoz\u00f3 terveit","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
A Mozilla k\u00f6zz\u00e9tette a Firefox Chrome manifestum\u00e1nak harmadik verzi\u00f3j\u00e1nak megval\u00f3s\u00edt\u00e1si terv\u00e9t, amely meghat\u00e1rozza a b\u0151v\u00edtm\u00e9nyek sz\u00e1m\u00e1ra el\u00e9rhet\u0151 lehet\u0151s\u00e9geket \u00e9s er\u0151forr\u00e1sokat. A harmadik manifestum verzi\u00f3j\u00e1t kritika \u00e9rte, mivel sz\u00e1mos tartalomblokkol\u00f3 b\u0151v\u00edtm\u00e9ny m\u0171k\u00f6d\u00e9s\u00e9t zavarja \u00e9s a biztons\u00e1got vesz\u00e9lyezteti. <\/p>\n
A Firefox szinte az \u00f6sszes \u00fajdons\u00e1got \u00e9s korl\u00e1toz\u00e1st meg szeretn\u00e9 val\u00f3s\u00edtani az \u00faj manifestumban, bele\u00e9rtve a tartalomsz\u0171r\u00e9s deklarat\u00edv API-j\u00e1t (declarativeNetRequest). Azonban a Chrome-t\u00f3l elt\u00e9r\u0151en a Firefoxban nem sz\u00fcntetik meg a r\u00e9gi blokkol\u00f3 API webRequest t\u00e1mogat\u00e1s\u00e1t, legal\u00e1bbis addig, am\u00edg az \u00faj API teljes m\u00e9rt\u00e9kben nem felel meg a webRequest API-t haszn\u00e1l\u00f3 b\u0151v\u00edtm\u00e9nyfejleszt\u0151k ig\u00e9nyeinek. Ez a megk\u00f6zel\u00edt\u00e9s lehet\u0151v\u00e9 teszi a Chrome b\u0151v\u00edtm\u00e9nyeivel val\u00f3 kompatibilit\u00e1s biztos\u00edt\u00e1s\u00e1t an\u00e9lk\u00fcl, hogy megs\u00e9rten\u00e9 a webRequest API-ra \u00e9p\u00fcl\u0151 b\u0151v\u00edtm\u00e9nyek kompatibilit\u00e1s\u00e1t. <\/p>\n
Eml\u00e9keztet\u0151\u00fcl, a legf\u0151bb el\u00e9gedetlens\u00e9g az \u00faj manifestummal kapcsolatban a webRequest API csak olvashat\u00f3 m\u00f3dra val\u00f3 \u00e1t\u00e1ll\u00edt\u00e1s\u00e1hoz kapcsol\u00f3dik, amely lehet\u0151v\u00e9 tette saj\u00e1t kezel\u0151k csatlakoztat\u00e1s\u00e1t, teljes hozz\u00e1f\u00e9r\u00e9ssel a h\u00e1l\u00f3zati k\u00e9r\u00e9sekhez, \u00e9s k\u00e9pes volt \u00e9l\u0151ben m\u00f3dos\u00edtani a forgalmat. Ez az API alkalmaz\u00e1sban van az uBlock Origin \u00e9s sz\u00e1mos m\u00e1s, a nem k\u00edv\u00e1nt tartalom blokkol\u00e1s\u00e1ra \u00e9s a biztons\u00e1g n\u00f6vel\u00e9s\u00e9re szolg\u00e1l\u00f3 b\u0151v\u00edtm\u00e9nyben. A webRequest API helyett egy korl\u00e1tozott k\u00e9pess\u00e9g\u0171 API, a declarativeNetRequest ker\u00fclt aj\u00e1nl\u00e1sra, amely hozz\u00e1f\u00e9r\u00e9st biztos\u00edt a be\u00e9p\u00edtett sz\u0171r\u0151motorhoz, amely \u00f6n\u00e1ll\u00f3an kezeli a blokkol\u00e1si szab\u00e1lyokat, nem enged\u00e9lyezi a saj\u00e1t sz\u0171r\u00e9si algoritmusok haszn\u00e1lat\u00e1t, \u00e9s nem teszi lehet\u0151v\u00e9 a bonyolult, egym\u00e1sra \u00e9p\u00fcl\u0151 szab\u00e1lyok be\u00e1ll\u00edt\u00e1s\u00e1t a felt\u00e9telek f\u00fcggv\u00e9ny\u00e9ben. <\/p>\n
A Firefox a harmadik Chrome manifestum t\u00e1mogat\u00e1s\u00e1t 2021 v\u00e9g\u00e9n tervezi tesztelni, m\u00edg az \u00faj manifestum bevezet\u00e9s\u00e9t 2022 elej\u00e9re \u00fctemezik. Az \u00faj manifestum Firefoxba val\u00f3 bevezet\u00e9s\u00e9nek jellemz\u0151i k\u00f6z\u00e9 tartozik: <\/p>\n
\n
A declarativeNetRequest API biztos\u00edt\u00e1sa, de a r\u00e9gi webRequest API haszn\u00e1lat\u00e1nak lehet\u0151s\u00e9g\u00e9nek meg\u0151rz\u00e9s\u00e9vel.\n
A Cross-origin Requests Processing Update \u2014 According to the new manifest, the same power limitations that apply to the main page will also be imposed on the content processing scripts embedded in it (for instance, if the page does not have access to the geolocation API, then the extension script will not gain this access either). Part of the changes related to cross-origin request restrictions is already available for testing in nightly builds of Firefox (developed as part of the Fission project, which can be enabled in about:preferences#experimental) and is scheduled for widespread implementation in the third quarter of 2021.\n
Background pages will be replaced by service workers operating in the form of background processes. This change is not yet ready for testing.\n
Promise-based API. Firefox already supports this type of API in the 'browser.*' namespace and will transfer it to the 'chrome.*' namespace for the third version of the manifest.\n
A new granular permissions request model \u2014 an extension will no longer be able to activate for all pages at once (the 'all_urls' permission has been removed), and will only function in the context of the active tab, meaning that users will need to confirm the extension's operation for each site. Mozilla is working on strengthening access control but intends to allow users to make their own decisions about whether to allow extensions to operate with different tabs.\n