Martin Stransky, mentainer of Firefox packages in Fedora and RHEL, responsible for porting Firefox to Wayland, published a report reviewing the latest achievements in Firefox's functionality in Wayland-based environments. <\/p>\n
In upcoming Firefox releases, it is planned to address the clipboard and popup handling issues observed in Wayland builds. These features could not be implemented right away due to the differences in their implementation approach in X11 and Wayland. In the former case, difficulties arose because of the asynchronous operation of the Wayland clipboard, which required the creation of a separate layer to abstract access to the Wayland clipboard. This layer will be added in Firefox 93 and enabled by default in Firefox 94. <\/p>\n
Regarding popup dialogs, the main difficulty was that Wayland requires strict adherence to the hierarchy of popups, meaning that a parent window may create a child window with a popup, but the next popup initiated from that window must be tied to the original child window, forming a chain. In Firefox, each window could spawn multiple popups without forming a hierarchy. The problem was that using Wayland, closing one of the popups requires rebuilding the entire chain of windows with other popups, considering that having multiple open popups is not uncommon, as menus, tooltips, add-on dialogs, permission requests, etc., are implemented as popups. The situation was further complicated by shortcomings in Wayland and GTK, which meant that even minor changes could lead to various regressions. Nevertheless, the code for handling popups for Wayland has been debugged and is planned to be included in Firefox 94. <\/p>\n
Printre alte \u00eembun\u0103t\u0103\u021biri legate de Wayland se men\u021bioneaz\u0103 ad\u0103ugarea \u00een Firefox 93 a modific\u0103rilor legate de scalarea pe ecrane cu diferite DPI, care au eliminat flicker-ul \u00een timpul mut\u0103rii ferestrei spre marginea ecranului \u00een configura\u021bii cu mai multe monitoare. \u00cen Firefox 95 se preconizeaz\u0103 s\u0103 se rezolve problemele care apar \u00een utilizarea interfe\u021bei drag & drop, de exemplu, \u00een ceea ce prive\u0219te copierea fi\u0219ierelor din surse externe \u00een sistemele de fi\u0219iere locale \u0219i mutarea tab-urilor. <\/p>\n
\u00cen versiunea Firefox 96, portul Firefox pentru Wayland se planific\u0103 s\u0103 ating\u0103 o paritate func\u021bional\u0103 cu versiunea pentru X11, cel pu\u021bin \u00een utilizarea mediu GNOME pe Fedora. Dup\u0103 aceasta, aten\u021bia dezvoltatorilor se va concentra pe optimizarea func\u021bion\u0103rii procesului GPU \u00een medii Wayland, unde este mutat codul pentru interac\u021biunea cu adaptoarele grafice \u0219i care protejeaz\u0103 procesul principal al browser-ului de blocare \u00een caz de erori ale driverelor. De asemenea, se preconizeaz\u0103 mutarea codului pentru decodarea video prin VAAPI \u00een procesul GPU, cod care \u00een prezent ruleaz\u0103 \u00een procese de manipulare a con\u021binutului. <\/p>\n
De asemenea, merit\u0103 men\u021bionat c\u0103 un mic procent din utilizatorii versiuni stabile ale Firefox au acces la modul de izolare strict\u0103 a site-urilor, care s-a dezvoltat \u00een cadrul proiectului Fission. Spre deosebire de distribuirea aleatorie utilizat\u0103 p\u00e2n\u0103 acum pentru procesarea tab-urilor din pool-ul de procese disponibil (implicit 8), modul de izolare separ\u0103 procesarea fiec\u0103rui site \u00een propriul s\u0103u proces, \u00eemp\u0103r\u021bind nu pe tab-uri, ci pe domenii (Public Suffix), ceea ce permite izolarea suplimentar\u0103 a con\u021binutului scripturilor externe \u0219i a blocurilor iframe. Activarea modului Fission se realizeaz\u0103 prin variabila \u201efission.autostart=true\u201d din about:config sau pe pagina about:preferences#experimental. <\/p>\n
Modul de izolare strict\u0103 ajut\u0103 la protejarea \u00eempotriva atacurilor prin canale secundare, de exemplu, asociate cu vulnerabilit\u0103\u021bile de tip Spectre, \u0219i reduce fragmentarea memoriei, return\u00e2nd mai eficient memoria sistemului de operare, minimiz\u00e2nd impactul colect\u0103rii de\u0219eurilor \u0219i al calcului intensiv asupra paginilor din alte procese, sporind eficien\u021ba repartiz\u0103rii sarcinii \u00eentre diferitele nuclee CPU \u0219i \u00eembun\u0103t\u0103\u021bind stabilitatea (blocarea procesului care gestioneaz\u0103 iframe-ul nu va afecta site-ul principal \u0219i alte taburi). <\/p>\n
Printre problemele cunoscute care apar \u00een utilizarea modului de izolare strict\u0103, se remarc\u0103 o cre\u0219tere semnificativ\u0103 a consumului de memorie \u0219i a descriptorilor de fi\u0219iere atunci c\u00e2nd sunt deschise un num\u0103r mare de taburi, precum \u0219i disfunc\u021bii ale unor extensii, dispari\u021bia con\u021binutului iframe \u00een timpul imprim\u0103rii \u0219i \u00een apelurile func\u021biei de captur\u0103 de ecran, sc\u0103derea eficien\u021bei cache-ului documentelor cu iframe, pierderea con\u021binutului formularelor completate, dar neexpediate, la restaurarea sesiunii dup\u0103 un blocaj. <\/p>\n