| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
fixes #1340
|
|
|
|
| |
related #1335
|
|
|
|
| |
fixes #1332
|
|
|
|
|
| |
fixes #290
fixes #1330
|
| |
|
| |
|
|
|
|
|
|
| |
teated as milli sec)
fixes #1296
|
|
|
|
| |
fixes #1334
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
- Messages from MUCs weren't added to their respective MUC MAM ranges, thus re-fetched on rejoin
- The earliest ('first') message of a mam page was used to update the to_id, but it should have been 'last'; also the other way around.
- Duplicates weren't detected properly
|
|
|
|
| |
fixes #1297
|
|
|
|
|
| |
MenuButton.set_child was only added to VAPIs of 0.52 and later.
Even if GTK4 is new enough, they wouldn't be available.
|
| |
|
| |
|
|
|
|
| |
Fixes #1307
|
| |
|
| |
|
| |
|
|
|
|
| |
fixes #1294
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
fixes #1284
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
fixes #1227
|
|
|
|
| |
fixes #1262
|
| |
|
| |
|
| |
|
|
|
|
| |
MenuButton.activate only exists since 4.4
|
| |
|
| |
|
| |
|
|
|
|
|
| |
A bug in GTK caused the application to crash in some tooltip-related conditions
https://gitlab.gnome.org/GNOME/gtk/-/issues/4941
|
| |
|