Closed
Bug 1828067
Opened 1 year ago
Closed 1 year ago
[Wayland] Don't use extra wl_registry connection in nsGtkKeyUtils
Categories
(Core :: Widget: Gtk, enhancement, P3)
Core
Widget: Gtk
Tracking
()
RESOLVED
FIXED
114 Branch
| Tracking | Status | |
|---|---|---|
| firefox114 | --- | fixed |
People
(Reporter: stransky, Assigned: stransky)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
To speed up Wayland start don't use extra wl_registry connection in nsGtkKeyUtils but use the one from Wayland Display.
|
Assignee | |
Updated•1 year ago
|
|
|
Assignee | |
Comment 1•1 year ago
|
||
To speed up start Firefox on Wayland don't use extra wl_registry connection in nsGtkKeyUtils but use the one from nsWaylandDisplay.
In this patch we do:
- Remove wl_registry handlers from KeymapWrapper but use the one in nsWaylandDisplay
- Make wl_seat/wl_keyboard static and store obtained values here. We don't need to create KeymapWrapper object for it.
- Support wl_seat/wl_keyboard removal by Wayland compositor.
Pushed by stransky@redhat.com: https://hg.mozilla.org/integration/autoland/rev/29f3802bdae8 [Wayland] Migrate nsGtkKeyUtils wl_registry to nsWaylandDisplay r=emilio
|
||
Comment 3•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox114:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 114 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•