{"id":287717,"date":"2023-11-03T09:25:33","date_gmt":"2023-11-03T08:25:33","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=287717"},"modified":"2023-12-08T07:15:29","modified_gmt":"2023-12-08T06:15:29","slug":"edge-119-0-2151-44-118-0-2088-88","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2023\/11\/03\/edge-119-0-2151-44-118-0-2088-88\/","title":{"rendered":"Edge 119.0.2151.44 \/ 118.0.2088.88"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"margin: 0px 10px 0px 0px;\" title=\"Edge\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2020\/01\/Edge.jpg\" alt=\"Edge\" width=\"65\" height=\"67\" align=\"left\" border=\"0\" \/>[<a href=\"https:\/\/borncity.com\/win\/2023\/11\/03\/edge-119-0-2151-44-118-0-2088-88\/\" target=\"_blank\" rel=\"noopener\">English<\/a>]Microsoft hat zum 2. November 2023 sowohl ein Update des Chrome Browsers im Extended Stable auf 118.0.2088.88 freigegeben, als auch ein Update auf den Edge 119.0.2151.44\u00a0 ver\u00f6ffentlicht. Danke an den Leser, der zum 3. November 2023 <a href=\"https:\/\/borncity.com\/blog\/2023\/11\/01\/google-chrome-119-0-6045-105-106\/#comment-161847\">meldete<\/a>, dass Microsoft den Edge-Browser auf die Version 119.0.2151.44 aktualisiert habe.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg05.met.vgwort.de\/na\/7bf6956989be40fb99180d6f5f52c54b\" alt=\"\" width=\"1\" height=\"1\" \/>Die Updates sind erforderlich, um Chrome-Schwachstellen zu schlie\u00dfen. Zum 1. November 2023 schreibt Microsoft <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-relnotes-security#november-1-2023\" target=\"_blank\" rel=\"noopener\">hier<\/a> \"Microsoft ist \u00fcber die j\u00fcngsten Sicherheitsl\u00fccken in Chromium informiert. Wir arbeiten aktiv an der Freigabe eines Sicherheitspatches.\" Die Chrome Schwachstellen sind im Beitrag <a href=\"https:\/\/borncity.com\/blog\/2023\/11\/01\/google-chrome-119-0-6045-105-106\/\">Google Chrome 119.0.6045.105\/.106<\/a> beschrieben.<\/p>\n<h2>Edge 119.0.2151.44<\/h2>\n<p>Im Stable Channel hat Microsoft das Feature-Update auf den neuen Entwicklungszweig 119 ausgerollt. Zum 2. November 2023 wurde der Edge 119.0.2151.44\u00a0 ver\u00f6ffentlicht. Es hei\u00dft in den <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-relnote-stable-channel#version-1190215144-november-2-2023\" target=\"_blank\" rel=\"noopener\">Release Notes<\/a> \"Fixed various bugs and performance issues\", Diese Version schlie\u00dft die in obigem Absatz angesprochenen Chromium-Schwachstellen (in den <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-relnotes-security#november-1-2023\" target=\"_blank\" rel=\"noopener\">Sicherheitsmitteilungen<\/a> gibt es noch keinen neueren Eintrag). Da es sich um ein Feature-Update der Version 119 handelt, kommen eine Reihe Neuerungen hinzu.<\/p>\n<ul>\n<li><strong>Compression Dictionary Transport support.<\/strong> A version of the <a href=\"https:\/\/datatracker.ietf.org\/doc\/draft-ietf-httpbis-compression-dictionary\/\" target=\"_blank\" rel=\"noopener\">Compression Dictionary Transport<\/a> feature is available for sites to use by participating in the associated origin trial. If your network uses a middlebox that inspects network traffic and\/or you previously encountered issues with the ZSDCH feature, review the <a href=\"https:\/\/learn.microsoft.com\/en-us\/DeployEdge\/learnmore-zsdch-compression\" target=\"_blank\" rel=\"noopener\">Considerations for zstd-based Shared Dictionary Compression for HTTP<\/a> page which contains updated guidance.<\/li>\n<li><strong>Behavioral changes to the beforeunload event.<\/strong> The behavior of the beforeunload event has changed such that calling preventDefault in a beforeunload event handler triggers a confirmation dialog. Setting returnValue to an empty string in a beforeunload event handler no longer triggers a confirmation dialog. This behavior takes effect starting in Microsoft Edge version 119. Administrators can temporarily opt out of this functionality by disabling the <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-policies#beforeunloadeventcancelbypreventdefaultenabled\" target=\"_blank\" rel=\"noopener\">BeforeunloadEventCancelByPreventDefaultEnabled<\/a> policy.<\/li>\n<li><strong>Split screen restore improvements.<\/strong> Split screen allows you to simultaneously work on multiple tasks across two, side-by-side screens in one browsing tab to boost your productivity and multitask more efficiently. Now after the browser is restarted and the previous session is restored, the split tab will also be restored.<\/li>\n<li><strong>Additional capability to manage sidebar apps.<\/strong> Administrators can utilize the \"sidebar_auto_open_blocked\" <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-policies#extensionsettings\" target=\"_blank\" rel=\"noopener\">ExtensionSettings<\/a> policy field to control the auto-open behavior of sidebar apps. For more information, see <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-manage-extensions-ref-guide\" target=\"_blank\" rel=\"noopener\">Detailed guide to the ExtensionSettings<\/a> policy.<\/li>\n<li><strong>Updates to Microsoft Edge enterprise sync settings page.<\/strong> When the <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-policies#forcesynctypes\" target=\"_blank\" rel=\"noopener\">ForceSyncTypes<\/a> and <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-policies#synctypeslistdisabled\" target=\"_blank\" rel=\"noopener\">SyncTypesListDisabled<\/a> polices are used concurrently, the sync settings page (<code>edge:\/\/settings\/profiles\/sync<\/code>) accurately show the status for each data type.<\/li>\n<\/ul>\n<p>Zudem wurden folgende neue Richtlinien implementiert:<\/p>\n<ul>\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-policies#switchintranetsitestoworkprofile\" target=\"_blank\" rel=\"noopener\">SwitchIntranetSitesToWorkProfile<\/a> &#8211; Intranetseiten auf ein Arbeitsprofil umstellen<\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-policies#switchsitesoniemodesitelisttoworkprofile\" target=\"_blank\" rel=\"noopener\">SwitchSitesOnIEModeSiteListToWorkProfile<\/a> &#8211; Wechseln der Sites in der Site-Liste des IE-Modus zu einem Arbeitsprofil<\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-policies#organizationalbrandingonworkprofileuienabled\" target=\"_blank\" rel=\"noopener\">OrganizationalBrandingOnWorkProfileUIEnabled<\/a> &#8211; Erlauben der Verwendung der Branding-Assets der eigenen Organisation aus M365 auf der profilbezogenen Benutzeroberfl\u00e4che eines Arbeitsprofils<\/li>\n<\/ul>\n<h2>Edge 118.0.2088.88<\/h2>\n<p>Zu diesem Update <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-relnote-stable-channel#version-1180208888-november-2-2023\" target=\"_blank\" rel=\"noopener\">hei\u00dft<\/a> es nur \"Fixed various bugs and performance issues for Extended Stable release.\" &#8211; ich gehe aber davon aus, dass dort auch bestehende Chromium-Schwachstellen beseitigt wurden<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[English]Microsoft hat zum 2. November 2023 sowohl ein Update des Chrome Browsers im Extended Stable auf 118.0.2088.88 freigegeben, als auch ein Update auf den Edge 119.0.2151.44\u00a0 ver\u00f6ffentlicht. Danke an den Leser, der zum 3. November 2023 meldete, dass Microsoft den &hellip; <a href=\"https:\/\/borncity.com\/blog\/2023\/11\/03\/edge-119-0-2151-44-118-0-2088-88\/\">Weiterlesen <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4461],"tags":[4201],"class_list":["post-287717","post","type-post","status-publish","format-standard","hentry","category-edge","tag-edge"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/287717","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=287717"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/287717\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=287717"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=287717"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=287717"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}