{"id":88912,"date":"2020-07-16T07:42:12","date_gmt":"2020-07-16T05:42:12","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/reliz-chrome-84"},"modified":"2020-07-16T07:42:12","modified_gmt":"2020-07-16T05:42:12","slug":"reliz-chrome-84","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/news\/reliz-chrome-84","title":{"rendered":"L\u00ebshimi i Chrome 84","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Kompania Google <noindex><a rel=\"nofollow\" href=\"https:\/\/support.google.com\/chrome\/a\/answer\/7679408#84\">ka prezantuar<\/a><\/noindex> l\u00ebshimi i shfletuesit web <noindex><a rel=\"nofollow\" href=\"http:\/\/www.google.com\/chrome\">Chrome 84<\/a><\/noindex>. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromium.org\/developers\/calendar\">\u00ebsht\u00eb n\u00eb dispozicion<\/a><\/noindex> nj\u00eb publikim stabil i projektit t\u00eb lir\u00eb <noindex><a rel=\"nofollow\" href=\"http:\/\/dev.chromium.org\/\">Chromium<\/a><\/noindex>, q\u00eb sh\u00ebrben si baza e Chrome. Shfletuesi Chrome <noindex><a rel=\"nofollow\" href=\"https:\/\/code.google.com\/p\/chromium\/wiki\/ChromiumBrowserVsGoogleChrome\">dallohet<\/a><\/noindex> p\u00ebrdorimin e logove t\u00eb Google, pranin\u00eb e sistemit p\u00ebr d\u00ebrgimin e njoftimeve n\u00eb rast rr\u00ebzimi, mund\u00ebsin\u00eb p\u00ebr t\u00eb ngarkuar modulin Flash sipas k\u00ebrkes\u00ebs, module p\u00ebr riprodhimin e p\u00ebrmbajtjes s\u00eb mbrojtur (DRM), sistemin automatik t\u00eb instalimit t\u00eb p\u00ebrdit\u00ebsimeve dhe transmetimin gjat\u00eb k\u00ebrkimit <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=26822\">t\u00eb parametrave RLZ<\/a><\/noindex>. L\u00ebshimi i ardhsh\u00ebm i Chrome 85 \u00ebsht\u00eb planifikuar p\u00ebr 25 gusht.<\/p>\n<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/support.google.com\/chrome\/a\/answer\/7679408#84\">Main<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/productforums.google.com\/forum\/#!forum\/chrome\">ndryshime<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.chromium.org\/2020\/05\/chrome-84-beta-web-otp-web-animations.html\">n\u00eb<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/2020\/\">Chrome<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/v8.dev\/blog\/v8-release-84\">84<\/a><\/noindex>:<\/p>\n<ul>\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=51599\">\u00c7aktivizuar<\/a><\/noindex>  mb\u00ebshtetje p\u00ebr protokollet TLS 1.0 dhe TLS 1.1. P\u00ebr t\u2019u qasje ndaj faqeve t\u00eb internetit p\u00ebrmes nj\u00eb kanali t\u00eb sigurt, serveri duhet t\u00eb ofroj\u00eb mb\u00ebshtetje p\u00ebr t\u00eb pakt\u00ebn TLS 1.2, ndryshe shfletuesi tani do t\u00eb paraqes\u00eb nj\u00eb gabim. Sipas Google, aktualisht rreth 0.5% e ngarkimeve t\u00eb faqeve t\u00eb internetit vazhdojn\u00eb t\u00eb realizohen duke p\u00ebrdorur versione t\u00eb vjetra TLS. \u00c7aktivizimi \u00ebsht\u00eb kryer n\u00eb p\u00ebrputhje me <noindex><a rel=\"nofollow\" href=\"https:\/\/datatracker.ietf.org\/doc\/draft-ietf-tls-oldversions-deprecate\/\">rekomandimeve<\/a><\/noindex>  IETF (Internet Engineering Task Force). Arsyetimi p\u00ebr heqjen e TLS 1.0\/1.1 \u00ebsht\u00eb mungesa e mb\u00ebshtetjes p\u00ebr \u00e7el\u00ebsa modern\u00eb (p\u00ebr shembull ECDHE dhe AEAD) dhe k\u00ebrkesa p\u00ebr mb\u00ebshtetje t\u00eb \u00e7el\u00ebsave t\u00eb vjet\u00ebr, besueshm\u00ebria e t\u00eb cil\u00ebve n\u00eb faz\u00ebn aktuale t\u00eb zhvillimit t\u00eb teknologjis\u00eb kompjuterike \u00ebsht\u00eb v\u00ebn\u00eb n\u00eb dyshim (p\u00ebr shembull, k\u00ebrkesa p\u00ebr mb\u00ebshtetje TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA, p\u00ebr verifikimin e integritetit dhe autentikimit p\u00ebrdoret MD5 dhe SHA-1). Konfigurimi, q\u00eb lejon rikthimin n\u00eb TLS 1.0\/1.1 do t\u00eb mbahet deri n\u00eb janar 2021.\n<li class=\"l\"> \u00cbsht\u00eb siguruar bllokimi i <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=52329\">ngarkesave t\u00eb pasigurta<\/a><\/noindex> (pa enkriptim) t\u00eb skedar\u00ebve ekzekutiv\u00eb dhe \u00ebsht\u00eb shtuar nj\u00eb paralajm\u00ebrim p\u00ebr ngarkimin e pasigurt t\u00eb arkivave. M\u00eb von\u00eb, planifikohet gradualisht t\u00eb nd\u00ebrpritet plot\u00ebsisht mb\u00ebshtetja p\u00ebr ngarkimin e skedar\u00ebve pa p\u00ebrdorimin e enkriptimit. Bllokimi \u00ebsht\u00eb realizuar, pasi ngarkimi i skedar\u00ebve pa enkriptim mund t\u00eb p\u00ebrdoret p\u00ebr t\u00eb kryer veprime keqdash\u00ebse duke manipuluar p\u00ebrmbajtjen gjat\u00eb sulmeve MITM.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5995832180473856\">Shtuar<\/a><\/noindex> mb\u00ebshtetje fillestare <noindex><a rel=\"nofollow\" href=\"https:\/\/wicg.github.io\/client-hints-infrastructure\/\">identifikuesi<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/httpwg.org\/http-extensions\/client-hints.html\">Client Hints<\/a><\/noindex>, q\u00eb po zhvillohet si nj\u00eb alternativ\u00eb p\u00ebr headerin User-Agent. Mekanizmi Client Hints ofron si z\u00ebvend\u00ebsues User-Agent nj\u00eb s\u00ebr\u00eb headerash \u201cSec-CH-UA-*\u201d, t\u00eb cilat lejojn\u00eb organizimin e ofrimit selektiv t\u00eb t\u00eb dh\u00ebnave p\u00ebr parametrat specifik\u00eb t\u00eb shfletuesit dhe sistemit (versioni, platforma etj.) vet\u00ebm pas k\u00ebrkes\u00ebs nga serveri. P\u00ebrdoruesi ka mund\u00ebsin\u00eb t\u00eb p\u00ebrcaktoj\u00eb cilat parametra jan\u00eb t\u00eb lejuesh\u00ebm p\u00ebr t'u ofruar dhe t\u00eb ofroj\u00eb n\u00eb m\u00ebnyr\u00eb selektive k\u00ebt\u00eb informacion pronar\u00ebve t\u00eb faqeve t\u00eb internetit. Me p\u00ebrdorimin e Client Hints, identifikuesi nuk d\u00ebrgohet si parazgjedhje pa nj\u00eb k\u00ebrkes\u00eb t\u00eb qart\u00eb, gj\u00eb q\u00eb e b\u00ebn t\u00eb pamundur identifikimin pasiv (si parazgjedhje shfaqet vet\u00ebm emri i shfletuesit). <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5704553745874944\">Puna<\/a><\/noindex> sip\u00ebr <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=52182\">unifikimi i User-Agent<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/groups.google.com\/a\/chromium.org\/forum\/m\/#!msg\/blink-dev\/-2JIRNMWJ7s\/yHe4tQNLCgAJ\">\u00ebsht\u00eb shtyr\u00eb<\/a><\/noindex> deri vitin tjet\u00ebr.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromium.org\/updates\/same-site\">Ka vazhduar<\/a><\/noindex> aktivizimi<br \/>\nm\u00eb t\u00eb rrepta <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=52189\">kufizim<\/a><\/noindex> t\u00eb transferimit t\u00eb Cookie nd\u00ebrsaj, i cili ishte <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.chromium.org\/2020\/05\/resuming-samesite-cookie-changes-in-july.html\">anuluar<\/a><\/noindex> p\u00ebr shkak t\u00eb COVID-19. P\u00ebr k\u00ebrkesat e pa-HTTPS \u00ebsht\u00eb e ndaluar p\u00ebrpunimi i Cookie-ve nga pal\u00ebt e treta, t\u00eb cilat vendosen gjat\u00eb aksesit n\u00eb faqe t\u00eb ndryshme nga domeni i faqes aktuale. Cookie-t e tilla p\u00ebrdoren p\u00ebr t\u00eb ndjekur l\u00ebvizjet e p\u00ebrdoruesve midis faqeve n\u00eb kodin e rrjeteve t\u00eb reklamave, vegzave t\u00eb rrjeteve sociale dhe sistemeve t\u00eb analizave web. <\/p>\n<p>Kujtojm\u00eb se p\u00ebr menaxhimin e transmetimit t\u00eb Cookie-ve p\u00ebrdoret atributi SameSite q\u00eb tregohet n\u00eb titullin Set-Cookie, i cili p\u00ebr default do t\u00eb vendoset n\u00eb vler\u00ebn \u00abSameSite=Lax\u00bb, e cila kufizon d\u00ebrgimin e Cookie-ve p\u00ebr subk\u00ebrkesa nd\u00ebrfaq\u00ebsore, si\u00e7 \u00ebsht\u00eb k\u00ebrkesa p\u00ebr nj\u00eb imazh ose shkarkimi i p\u00ebrmbajtjes p\u00ebrmes iframe nga nj\u00eb faqe tjet\u00ebr. Faqet mund t\u00eb ri-definojn\u00eb modin e p\u00ebrdorur p\u00ebr default SameSite duke vendosur me qart\u00ebsi, n\u00eb momentin e vendosjes s\u00eb Cookie-ve, vler\u00ebn SameSite=None. Megjithat\u00eb, vlera SameSite=None p\u00ebr Cookie-t mund t\u00eb vendoset vet\u00ebm n\u00eb modin Secure (vepron p\u00ebr lidhjet p\u00ebrmes HTTPS). Ndryshimi do t\u00eb zbatohet n\u00eb m\u00ebnyr\u00eb t\u00eb fazuar, fillimisht p\u00ebr nj\u00eb p\u00ebrqindje t\u00eb vog\u00ebl p\u00ebrdoruesish, dhe m\u00eb pas duke zgjeruar gradualisht p\u00ebrmbushjen.<\/p>\n<li class=\"l\"> Implementim eksperimental i shtuar <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=52957\">bllokuesit t\u00eb reklamave t\u00eb r\u00ebnd\u00eb<\/a><\/noindex>, i cili mund t\u00eb aktivizohet p\u00ebrmes cil\u00ebsimit \u00abchrome:\/\/flags\/#enable-heavy-ad-intervention\u00bb. Bllokuesi lejon \u00e7aktivizimin automatik t\u00eb blloqeve reklamative iframe pas kalimit t\u00eb vlerave kufitare t\u00eb trafikut dhe ngarkes\u00ebs n\u00eb CPU. Bllokimi do t\u00eb aktivizohet n\u00ebse n\u00eb rrjedh\u00ebn kryesore \u00ebsht\u00eb shpenzuar m\u00eb shum\u00eb se 60 sekonda koh\u00eb procesori n\u00eb total ose 15 sekonda brenda nj\u00eb intervali 30-sekond\u00ebsh (p\u00ebrdor 50% t\u00eb burimeve m\u00eb shum\u00eb se 30 sekonda), si dhe kur jan\u00eb shkarkuar m\u00eb shum\u00eb se 4 MB t\u00eb dh\u00ebnash p\u00ebrmes rrjetit.\n<p>Bllokimi do t\u00eb aktivizohet vet\u00ebm n\u00ebse deri n\u00eb momentin e kalimit t\u00eb kufijve p\u00ebrdoruesi nuk ka nd\u00ebrvepruar me bllokun reklamativ (p\u00ebr shembull, nuk ka klikuar mbi t\u00eb), \u00e7ka duke pasur parasysh kufizimin n\u00eb trafik do t\u00eb lejoj\u00eb bllokimin e autoreproduksionit t\u00eb videove voluminoze n\u00eb reklama pa aktivizimin e qart\u00eb t\u00eb riprodhimit nga p\u00ebrdoruesi. Masat e propozuara do t'i lirojn\u00eb p\u00ebrdoruesit nga reklamat me implementim joefektiv t\u00eb kodit ose aktivitet parazitar t\u00eb q\u00ebllimsh\u00ebm (p\u00ebr shembull, q\u00eb realizojn\u00eb minimin). Sipas statistikave t\u00eb Google, reklamat q\u00eb bien n\u00ebn kriteret e bllokimit p\u00ebrb\u00ebjn\u00eb vet\u00ebm 0.30% t\u00eb t\u00eb gjith\u00eb blloqeve reklamative, por megjithat\u00eb k\u00ebto reklama konsumojn\u00eb 28% t\u00eb burimeve CPU dhe 27% t\u00eb trafikut nga t\u00eb gjith\u00eb volumit t\u00eb reklamave. <\/p>\n<li class=\"l\"> \u00cbsht\u00eb kryer nj\u00eb pun\u00eb p\u00ebr t\u00eb reduktuar konsumimin e burimeve CPU kur dritarja e shfletuesit nuk ndodhet n\u00eb fush\u00ebn e dukshme t\u00eb p\u00ebrdoruesit. Chrome tani kontrollon n\u00ebse dritarja e shfletuesit \u00ebsht\u00eb e mbuluar nga dritare t\u00eb tjera dhe p\u00ebrjashton vizatimin e piksel\u00ebve n\u00eb zonat e mbulimit. Aktivizimi i funksionit t\u00eb ri do t\u00eb b\u00ebhet gradualisht: p\u00ebr disa p\u00ebrdorues optimizimi do t\u00eb aktivizohet n\u00eb Chrome 84, nd\u00ebrsa p\u00ebr t\u00eb tjer\u00ebt n\u00eb Chrome 85.\n<li class=\"l\"> Aktivizimi i mbrojtjes nga <noindex><a rel=\"nofollow\" href=\"https:\/\/support.google.com\/webtools\/answer\/9799829\">njoftimet e bezdisshme<\/a><\/noindex>, si shembuj, k\u00ebrkesat p\u00ebr t\u00eb marr\u00eb njoftime push. Duke qen\u00eb se k\u00ebto k\u00ebrkesa nd\u00ebrpresin pun\u00ebn e p\u00ebrdoruesit dhe t\u00ebrheqin v\u00ebmendjen n\u00eb veprimet n\u00eb dialogjet e konfirmimit, n\u00eb vend t\u00eb nj\u00eb dialogu t\u00eb ve\u00e7ant\u00eb n\u00eb shiritin e adres\u00ebs do t\u00eb shfaqet nj\u00eb informacion i p\u00ebrkujtuesh\u00ebm q\u00eb nuk k\u00ebrkon veprime nga p\u00ebrdoruesi me nj\u00eb paralajm\u00ebrim mbi bllokimin e k\u00ebrkes\u00ebs p\u00ebr autorizim, i cili automatikisht paketohet n\u00eb nj\u00eb indikator me nj\u00eb imazh t\u00eb nj\u00eb zilje t\u00eb hequr. Duke klikuar mbi indikatorin, mund t\u00eb aktivizoni ose refuzoni autorizimin e k\u00ebrkuar n\u00eb \u00e7do moment t\u00eb p\u00ebrshtatsh\u00ebm.\n<\/p>\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/lh6.googleusercontent.com\/pM2hu9foX9242Vc4AOuz_ntSYy50F_Lb_61o7-s-cCGT4l8sS08fO40JHdKM-6q0afoRqZmOE1dXwJI5kPNs-kwB_KJPosvLLqklNQN4yren24JCG67MwY926uM4IU7vuqV4JqeU\"><img decoding=\"async\" alt=\"L\u00ebshimi i Chrome 84\" src=\"\/wp-content\/uploads\/2020\/07\/b327d04760987f54372a2ff4d057eb2e.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> \u00cbsht\u00eb siguruar mbajtja mend e zgjedhjes s\u00eb p\u00ebrdoruesit kur hapen trajtuesit e protokolleve t\u00eb jashtme \u2014 p\u00ebrdoruesi mund t\u00eb zgjedh\u00eb \u2018gjithmon\u00eb lejo p\u00ebr k\u00ebt\u00eb site\u2019 p\u00ebr nj\u00eb trajtues t\u00eb caktuar dhe shfletuesi do ta mbaj\u00eb mend k\u00ebt\u00eb vendim t\u00eb lidhur me sitin aktual.\n<li class=\"l\"> \u00cbsht\u00eb shtuar mbrojtja nga ndryshimi i cil\u00ebsimeve t\u00eb p\u00ebrdoruesit pa p\u00eblqimin e qart\u00eb. N\u00ebse nj\u00eb shtes\u00eb ndryshon motorin e k\u00ebrkimit t\u00eb paracaktuar ose faqen q\u00eb shfaqet p\u00ebr sked\u00ebn e re, shfletuesi tani do t\u00eb nxjerr\u00eb nj\u00eb dialog me propozimin p\u00ebr t\u00eb konfirmuar veprimin e specifikuar ose p\u00ebr t\u00eb anuluar ndryshimin.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/4926989725073408\">Vazhdon<\/a><\/noindex> implementimi i mbrojtjes nga ngarkimi i p\u00ebrmbajtjes multimedia t\u00eb p\u00ebrzier (kur n\u00eb nj\u00eb faqe HTTPS ngarkohen burime p\u00ebrmes protokollit http:\/\/). N\u00eb faqet e hapura p\u00ebrmes HTTPS, tani automatikisht do t\u00eb z\u00ebvend\u00ebsohen lidhjet \u2018http:\/\/\u2019 me \u2018https:\/\/\u2019 n\u00eb blloqet e lidhura me ngarkimin e imazheve (m\u00eb par\u00eb u z\u00ebvend\u00ebsuan skemat dhe iframe-t, auto-z\u00ebvend\u00ebsimi i burimeve audio dhe video pritet n\u00eb versionin e ardhsh\u00ebm). N\u00ebse nj\u00eb imazh nuk \u00ebsht\u00eb i disponuesh\u00ebm p\u00ebr https, ngarkimi i tij bllokohet (mund t\u00eb sh\u00ebnohet bllokimi manualisht p\u00ebrmes menus\u00eb, e cila \u00ebsht\u00eb e aksesueshme p\u00ebrmes simbolit t\u00eb ky\u00e7it n\u00eb shiritin e adres\u00ebs).\n<li class=\"l\"> \u00cbsht\u00eb shtuar mb\u00ebshtetje p\u00ebr API <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/web-otp\/\">Web OTP<\/a><\/noindex> (ka zhvilluar si SMS Receiver API), i cili lejon organizimin e hyrjes n\u00eb faqen web t\u00eb nj\u00eb passwordi t\u00eb p\u00ebrkohsh\u00ebm, pas marrjes s\u00eb mesazhit SMS me kodin e konfirmimit, i d\u00ebrguar n\u00eb smartphone Android t\u00eb p\u00ebrdoruesit, n\u00eb t\u00eb cilin \u00ebsht\u00eb hapur shfletuesi. Konfirmimi p\u00ebrmes SMS, p\u00ebr shembull, mund t\u00eb p\u00ebrdoret p\u00ebr verifikimin e numrit t\u00eb telefonit t\u00eb dh\u00ebn\u00eb nga p\u00ebrdoruesi gjat\u00eb regjistrimit. N\u00ebse m\u00eb par\u00eb p\u00ebrdoruesi duhej t\u00eb hapte aplikacionin p\u00ebr t\u00eb punuar me SMS, t\u00eb kopjonte kodin n\u00eb clipboard, t\u00eb kthehej n\u00eb shfletues dhe t\u00eb ngjiste k\u00ebt\u00eb kod, API i ri ofron mund\u00ebsin\u00eb p\u00ebr t\u00eb automatizuar k\u00ebt\u00eb proces dhe p\u00ebr ta reduktuar n\u00eb nj\u00eb prekje.\n<li class=\"l\"> API i zgjeruar <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/web-animations\/\">Animacionet Web<\/a><\/noindex><br \/>\np\u00ebr t\u00eb menaxhuar riprodhimin e animacioneve web. N\u00eb versionin e ri \u00ebsht\u00eb shtuar mb\u00ebshtetje p\u00ebr operacionet e kompozimit, duke lejuar kontrollimin se si kombinohen efektet dhe duke ofruar trajtues t\u00eb rinj, t\u00eb cil\u00ebt thirren kur ndodhin ngjarjet e z\u00ebvend\u00ebsimit t\u00eb p\u00ebrmbajtjes. API i Animacioneve Web tani gjithashtu mb\u00ebshtet Promise p\u00ebr t\u00eb p\u00ebrcaktuar renditjen e shfaqjes s\u00eb animacioneve dhe p\u00ebr t\u00eb menaxhuar m\u00eb mir\u00eb se si animacioni interakton me mund\u00ebsi t\u00eb tjera t\u00eb aplikacionit.<\/p>\n<li class=\"l\"> N\u00eb modalitetin e Origin Trials (mund\u00ebsi eksperimentale q\u00eb k\u00ebrkojn\u00eb aktivizim t\u00eb ve\u00e7ant\u00eb) jan\u00eb shtuar disa API t\u00eb reja. Origin Trial n\u00ebnkupton mund\u00ebsin\u00eb e p\u00ebrdorimit t\u00eb API t\u00eb caktuar nga aplikacione t\u00eb ngarkuara nga localhost ose 127.0.0.1, ose pas regjistrimit dhe marrjes s\u00eb nj\u00eb token-i t\u00eb ve\u00e7ant\u00eb, i cili vepron p\u00ebr nj\u00eb koh\u00eb t\u00eb kufizuar p\u00ebr nj\u00eb sit t\u00eb caktuar.\n<ul>\n<li class=\"l\"> API <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5658847691669504\">Dyqani i Cookies<\/a><\/noindex> p\u00ebr qasje nga pun\u00ebtori i sh\u00ebrbimit n\u00eb HTTP Cookies, q\u00eb sh\u00ebrben si nj\u00eb alternativ\u00eb asinkrone p\u00ebr p\u00ebrdorimin e document.cookie.\n<li class=\"l\">  API <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/idle-detection\/\">Detektimi i Papun\u00ebsis\u00eb<\/a><\/noindex> p\u00ebr t\u00eb p\u00ebrcaktuar papun\u00ebsin\u00eb e p\u00ebrdoruesit, duke lejuar p\u00ebrcaktimin e koh\u00ebs kur p\u00ebrdoruesi nuk nd\u00ebrvepron me tastier\u00ebn\/miun, \u00ebsht\u00eb aktivizuar ruajt\u00ebsi i ekranit, ekrani \u00ebsht\u00eb bllokuar ose puna \u00ebsht\u00eb n\u00eb nj\u00eb monitor tjet\u00ebr. Informimi i aplikacionit mbi papun\u00ebsin\u00eb b\u00ebhet p\u00ebrmes d\u00ebrgimit t\u00eb nj\u00eb njoftimi pasi t\u00eb arrihet nj\u00eb prag i caktuar papun\u00ebsie.\n<li class=\"l\"> Modaliteti <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5683766104162304\">Izolimi i Origjin\u00ebs<\/a><\/noindex>, lejon zhvilluesin t\u00eb p\u00ebrdor\u00eb nj\u00eb izolim m\u00eb t\u00eb plot\u00eb t\u00eb p\u00ebrpunimit t\u00eb p\u00ebrmbajtjes n\u00eb nj\u00eb proces t\u00eb ve\u00e7ant\u00eb lidhur me origjin\u00ebn (origin - domeni + porta + protokolli), n\u00eb vend t\u00eb faqes, me koston e nd\u00ebrprerjes s\u00eb mb\u00ebshtetjes p\u00ebr disa funksionalitete t\u00eb vjetra, si\u00e7 jan\u00eb ekzekutimi sinkron i skripteve q\u00eb p\u00ebrdorin document.domain dhe thirrjen postMessage() p\u00ebr t\u00eb d\u00ebrguar mesazhe instanceve t\u00eb WebAssembly.Module. N\u00eb t\u00eb tjera fjal\u00eb, Izolimi i Origjin\u00ebs lejon organizimin e ndarjes n\u00eb procese t\u00eb ndryshme n\u00eb baz\u00eb t\u00eb domenit t\u00eb burimit, dhe jo faqes me t\u00eb gjith\u00eb p\u00ebrfshirjet e huaja n\u00eb faqet.\n<li class=\"l\"> API <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/features\/6533147810332672\">WebAssembly SIMD<\/a><\/noindex> p\u00ebr t\u00eb p\u00ebrdorur instrukcionet SIMD vektoriale n\u00eb aplikacionet n\u00eb formatin WebAssembly. P\u00ebr t\u00eb siguruar pavar\u00ebsi nga platforma, ofrohet nj\u00eb lloj i ri 128-bit\u00ebsh, i cili mund t\u00eb p\u00ebrfaq\u00ebsoj\u00eb lloje t\u00eb ndryshme t\u00eb dh\u00ebnave t\u00eb paketuar dhe disa operacione themelore vektoriale p\u00ebr p\u00ebrpunimin e t\u00eb dh\u00ebnave t\u00eb paketuar. SIMD lejon p\u00ebrmir\u00ebsimin e performanc\u00ebs p\u00ebrmes paralelizimit t\u00eb p\u00ebrpunimit t\u00eb t\u00eb dh\u00ebnave dhe do t\u00eb jet\u00eb i dobish\u00ebm kur kompilohet kodi natyror n\u00eb WebAssembly. P\u00ebr t\u00eb aktivizuar mb\u00ebshtetje p\u00ebr SIMD mund t\u00eb p\u00ebrdoret konfigurimi &#171;chrome:\/\/flags\/#enable-webassembly-simd&#187;.\n<\/ul>\n<li class=\"l\"> Stabilizuar dhe tani \u00ebsht\u00eb duke u shp\u00ebrndar\u00eb jasht\u00eb Origin Trials<br \/>\nAPI <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/content-indexing-api\/\">Content Indexing<\/a><\/noindex>, duke ofruar metadatat mbi p\u00ebrmbajtjen q\u00eb m\u00eb par\u00eb ishte e cachesuar nga aplikacionet web, t\u00eb cilat punojn\u00eb n\u00eb modin Progressive Web Apps (PWS). Aplikacioni mund t\u00eb ruaj\u00eb n\u00eb an\u00ebn e shfletuesit t\u00eb dh\u00ebna t\u00eb ndryshme, duke p\u00ebrfshir\u00eb imazhe, video dhe artikuj, dhe n\u00eb rast t\u00eb humbjes s\u00eb lidhjes s\u00eb rrjetit, t'i p\u00ebrdor\u00eb ato me an\u00eb t\u00eb API Cache Storage dhe IndexedDB. API Indexing t\u00eb P\u00ebrmbajtjes jep mund\u00ebsin\u00eb p\u00ebr t\u00eb shtuar, gjetur dhe fshir\u00eb burime t\u00eb tilla. N\u00eb shfletues, ky API tashm\u00eb p\u00ebrdoret p\u00ebr t\u00eb enumeruar list\u00ebn e faqeve dhe t\u00eb dh\u00ebnave multimedia, t\u00eb cilat jan\u00eb t\u00eb disponueshme p\u00ebr shikim offline.<\/p>\n<li class=\"l\"> Stabilizuar varianti i API <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/2018\/12\/wakelock\">Wake Lock<\/a><\/noindex> bazuar n\u00eb mekanizmin Promise, duke ofruar nj\u00eb m\u00ebnyr\u00eb m\u00eb t\u00eb sigurt p\u00ebr t\u00eb menaxhuar fikjen automatike t\u00eb ekranit dhe kalimin e pajisjeve n\u00eb modet e kursimit t\u00eb energjis\u00eb.\n<li class=\"l\"> N\u00eb versionin p\u00ebr platform\u00ebn Android <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/app-shortcuts\">\u00ebsht\u00eb shtuar<\/a><\/noindex> mb\u00ebshtetje p\u00ebr ikona aplikacionesh, t\u00eb cilat lejojn\u00eb qasje t\u00eb shpejt\u00eb n\u00eb veprime tipike t\u00eb k\u00ebrkuara n\u00eb aplikacion. P\u00ebr t\u00eb krijuar ikona, mjafton t\u00eb shtoni element\u00eb n\u00eb manifestin e aplikacionit web n\u00eb formatin PWA (Progressive Web Apps).<br \/>\n<center><noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/app-shortcuts\/\"><img decoding=\"async\" alt=\"L\u00ebshimi i Chrome 84\" src=\"\/wp-content\/uploads\/2020\/07\/bd93f6ee778be3c616f66229bc54bf54.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> P\u00ebr Web Worker lejohet p\u00ebrdorimi i API <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/reporting-observer\/\">ReportingObserver<\/a><\/noindex>, q\u00eb lejon p\u00ebrcaktimin e nj\u00eb trajtuesi p\u00ebr gjenerimin e raporteve, i cili thirret kur t\u00eb p\u00ebrdoren mund\u00ebsit\u00eb e vjetruara. Raporti i gjeneruar nga zgjedhja e p\u00ebrdoruesit mund t\u00eb ruhet, t\u00eb d\u00ebrgohet n\u00eb server ose t\u00eb p\u00ebrpunohet nga nj\u00eb sken\u00eb n\u00eb JavaScript.\n<li class=\"l\"> P\u00ebrdit\u00ebsuar API <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/resize-observer\">Resize Observer<\/a><\/noindex>, q\u00eb lejon lidhjen e nj\u00eb trajtuesi, t\u00eb cilit do t'i d\u00ebrgohen njoftime p\u00ebr ndryshimin e madh\u00ebsis\u00eb s\u00eb elementeve t\u00eb specifikuara n\u00eb faqe. N\u00eb ResizeObserverEntry jan\u00eb shtuar tri veti t\u00eb reja: contentBoxSize, borderBoxSize dhe devicePixelContentBoxSize p\u00ebr t\u00eb marr\u00eb informacion m\u00eb t\u00eb detajuar, e dh\u00ebn\u00eb n\u00eb form\u00ebn e nj\u00eb vargu nga objektet ResizeObserverSize.\n<li class=\"l\"> Shtuar fjal\u00ebn ky\u00e7e &#171;<noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5644990145363968\">revert<\/a><\/noindex>&#187; p\u00ebr t\u00eb rikthyer stilin e elementit n\u00eb vler\u00ebn e tij t\u00eb paracaktuar.\n<li class=\"l\"> \u00c7liruar nga prefiksi i vetis\u00eb CSS &#171;-webkit-appearance&#187; dhe &#171;-webkit-ruby-position&#187;, t\u00eb cilat tani jan\u00eb t\u00eb disponueshme si &#171;<noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/4715298156445696\">appearance<\/a><\/noindex>\u00bb dhe \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/6249925820022784\">ruby-position<\/a><\/noindex>&#171;.\n<li class=\"l\"> N\u00eb JavaScript <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5700509656678400\">\u00ebsht\u00eb implementuar<\/a><\/noindex> mb\u00ebshtetje p\u00ebr sh\u00ebnimin e metoda dhe pronave t\u00eb klas\u00ebs si private, duke lejuar k\u00ebshtu aksesin vet\u00ebm brenda klas\u00ebs (m\u00eb par\u00eb, vet\u00ebm fushat mund t\u00eb ishin private). P\u00ebr t\u00eb sh\u00ebnuar metodat dhe pronat si private duhet <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/tc39\/proposal-private-methods\/blob\/master\/README.md\">t\u00eb specifikoni<\/a><\/noindex> para emrit t\u00eb fush\u00ebs shenj\u00ebn &#171;#&#187;.\n<li class=\"l\"> N\u00eb JavaScript <noindex><a rel=\"nofollow\" href=\"https:\/\/v8.dev\/blog\/v8-release-84\">\u00ebsht\u00eb shtuar<\/a><\/noindex> mb\u00ebshtetje <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%A1%D0%BB%D0%B0%D0%B1%D0%B0%D1%8F_%D1%81%D1%81%D1%8B%D0%BB%D0%BA%D0%B0\">referencat e dob\u00ebta<\/a><\/noindex> (weak reference) p\u00ebr objektet JavaScript, q\u00eb lejojn\u00eb ruajtjen e nj\u00eb referenc\u00eb n\u00eb objekt, por nuk bllokojn\u00eb fshirjen e objektit t\u00eb lidhur nga mbledh\u00ebsi i plehrave. Po ashtu \u00ebsht\u00eb shtuar mb\u00ebshtetje p\u00ebr finalizator\u00ebt, duke ofruar mund\u00ebsin\u00eb p\u00ebr t\u00eb p\u00ebrcaktuar nj\u00eb trajtim, q\u00eb thirret pas p\u00ebrfundimit t\u00eb mbledhjes s\u00eb plehrave t\u00eb objektit t\u00eb caktuar.\n<li class=\"l\"> Fillimi i aplikacioneve n\u00eb WebAssembly \u00ebsht\u00eb p\u00ebrshpejtuar, fal\u00eb implementimit n\u00eb kompilatorin fillestar (baseline) Liftoff <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/WebAssembly\/threads\">instruksioneve atomike<\/a><\/noindex> dhe <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/WebAssembly\/bulk-memory-operations\">p\u00ebr operacione paketimi me memorie<\/a><\/noindex>. Mjetet p\u00ebr debuggimin e WebAssembly jan\u00eb p\u00ebrmir\u00ebsuar, duke rritur ndjesh\u00ebm performanc\u00ebn e debuggimit kur p\u00ebrdoren piketat e ndaljes (m\u00eb par\u00eb p\u00ebr debuggim p\u00ebrdorej interpretuesi, tani kompilatori Liftoff).\n<li class=\"l\"> N\u00eb mjetet p\u00ebr zhvilluesit e web-it pphttps:\/\/developers.google.com\/web\/updates\/2020\/05\/devtools \u00ebsht\u00eb azhurnuar]] paneli p\u00ebr analizimin e performanc\u00ebs. \u00cbsht\u00eb shtuar informacion i p\u00ebrgjithsh\u00ebm mbi metrik\u00ebn <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/tbt\/\">TBT<\/a><\/noindex> (Total Blocking Time), q\u00eb tregon sa koh\u00eb duket se faqja \u00ebsht\u00eb e aksesueshme, por n\u00eb t\u00eb v\u00ebrtet\u00eb nuk \u00ebsht\u00eb (dmth. faqja \u00ebsht\u00eb vizatuar tashm\u00eb, por ende \u00ebsht\u00eb duke bllokuar ekzekutimin e shtyll\u00ebs kryesore dhe nuk \u00ebsht\u00eb e mundur futja e t\u00eb dh\u00ebnave). \u00cbsht\u00eb shtuar nj\u00eb seksion i ri Experience p\u00ebr analizimin e metrik\u00ebs <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/cls\/\">CLS<\/a><\/noindex> (Cumulative Layout Shift), q\u00eb reflekton stabilitetin vizual t\u00eb p\u00ebrmbajtjes. N\u00eb panelin e inspektimit t\u00eb stilit CSS \u00ebsht\u00eb realizuar nj\u00eb parap\u00ebrgjigje e imazheve, t\u00eb cilat jan\u00eb specifikuar p\u00ebrmes pron\u00ebs &#171;background-image&#187;.\n<\/ul>\n<p>P\u00ebrve\u00e7 risive dhe korrigjimeve t\u00eb gabimeve n\u00eb versionin e ri, jan\u00eb eliminuar <noindex><a rel=\"nofollow\" href=\"https:\/\/bugs.chromium.org\/p\/chromium\/issues\/list?can=1&#038;q=label%3ARelease-0-M84\">38 vulnerabilitete<\/a><\/noindex>. Shumica e vulnerabiliteteve jan\u00eb identifikuar si rezultat i testimeve automatike me mjete <noindex><a rel=\"nofollow\" href=\"http:\/\/code.google.com\/p\/address-sanitizer\/wiki\/AddressSanitizer\">AddressSanitizer<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/code.google.com\/p\/memory-sanitizer\/wiki\/MemorySanitizer\">MemorySanitizer<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/sites.google.com\/a\/chromium.org\/dev\/developers\/testing\/control-flow-integrity\">Control Flow Integrity<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/sites.google.com\/a\/chromium.org\/dev\/developers\/testing\/libfuzzer\">LibFuzzer<\/a><\/noindex> dhe <noindex><a rel=\"nofollow\" href=\"http:\/\/lcamtuf.coredump.cx\/afl\/\">AFL<\/a><\/noindex>. Nj\u00eb problem (CVE-2020-6510, mbushje e tamponit n\u00eb trajtuesin e operacioneve t\u00eb prapme fetch) \u00ebsht\u00eb sh\u00ebnuar si kritike, dmth. lejon kap\u00ebrcimin e t\u00eb gjitha niveleve t\u00eb siguris\u00eb s\u00eb shfletuesit dhe ekzekutimin e kodit n\u00eb sistem p\u00ebrtej mjedisit sandbox. N\u00eb kuad\u00ebr t\u00eb programit p\u00ebr shp\u00ebrblimin financiar p\u00ebr zbulimin e vulnerabiliteteve p\u00ebr l\u00ebshimin aktual, kompania Google ka dh\u00ebn\u00eb 26 shp\u00ebrblime me nj\u00eb total prej 21500 dollar\u00ebsh (dy shp\u00ebrblime $5000, dy shp\u00ebrblime $3000, nj\u00eb shp\u00ebrblim $2000, dy shp\u00ebrblime $1000 dhe tre shp\u00ebrblime $500). Shuma e 16 shp\u00ebrblimeve ende nuk \u00ebsht\u00eb p\u00ebrcaktuar. <\/p>\n<p><noindex><a rel=\"nofollow\" name=\"link\"><\/a><\/noindex><\/p>\n<p>Burimi: <a \ncontent=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=53362\">opennet.ru<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Google \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0430 \u0440\u0435\u043b\u0438\u0437 web-\u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0430 Chrome 84. \u041e\u0434\u043d\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u043e \u0434\u043e\u0441\u0442\u0443\u043f\u0435\u043d \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u044b\u0439 \u0432\u044b\u043f\u0443\u0441\u043a \u0441\u0432\u043e\u0431\u043e\u0434\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430 Chromium, \u0432\u044b\u0441\u0442\u0443\u043f\u0430\u044e\u0449\u0435\u0433\u043e \u043e\u0441\u043d\u043e\u0432\u043e\u0439 Chrome. \u0411\u0440\u0430\u0443\u0437\u0435\u0440 Chrome \u043e\u0442\u043b\u0438\u0447\u0430\u0435\u0442\u0441\u044f \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043b\u043e\u0433\u043e\u0442\u0438\u043f\u043e\u0432 Google, \u043d\u0430\u043b\u0438\u0447\u0438\u0435\u043c \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u043e\u0442\u043f\u0440\u0430\u0432\u043a\u0438 \u0443\u0432\u0435\u0434\u043e\u043c\u043b\u0435\u043d\u0438\u0439 \u0432 \u0441\u043b\u0443\u0447\u0430\u0435 \u043a\u0440\u0430\u0445\u0430, \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c\u044e \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u043c\u043e\u0434\u0443\u043b\u044f Flash \u043f\u043e \u0437\u0430\u043f\u0440\u043e\u0441\u0443, \u043c\u043e\u0434\u0443\u043b\u044f\u043c\u0438 \u0434\u043b\u044f \u0432\u043e\u0441\u043f\u0440\u043e\u0438\u0437\u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0437\u0430\u0449\u0438\u0449\u0451\u043d\u043d\u043e\u0433\u043e \u0432\u0438\u0434\u0435\u043e\u043a\u043e\u043d\u0442\u0435\u043d\u0442\u0430 (DRM), \u0441\u0438\u0441\u0442\u0435\u043c\u043e\u0439 \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0439 \u0438 \u043f\u0435\u0440\u0435\u0434\u0430\u0447\u0435\u0439 \u043f\u0440\u0438 \u043f\u043e\u0438\u0441\u043a\u0435 RLZ-\u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u043e\u0432. \u0421\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u0439 \u0432\u044b\u043f\u0443\u0441\u043a Chrome 85 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":88913,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-88912","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Google \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0430 \u0440\u0435\u043b\u0438\u0437 web-\u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0430\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sq\/blog\/news\/reliz-chrome-84\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0420\u0435\u043b\u0438\u0437 Chrome 84 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Google \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0430 \u0440\u0435\u043b\u0438\u0437 web-\u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0430\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/news\/reliz-chrome-84\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-07-16T05:42:12+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-07-16T05:42:12+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47L\u00ebshimi i Chrome 84 | ProHoster","description":"Kompania Google e lajm\u00ebroi lansimin e shfletuesit web.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/news\/reliz-chrome-84","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0420\u0435\u043b\u0438\u0437 Chrome 84 | ProHoster","og:description":"\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Google \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0430 \u0440\u0435\u043b\u0438\u0437 web-\u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0430","og:url":"https:\/\/prohoster.info\/sq\/blog\/news\/reliz-chrome-84","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-07-16T05:42:12+00:00","article:modified_time":"2020-07-16T05:42:12+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"88912","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 13:19:36","updated":"2022-09-30 22:56:22","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/88912","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=88912"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/88912\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/88913"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=88912"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=88912"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=88912"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}