-
Notifications
You must be signed in to change notification settings - Fork 393
Expand file tree
/
Copy pathReleaseNotes.html
More file actions
9610 lines (8715 loc) · 458 KB
/
Copy pathReleaseNotes.html
File metadata and controls
9610 lines (8715 loc) · 458 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<style>
dt { font-weight: bold; }
h3 { text-decoration: underline; }
dd { margin-top: 10px; margin-bottom: 10px; }
dd p { margin-top: 0; }
dd div { margin: 10px 0; }
</style>
<title>Wt Release notes</title>
</head>
<body>
<h1>Wt Release notes</h1>
This file lists important notes on migrating existing applications to
newer version of Wt. It lists changes in the library that may break
the way you build Wt, the way you configure Wt or the Wt API and
behaviour.
<h2>Release 4.14.4 (October 1, 2026)</h2>
<p>Wt 4.14.4 is a patch release that addresses the following issue:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14635" target="_blank">Issue #14635</a>
fixed
<a href="classWt_1_1WFormWidget.html#a5216ba1594b5dc525cc47cad593c7ba8" target="_blank">WFormWidget::changed()</a> signal sometimes being emitted
a second time with incorrect informations when the form-data caching was enabled.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14824" target="_blank">Issue #14824</a>:
fixed
<a href="classWt_1_1WWidget.html#ab4e595dd2fd53ec3648409e44b58ce32" target="_blank">WWidget::anchorAt()</a>
(and therefore
<a href="classWt_1_1WPopupMenu.html" target="_blank">WPopupMenu</a>) sometimes not correctly aligning the widget with its
position anchor.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14619" target="_blank">Issue #14619</a>:
fixed resizable layouts not filling their available height when revealed as
deferred <a href="classWt_1_1WStackedWidget.html" target="_blank">WStackedWidget</a>
content or as a lazily loaded
<a href="classWt_1_1WTabWidget.html" target="_blank">WTabWidget</a> tab.
</li>
</ul>
<h2>Release 4.14.3 (September 8, 2026)</h2>
<p>Wt 4.14.3 is a patch release that addresses the following issue:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14789" target="_blank">Issue #14789</a>:
fixed
<a href="classWt_1_1WLineEdit.html#addb99c6ab5483836adf44a2706a410af" target="_blank">WLineEdit::setText()</a>
causing a JavaScript error when called after
<a href="classWt_1_1WLineEdit.html#a0639ec7e420ba32ffb148303a79fb969" target="_blank">WLineEdit::setInputMask()</a>
if the widget was already rendered.
</li>
</ul>
<h2>Release 4.14.2 (August 27, 2026)</h2>
<p>Wt 4.14.2 is a patch release that addresses the following issues:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14614" target="_blank">Issue #14614</a>:
fixed
<a href="classWt_1_1WWidget.html#af0df90fe8bbcb42dd057f8c1f1835b49" target="_blank">WWidget::positionAt()</a>
sometimes not correctly positioning the widget, especially when the widget it was positioned at
was inside of another popup.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14716" target="_blank">Issue #14716</a>:
fixed
<a href="classWt_1_1WPopupMenu.html" target="_blank">WPopupMenu</a>
being incorrectly positioned relative to a widget after previously being
popped up at a point.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14767" target="_blank">Issue #14767</a>:
fixed
<a href="classWt_1_1WPopupMenu.html#a9da2dff4c6de6845a5a15b1a7c22572c" target="_blank">WPopupMenu::popup(WPoint)</a> (and therefore
<a href="classWt_1_1WPopupMenu.html#a8b63c8824aa820d8d3669e563b6f57f4" target="_blank">WPopupMenu::popup(WMouseEvent)</a>)
not changing the position of the
<a href="classWt_1_1WPopupMenu.html" target="_blank">WPopupMenu</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14475" target="_blank">Issue #14475</a>:
fixed
<a href="classWt_1_1WDialog.html" target="_blank">WDialog</a> sometimes moving for no reason, or teleporting
to the wrong position when being moved by the user.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14712" target="_blank">Issue #14712</a>:
fixed
<a href="classWt_1_1WDialog.html#ac092840d5ce4ac38198a15a8ddda5e87" target="_blank">WDialog::moved()</a> signal
sometimes being emitted with an incorrect x coordinate when being moved by something else than the user.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14660" target="_blank">Issue #14660</a>:
fixed
<a href="classWt_1_1Dbo_1_1FixedSqlConnectionPool.html" target="_blank">Wt::Dbo::FixedSqlConnectionPool</a> not always correctly
waking up threads waiting for a connection when a connection was returned to the pool. This could lead to a deadlock.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14744" target="_blank">Issue #14744</a>:
fixed JavaScript error sometimes happening when resizing or adding a
<a href="classWt_1_1WTreeView.html" target="_blank">WTreeView</a> after another one had
been removed.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14714" target="_blank">Issue #14714</a>:
fixed
<a href="classWt_1_1WTextEdit.html" target="_blank">WTextEdit</a> not being
resizable below the TinyMCE default height of 400px, for example when placed
in a layout using
<a href="namespaceWt.html#aeb0e4f49ce4a28d8ce9b0c6005027876" target="_blank">LayoutImplementation::JavaScript</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14713" target="_blank">Issue #14713</a>:
fixed
<a href="classWt_1_1WTextEdit.html" target="_blank">WTextEdit</a> ignoring its offset
and always rendering in the top-left corner when positioned.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14690" target="_blank">Issue #14690</a>:
fixed
<a href="classWt_1_1WTextEdit.html" target="_blank">WTextEdit</a> not filling the
available width and height when in a layout using
<a href="namespaceWt.html#aeb0e4f49ce4a28d8ce9b0c6005027876" target="_blank">LayoutImplementation::Flex</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14437" target="_blank">Issue #14437</a>:
fixed layouts with
<a href="namespaceWt.html#aeb0e4f49ce4a28d8ce9b0c6005027876" target="_blank">LayoutImplementation::Flex</a>
not correctly removing some wrappers when removing a widget from itself.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14597" target="_blank">Issue #14597</a>:
fixed endless page reloads when using session id prefixes with <code>Combined</code> session
tracking method.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14596" target="_blank">Issue #14596</a>:
fixed incorrect handling, on the client side, of url parameters containing <code>=</code> as part of their value.
</li>
</ul>
<h2>Release 4.14.1 (August 6, 2026)</h2>
<p>Wt 4.14.1 is a patch release that addresses the following issues:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14672" target="_blank">Issue #14672</a>:
fixed web-socket not working when compression was enabled due to all of their messages being fully compressed.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14676" target="_blank">Issue #14676</a>:
fixed
<a href="classWt_1_1Auth_1_1Mfa_1_1TotpProcess.html" target="_blank">Auth::Mfa::TotpProcess</a> considering a user
trying to login while being throttled as a failed attempt, which would increase the throttle time.
Additionally, fixed the throttle time shown to the user when trying to enter the TOTP code being smaller than it actually is.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14677" target="_blank">Issue #14677</a>:
fixed
<a href="classWt_1_1WMenu.html" target="_blank">WMenu</a> selection sometimes not propagating their selection
correctly to the top-most menu.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13654" target="_blank">Issue #13654</a>:
fixed a JavaScript error when adding a submenu to a
<a href="classWt_1_1WMenu.html" target="_blank">WMenu</a> that had been
removed from the page by a
<a href="classWt_1_1WTemplate.html" target="_blank">WTemplate</a> condition.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14691" target="_blank">Issue #14691</a>:
fixed
<a href="classWt_1_1WTextEdit.html" target="_blank">WTextEdit</a> not correctly
handling margins, especially when in a layout with
<a href="namespaceWt.html#aeb0e4f49ce4a28d8ce9b0c6005027876" target="_blank">LayoutImplementation::JavaScript</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14685" target="_blank">Issue #14685</a>:
fixed
<a href="classWt_1_1WTextEdit.html" target="_blank">WTextEdit</a> ignoring the offsets.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14663" target="_blank">Issue #14663</a>:
Fixed
<a href="classWt_1_1WDate.html" target="_blank">WDate</a> incorrectly handling negative years.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14667" target="_blank">Issue #14667</a>:
fixed a use-after-free that could happen at the destruction of a session.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14704" target="_blank">Issue #14704</a>:
fixed suspicious get requests not being treated as bot requests by some features,
when it should.
</li>
</ul>
<h2>Release 4.14.0 (July 15, 2026)</h2>
<p>Notable changes:</p>
<ul>
<li>
Wt stops supporting being build with C++14. The minimum required C++ standard to build Wt is now C++17.
</li>
<li>
A new tutorial on how localization works in Wt is now available <a href="../../tutorial/localization.html" target="_blank">here</a>.
</li>
</ul>
<p>Wt 4.14.0 is a major release that introduces the following new features:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/13788" target="_blank">Issue #13788</a>:
added color mode support to
<a href="classWt_1_1WTheme.html" target="_blank">WTheme</a>. This is mainly relevant for
<a href="classWt_1_1WBootstrap5Theme.html" target="_blank">WBootstrap5Theme</a>, which introduced this concept to support
dark and light mode.
The color mode can be changed using
<a href="classWt_1_1WTheme.html#a4e17e64908c4882d9263b808210b25b2" target="_blank">WTheme::setColorMode()</a>. Note that you will have
to override this function if you want other themes than
<a href="classWt_1_1WBootstrap5Theme.html" target="_blank">WBootstrap5Theme</a> to support color modes. Some changes to
<a href="classWt_1_1WBootstrap5Theme.html" target="_blank">WBootstrap5Theme</a> custom css for wt have also be made to support
dark mode.
It is also possible to react to color mode changes by connecting to the
<a href="classWt_1_1WApplication.html#ad9f67bae1c1ff7100cd46258553817d4" target="_blank">WApplication::themeColorModeChanged()</a> signal and
to check the preferred color scheme of the client using
<a href="classWt_1_1WEnvironment.html#a9f77d68ae27a0ff1f22a6d3aefe07185" target="_blank">WEnvironment::preferredColorScheme()</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14047" target="_blank">Issue #14047</a>:
added the possibility to define an endpoint to which Content Security Policy (CSP) violation reports are sent by the browser.
This can be configured using the <code>debug-csp</code> and <code>csp-debug-endpoint</code> configuration options in the
<code>wt_config.xml</code> file. Note that this does not requires <code>use-script-nonce</code> to be set to <code>true</code>,
allowing you to debug CSP issues without breaking your application by enforcing it.
Additionally,
<a href="classWt_1_1WCspErrorLogger.html" target="_blank">WCspErrorLogger</a> was added to facilitate logging of CSP
violation reports. This new
<a href="classWt_1_1WResource.html" target="_blank">WResource</a> can be used to log CSP violations
reported by the browser. You can also create your own
<a href="classWt_1_1WResource.html" target="_blank">WResource</a> to handle the reports.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14494" target="_blank">Issue #14494</a>:
added
<a href="classWt_1_1WWidget.html#ab4e595dd2fd53ec3648409e44b58ce32" target="_blank">WWidget::anchorAt()</a>
which anchor the widget to another one using CSS position-area, and in addition, makes the widget disappear when its position-anchor
is scrolled out of view. This is now used by default for
<a href="classWt_1_1WPopupMenu.html" target="_blank">WPopupMenu</a>s inside
<a href="classWt_1_1WPushButton.html" target="_blank">WPushButton</a>.
Additionally, changed
<a href="classWt_1_1WWidget.html#af0df90fe8bbcb42dd057f8c1f1835b49" target="_blank">WWidget::positionAt()</a>
to use CSS position-anchor, when available, to avoid the need reparent the popup widgets while still allowing
them to keep the correct position when the anchor widget is moved due to scrolling.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14213" target="_blank">Issue #14213</a>:
Added
<a href="classWt_1_1Dbo_1_1Query.html#ad95a5bc43cf4f8484574496d42db7738" target="_blank">Wt::Dbo::Query::with()</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/993" target="_blank">Issue #993</a>:
Add the
<a href="classWt_1_1Dbo_1_1NotificationListener.html" target="_blank">Dbo::NotificationListener</a>, which allows to send and receive notifications through a database.
This is currently only implemented for PostgreSQL, but can be implemented for other Dbo by making a custom implementation of the following functions:
<ul>
<li><a href="classWt_1_1Dbo_1_1SqlConnection.html#ab5008c26e355303c276ad847fa9af4a0" target="_blank">Dbo::SqlConnection::subscribe()</a></li>
<li><a href="classWt_1_1Dbo_1_1SqlConnection.html#a1f6d207b50a5b0ed88fa21bb5945dc1a" target="_blank">Dbo::SqlConnection::notify()</a></li>
<li><a href="classWt_1_1Dbo_1_1SqlConnection.html#ab324381df8db923d165bea8b7afa5532" target="_blank">Dbo::SqlConnection::getNextNotify()</a></li>
<li><a href="classWt_1_1Dbo_1_1SqlConnection.html#a0f76caf1e8b8ba6e21fdbf64f2c6a1c5" target="_blank">Dbo::SqlConnection::setupNotify()</a></li>
<li><a href="classWt_1_1Dbo_1_1SqlConnection.html#adb0aee2ce0f35ae4f268e1bceb376b9f" target="_blank">Dbo::SqlConnection::stopListen()</a></li>
</ul>
</li>
<li>
<a href="https://redmine.emweb.be/issues/13499" target="_blank">Issue #13499</a>:
adds support for cookies prefix in Wt::Auth. It is now possible to select the prefix of
the remember-me cookies via the
<a href="classWt_1_1Auth_1_1AuthService.html#a3fd5f9c0e4db84849d13665830ae6b54" target="_blank">AuthService::setAuthTokensEnabled()</a>,
and
<a href="classWt_1_1Auth_1_1AuthService.html#a0b5f5b5ed79f215b44d13861e5adceff" target="_blank">AuthService::setMfaTokenCookiePrefix()</a>
functions. By default the <code>__Secure-</code> is now used when the connection is done over https.
This might break existing applications that rely on
<a href="classWt_1_1Auth_1_1AuthService.html#a14681ebd1a116357762b577f9b770149" target="_blank">AuthService::authTokenCookieName()</a>
or
<a href="classWt_1_1Auth_1_1AuthService.html#a52db9a68ccb2ce29b50a560fe386f49d" target="_blank">AuthService::mfaTokenCookieName()</a>
to return the full name of the cookie, or applications that rely on the remember-me cookie having a specific name.
If that is your case, consider setting the cookie prefix to
<a href="namespaceWt_1_1Auth.html#a9057020ce69c5a162c0766dc63b466a5" target="_blank">AuthCookiePrefix::Empty()</a>.
This also adds some helper classes and functions that can be used to create and retrieve the
value of cookies with prefixes.
The <a href="classWt_1_1Http_1_1SecureCookie.html" target="_blank">Http::SecureCookie</a>
and <a href="classWt_1_1Http_1_1HostCookie.html" target="_blank">Http::HostCookie</a> classes
can be used to easily create cookies with prefix, and the
<a href="classWt_1_1WEnvironment.html#a535ed99087c3e2de6241b0219cdfad4a" target="_blank">WEnvironment::getSecureCookie()</a> and
<a href="classWt_1_1WEnvironment.html#ac9cb11d1d72b5e83b28df76ac7f43fa7" target="_blank">WEnvironment::getHostCookie()</a> can
be used to retrieve the value of cookies with the corresponding prefix from the user's browser.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14571" target="_blank">Issue #14571</a>:
added
<a href="classWt_1_1WTableView.html#a758e93e27af525ca489557bccf459da2" target="_blank">WTableView::incomingIndex()</a>
which allows to retrieve the index of the next cell that is not yet fully visible in the viewport
in the direction of the given corner.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13787" target="_blank">Issue #13787</a>:
added
<a href="classWt_1_1WTableView.html#a606039eb8b7d3e399bdb8024787c1fb8" target="_blank">WTableView::visibleRowCount()</a>
and
<a href="classWt_1_1WTableView.html#adee027fcac266b887c6908e368a68a0b" target="_blank">WTableView::visibleColumnCount()</a>
which allow to retrieve the number of fully visible rows and columns.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14493" target="_blank">Issue #14493</a>:
allowed to ignore bubbling
<a href="classWt_1_1EventSignal.html" target="_blank">EventSignal</a> using
<a href="classWt_1_1EventSignalBase.html#a493ddaa7a9332c7880f6e005c2a0b9cb" target="_blank">EventSignal::ignoreBubbling()</a>.
</li>
</ul>
<p>Wt 4.14.0 also fixes the following bugs:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14476" target="_blank">Issue #14476</a>:
fixed non-modal
<a href="classWt_1_1WDialog.html" target="_blank">WDialog</a> not being able to receive focus
if none of their descendants could. This would make it impossible for the
<a href="classWt_1_1WDialog.html" target="_blank">WDialog</a> to receive any event.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14603" target="_blank">Issue #14603</a>:
fixed
<a href="classWt_1_1WMenu.html" target="_blank">WMenu</a> internal path matching considering
prefix matches as valid even when they did not end on a path segment boundary.
</li>
<li>
<a href="https://redmine.emweb.be/issues/3824" target="_blank">Issue #3824</a>:
resolved a concurrent usage of <a href="classWt_1_1WServer.html#ae8dbb9cc4e418517ee0568a0dd1df182" target="_blank">WServer::localizedStrings()</a>.
This was achieved by making items inside <a href="classWt_1_1WMessageResourceBundle.html" target="_blank">WMessageResourceBundle</a> (namely <code>WMessageResources</code>) thread-safe.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14654" target="_blank">Issue #14654</a>:
fixed compile errors happening when using OpenSSL 4.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14497" target="_blank">Issue #14497</a>:
fixed compilation errors when compiling Wt with C++26.
</li>
</ul>
<p>Wt 4.14.0 also comes with the following improvements:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14078" target="_blank">Issue #14078</a>:
Wt now uses uses the <code>inline-start</code>, <code>inline-end</code>, <code>block-start</code>, and <code>block-end</code>
variants of CSS margin, padding, and border properties. This is mainly an internal change, but it should help decrease
bug related to right-to-left support.
Additionally,
<a href="classWt_1_1WBootstrap5Theme.html" target="_blank">WBootstrap5Theme</a> will now use the RTL version of Bootstrap 5 CSS when
<a href="classWt_1_1WApplication.html#a44c5f0398b5539269be3961b26e95b08" target="_blank">WApplication::setLayoutDirection()</a> is used to set the
layout direction to <code>LayoutDirection::RightToLeft</code>.
With those changes also comes several bug fixes and improvements related to RTL support.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14479" target="_blank">Issue #14479</a>:
added the possibility to configure whether a MIME type should be allowed to be
compressed on the fly by the server when being sent to the client by wthttp. This
can be done by adding a third (optional) column to the MIME type configuration file
with a boolean value indicating whether the MIME type should be compressed or not.
Additionally, excepted for some specific MIME types, wthttp will by default be allowed
to compress any MIME type that are not audio, image, or video.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14468" target="_blank">Issue #14468</a>:
added the possibility to know the visibility state of the application using the new
<a href="classWt_1_1WApplication.html#a4e71102a866d0658a4aaecba80ceeae9" target="_blank">WApplication::visibilityState()</a>, and
to be notified when it changes using the new
<a href="classWt_1_1WApplication.html#af34126f4f6f2b93c98bb99da2507dc22" target="_blank">WApplication::visibilityChanged()</a> signal.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14584" target="_blank">Issue #14584</a>:
added the possibility to change the charts legend and title text color using
<a href="classWt_1_1Chart_1_1WCartesian3DChart.html#a839a0c8cb83b02fdd184e7c01928c221" target="_blank">WCartesian3DChart::setTitleColor()</a>,
<a href="classWt_1_1Chart_1_1WAbstractChart.html#a0850f2aa0b9d5da5dba9f446861d2a49" target="_blank">WAbstractChart::setTitleColor()</a>,
<a href="classWt_1_1Chart_1_1WCartesian3DChart.html#a079171fc181627ed11076763eeca2f97" target="_blank">WCartesian3DChart::setLegendStyle()</a>,
<a href="classWt_1_1Chart_1_1WCartesianChart.html#a5c0beac0ce9183dae3f261c62bfae292" target="_blank">WCartesianChart::setLegendStyle()</a>, and
<a href="classWt_1_1Chart_1_1WPieChart.html#a1976f7ba7c6f4edd5872ba7034f3cfed" target="_blank">WPieChart::setLabelTextColor()</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14550" target="_blank">Issue #14550</a>:
reduced the amount of duplicated JavaScript code generated for signals.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14462" target="_blank">Issue #14462</a>:
added
<a href="classWt_1_1WKeyEvent.html#afaf43407e19769fce1957d84b4056b76" target="_blank">WKeyEvent::keyValue()</a>, which
allows to access the <code>key</code> property of the JavaScript key event that is
sent to the server.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13825" target="_blank">Issue #13825</a>:
it is now possible to remove or update polylines and circles on a
<a href="classWt_1_1WLeafletMap.html" target="_blank">WLeafletMap</a>.
To make this possible, those elements are now represented by the classes
<a href="classWt_1_1WLeafletMap_1_1Polyline.html" target="_blank">WLeafletMap::Polyline</a>
and
<a href="classWt_1_1WLeafletMap_1_1Circle.html" target="_blank">WLeafletMap::Circle</a>
respectively, which are map items, like
<a href="classWt_1_1WLeafletMap_1_1Marker.html" target="_blank">WLeafletMap::Marker</a>
for instance.
These new classes can be added or removed from the map using
<a href="classWt_1_1WLeafletMap.html#a0b855e1d88046ad195b6d02b7123f1f2" target="_blank">WLeafletMap::addPolyline()</a>,
<a href="classWt_1_1WLeafletMap.html#a86e144d405ae4861529875bf5c19271a" target="_blank">WLeafletMap::removePolyline()</a>,
<a href="classWt_1_1WLeafletMap.html#a0e04c48a32a4e6b50cc47537d744fff6" target="_blank">WLeafletMap::addCircle()</a> and,
<a href="classWt_1_1WLeafletMap.html#abf1195588199c9cb0d429b3e95934fb8" target="_blank">WLeafletMap::removeCircle()</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13856" target="_blank">Issue #13856</a>:
added the possibility to change whether widgets are rendered using native controls
by default. This can be done using the new function
<a href="classWt_1_1WWebWidget.html#a2536488d7b48671b3cb3a171c362bcd3" target="_blank">WWebWidget::setDefaultNativeControl()</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12464" target="_blank">Issue #12464</a>:
added the possibility to specify the MIME type when calling
<a href="classWt_1_1WStreamResource.html#a6397570c842aa542bb195b6b31c2dab6" target="_blank">WStreamResource::handleRequestPiecewise()</a>,
allowing to override the MIME type set by
<a href="classWt_1_1WStreamResource.html#aa25f97d38747be9451336422029bbde5" target="_blank">WStreamResource::setMimeType()</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14593" target="_blank">Issue #14593</a>:
added the possibility to configure whether a request with an invalid session ID should be treated
like a bot request or not. This can be configured using the <code>is-invalid-wtd-suspicious</code>
option in the <code>wt_config.xml</code> file. This is mainly usefull when having the
<code>reload-is-new-session</code> option set to <code>false</code>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14557" target="_blank">Issue #14557</a>:
stopped required scripts loading failure from stopping the application from the client side, making it impossible to
recover from such failure. Instead, more detail will be logged about the failure so that developers can decide how to handle it.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14074" target="_blank">Issue #14074</a>:
added the possibility to ignore the current local when using
<a href="classWt_1_1WDate.html#a899adee8d72161fa6bb08509a5e10ec0" target="_blank">WDate::fromString()</a>
or
<a href="classWt_1_1WDateTime.html#a403de3403bdce0885999d28fc53fdfcf" target="_blank">WDateTime::fromString()</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14044" target="_blank">Issue #14044</a>:
added
<a href="classWt_1_1Dbo_1_1Session.html#a359aec75ed8947531c2c8f278ee32b3c" target="_blank">Dbo::Session::transactionCount()</a>
that returns the number of open
<a href="classWt_1_1Dbo_1_1Transaction.html" target="_blank">Dbo::Transaction</a>,
for the <a href="classWt_1_1Dbo_1_1Session.html" target="_blank">Dbo::Session</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14625" target="_blank">Issue #14625</a>:
added the possibility to use a custom random number generator for Wt using
<a href="classWt_1_1WRandom.html#ae641c67f8897a8f4fd1e0701f9aa6a81" target="_blank">WRandom::setGenerator()</a> and
<a href="classWt_1_1WRandom.html#ac4c462df437bfd67370413b9d2609f43" target="_blank">WRandom::setUniformGenerator()</a>.
This can be used in case the default random number generator does not work correctly on a specific platform.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13666" target="_blank">Issue #13666</a>:
bumped the minimum required C++ standard to build Wt to C++17. This means that all uses of <code>WT_CXX17</code> and
<code>WT_CXX17ONLY</code> were removed in Wt's source code. <code>WT_CXX17</code> is now always defined, since Wt requires
C++17.
Additionnaly <code>Wt::cpp17::any</code> is now marked as deprecated, since this only existed because C++14
lacked <code>std::any</code>.
</li>
</ul>
<h2>Release 4.13.4 (July 2, 2026)</h2>
<p>Wt 4.13.4 is a patch release that addresses the following issues:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14615" target="_blank">Issue #14615</a>:
fixed a memory leak sometimes happening when using a spool file.
</li>
</ul>
<p>Wt 4.13.4 also comes with the following improvements:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14630" target="_blank">Issue #14630</a>:
disabled form data caching by default, as it still has some bugs that need to be fixed.
</li>
</ul>
<h2>Release 4.13.3 (June 16, 2026)</h2>
<p>Wt 4.13.3 is a patch release that addresses the following issues:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14513" target="_blank">Issue #14513</a>:
fixed form data sometimes being updated for events where it should not be updated,
or not being updated for events where it should. This was mainly causing issues with
Firefox.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12463" target="_blank">Issue #12463</a>:
made
<a href="classWt_1_1WStreamResource.html#ab83350ee7a4a14ad06965145073b0293" target="_blank">WStreamResource::handleRequestPiecewise()</a>
able to concurrently handle multiple requests correctly.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14150" target="_blank">Issue #14150</a>:
fixed
sub-sub-<a href="classWt_1_1WPopupMenu.html" target="_blank">WPopupMenu</a> sometimes popping
up behind its parent menu.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14575" target="_blank">Issue #14575</a>:
fixed
<a href="classWt_1_1WDateEdit.html" target="_blank">WDateEdit</a> and
<a href="classWt_1_1WTimeEdit.html" target="_blank">WTimeEdit</a> popups missing some style classes when the editor started hidden.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12407" target="_blank">Issue #12407</a>:
fixed submenus wrongly selecting themselves when clearing their selection using
<a href="classWt_1_1WMenu.html#aec1801d047dc0f150d1cc12b801aa6c2" target="_blank">WMenu::select(-1)</a>. This meant that
instead of clearing the selection of a submenu, calling
<a href="classWt_1_1WMenu.html#aec1801d047dc0f150d1cc12b801aa6c2" target="_blank">WMenu::select(-1)</a> would actually
select the first item of the submenu.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14576" target="_blank">Issue #14576</a>:
fixed adding an empty path component or changing a path component to an empty one in a
<a href="classWt_1_1WMenu.html" target="_blank">WMenu</a> would change the selected
item to the one with the empty path component if the
<a href="classWt_1_1WMenu.html" target="_blank">WMenu</a> had internal path enabled.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12073" target="_blank">Issue #12073</a>:
fixed compilation error on windows when compiling <code>wtdbopostgres.lib</code> with C++17 or higher.
</li>
<li>
<a href="https://redmine.emweb.be/issues/10923" target="_blank">Issue #10923</a>:
fixed various entries of <a href="classWt_1_1WEnvironment.html" target="_blank">WEnvironment</a> properties
not being set in
<a href="namespaceWt.html#af4b6ed5fd28b4f5fa141b153c1107349accf2281a355c2c9cd4698ac30bea7820" target="_blank">Widgetset</a> mode.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14527" target="_blank">Issue #14527</a>:
fixed resize handles in layouts adding extra space at the end of a row or column.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12429" target="_blank">Issue #12429</a>:
fixed
<a href="classWt_1_1WAbstractItemView.html" target="_blank">WAbstractItemView</a> not resetting
the sorted column when changing or resetting its model.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14572" target="_blank">Issue #14572</a>:
fixed
<a href="classWt_1_1WAbstractItemView.html#ae68d56771c5e9d408d78b4b9d198967f" target="_blank">WAbstractItemView::scrollTo()</a>
not fully scrolling the column to the left when it should, leading to the right border of the last column being hidden.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14576" target="_blank">Issue #14576</a>:
fixed
<a href="classWt_1_1WTemplate.html" target="_blank">WTemplate</a> with bound widgets executing JavaScript code on the client side when calling
<a href="classWt_1_1WTemplate.html#a98baf277a7dd3144a38edb77cbb3d284" target="_blank">WTemplate::renderTemplate()</a>.
Additionally,
<a href="classWt_1_1WWidget.html#aaae07190fb97d856149226ea315a75d0" target="_blank">WWidget::htmlText()</a> will no longer execute JavaScript code,
but will instead stream the JavaScript code to the optional
<a href="classWt_1_1WStringStream.html" target="_blank">WStringStream</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/9106" target="_blank">Issue #9106</a>:
fixed a race condition that could lead to websocket connections not being closed at the destruction of the session.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14579" target="_blank">Issue #14579</a>:
ensured that
<a href="classWt_1_1WResource.html" target="_blank">WResource</a> suggested file names
fallback for browser that do not support RFC 5987 are sent without non-ASCII characters
to maximize retrocompatibility.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14172" target="_blank">Issue #14172</a>:
fixed
<a href="classWt_1_1WTextEdit.html" target="_blank">WTextEdit</a> making the
application crash when the configured TinyMCE version was not a valid integer.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13907" target="_blank">Issue #13907</a>:
fixed a warning about an incorrect version of TinyMCE sometimes being logged when the correct version was actually used.
</li>
</ul>
<p>Wt 4.13.3 also comes with the following improvements: </p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/12664" target="_blank">Issue #12664</a>:
added the possibility to check whether a
<a href="classWt_1_1Mail_1_1Client.html" target="_blank">Mail::Client</a> is connected
to an SMTP server using
<a href="classWt_1_1Mail_1_1Client.html#a77e59d60fe764dd199a86a7fe922ac9b" target="_blank">Mail::Client::isConnected()</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14473" target="_blank">Issue #14473</a>:
made
<a href="classWt_1_1WDialog.html#a7dd5be946b39806805285cfa7416757f" target="_blank">WDialog::positionAt(WMouseEvent)</a>
also show the dialog.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14045" target="_blank">Issue #14045</a>:
added debug logging when committing or rolling back a
<a href="classWt_1_1Dbo_1_1Transaction.html" target="_blank">Dbo::Transaction</a>.
The case where the transaction is nested, and would not immediately commit, is logged as well.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12815" target="_blank">Issue #12815</a>:
added some clarification to the documentation of
<a href="namespaceWt_1_1Form_1_1Dbo.html" target="_blank">Form::Dbo</a> classes.
</li>
</ul>
<h2>Release 4.13.2 (May 7, 2026)</h2>
<p>Wt 4.13.2 is a patch release that addresses the following issues:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14490" target="_blank">Issue #14490</a>:
fixed form object data not being correctly cached when updated via signal. It seems that
it mainly caused issues with browser auto-fill.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14469" target="_blank">Issue #14469</a>:
fixed
<a href="classWt_1_1WGroupBox.html" target="_blank">WGroupBox</a> being unable to add or insert widgets.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14482" target="_blank">Issue #14482</a>:
fixed
<a href="classWt_1_1WApplication.html#a1918508a02889373a9e1fc1d872f2753" target="_blank">WApplication::focusedWidget()</a>
returning nullptr when the focused widget was inside of a popup.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14488" target="_blank">Issue #14488</a>:
fixed
<a href="classWt_1_1WApplication.html#a60c1defb57949f6f78c6c1373a18e74e" target="_blank">Global key events</a>
not being emitted if connected for the first time after the page had already been loaded by the client.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14481" target="_blank">Issue #14481</a>:
ensured that <code>XHTML</code> content in a <a href="classWt_1_1WPushButton.html" target="_blank">WPushButton</a> is correctly
rendered as such, in case of the content being a localized string, containing an <code>XHTML entity</code>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/7974" target="_blank">Issue #7974</a>:
fixed
<a href="classWt_1_1WPopupMenu.html" target="_blank">WPopupMenu</a> and
<a href="classWt_1_1WPopupWidget.html" target="_blank">WPopupWidget</a>
not avoiding being cut off by the edges of their parent widget when being
positioned.
</li>
<li>
<a href="https://redmine.emweb.be/issues/11704" target="_blank">Issue #11704</a>
fixed Wt not being able to dynamically link against libharu versions 2.4.2 and higher on Windows.
Additionally, the version of libharu bundled with Wt binary releases on Windows has been updated from 2.3.0 to 2.4.6.
</li>
</ul>
<p>Wt 4.13.2 also comes with the following improvements:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14367" target="_blank">Issue #14367</a>:
made it possible to scroll a
<a href="classWt_1_1WTableView.html" target="_blank">WTableView</a> when having the mouse over a
header (column or row) if scrolling in that direction would make that header move.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14466" target="_blank">Issue #14466</a>:
added the possibility to upgrade mariadb-connector-c to version 3.4.8 on windows. The library has been
updated on the windows builds.
</li>
</ul>
<h2>Release 4.13.1 (April 15, 2026)</h2>
<p>Wt 4.13.1 is a patch release that addresses the following issues:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14472" target="_blank">Issue #14472</a>:
delayed the automatic connection of the
<a href="classWt_1_1WWebWidget.html#ae33de6853f17057cb6a8ff06a160b14d" target="_blank">WWebWidget::focussed()</a> signal until the first
render of the widget.
</li>
</ul>
<h2>Release 4.13.0 (April 14, 2026)</h2>
<p>Wt 4.13.0 is a major release that introduces the following new features:</p>
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12968" target="_blank">Issue #12968</a>:
It is now possible to send notifications trough JavaScript notification API using <a href="classWt_1_1WNotification.html" target="_blank">WNotification</a>. You
can see examples of how to use it in the
<a href="https://www.webtoolkit.eu/widgets/notification" target="_blank">Widget Gallery</a>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12967" target="_blank">Issue #12967</a>:
It is now possible to change the favicon of an individual
<a href="classWt_1_1WApplication.html" target="_blank">WApplication</a> using
<a href="classWt_1_1WApplication.html#a2681edc4e1b0edbb22c5e1aa72381101" target="_blank">WApplication::setFavicon()</a>. This takes as parameter a
<a href="classWt_1_1WFavicon.html" target="_blank">WFavicon</a> which is a new class representing favicons. Since the main goal of this feature is to allow developers to notify
the user using the favicon, the WFavicon is mainly designed to make around this idea. While WFavicon is an abstract class, we also added four specialisations of this class.
The
<a href="classWt_1_1WResourceFavicon.html" target="_blank">WResourceFavicon</a> and
<a href="classWt_1_1WUrlFavicon.html" target="_blank">WUrlFavicon</a> are simple specialisations of WFavicon that allows to create a favicon from a
<a href="classWt_1_1WResource.html" target="_blank">WResource</a> or a URL respectively.
The
<a href="classWt_1_1WRasterFavicon.html" target="_blank">WRasterFavicon</a>, uses a
<a href="classWt_1_1WRasterImage.html" target="_blank">WRasterImage</a> to update the favicon (this is only available if WRasterImage is available).
And the
<a href="classWt_1_1WFaviconPair.html" target="_blank">WFaviconPair</a>, can be used to switch between two
<a href="classWt_1_1WFavicon.html" target="_blank">WFavicon</a>.
You can see examples of how to use it in the
<a href="https://www.webtoolkit.eu/widgets/notification/wfavicon" target="_blank">Widget Gallery</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12946" target="_blank">Issue #12946</a>:
Added
<a href="classWt_1_1WBadge.html" target="_blank">WBadge</a>, a new class that represents a badge which is a text
with a special look. Badges are often used to draw the attention, or warn of updates.
It is possible to add a WBadge to a
<a href="classWt_1_1WPushButton.html" target="_blank">WPushButton</a>, to a
<a href="classWt_1_1WMenuItem.html" target="_blank">WMenuItem</a>, (and by extension) to a
<a href="classWt_1_1WTabWidget.html" target="_blank">WTabWidget</a>.
You can see examples of how to use it in the
<a href="https://www.webtoolkit.eu/widgets/notification/wbadge" target="_blank">Widget Gallery</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13785" target="_blank">Issue #13785</a>:
<a href="classWt_1_1WAbstractItemView.html#ae68d56771c5e9d408d78b4b9d198967f" target="_blank">WAbstractItemView::scrollTo()</a> now also
takes the column of the index into account when scrolling to an item. It is now also possible to specify different hints for the row and
column when scrolling to an item.
Additionally, some bugs linked to scrolling were fixed for both
<a href="classWt_1_1WTableView.html" target="_blank">WTableView</a> and
<a href="classWt_1_1WTreeView.html" target="_blank">WTreeView</a>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/7986" target="_blank">Issue #7986</a>:
added caching for form objects data on the server side to reduce the size of the request sent to the server by the client.
This can be disabled by setting the <code>form-data-caching</code> option to <code>false</code> in the <code>wt_config.xml</code> file.
Note that this reduction in request size may come at the cost of an increase response size when updating form objects. It is possible
to limit this impact by changing the <code>form-data-resend-ratio-limit</code> option in the <code>wt_config.xml</code> file.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14305" target="_blank">Issue #14305</a>:
added the possibility to change the format of the access logs using
<a href="classWt_1_1WServer.html#ac513e830dbe4eb582bfc37b27826c7c1" target="_blank">WServer::setAccessLoggerFormat()</a>.
Additionally, the access logger is now accessible through the new
<a href="classWt_1_1WServer.html#acc962bccafdd3345b2d4e39e6b9baf31" target="_blank">WServer::accessLogger()</a> function, which
allows to change the output file of the access logger at runtime. To complement this, it is now also possible to change
whether the access logs are redirected to the standard logger or not using
<a href="classWt_1_1WServer.html#a3aeddcc6ac27fab56874747b3dddee71" target="_blank">WServer::setRedirectAccessLog()</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12940" target="_blank">Issue #12940</a>:
Added
<a href="classWt_1_1WTextF.html" target="_blank">WTextF</a> which is text that can be exposed to the client side. This allows developers to handle updates to the text of a
<a href="classWt_1_1WPaintedWidget.html" target="_blank">WPaintedWidget</a> directly on the client side.
<a href="classWt_1_1WPaintDevice.html" target="_blank">WPaintDevice</a>, and
<a href="classWt_1_1WPainter.html" target="_blank">WPainter</a> have been updated to use WTextF instead of
<a href="classWt_1_1WString.html" target="_blank">WString</a>.
</li>
</ul>
<p>Wt 4.13.0 also fixes the following bugs:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14441" target="_blank">Issue #14441</a>:
fixed segmentation fault that could occur when deleting a
<a href="classWt_1_1WApplication.html" target="_blank">WApplication</a> that had a
<a href="classWt_1_1WDialog.html" target="_blank">WDialog</a> open.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14447" target="_blank">Issue #14447</a>:
fixed
<a href="classWt_1_1WRadioButton.html" target="_blank">WRadioButton</a> never being set to the checked state
from the client side when not being inside a
<a href="classWt_1_1WButtonGroup.html" target="_blank">WButtonGroup</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14416" target="_blank">Issue #14416</a>:
fixed
<a href="classWt_1_1WWebWidget.html#aa140064593fa5f47ebdf26fcf71c4948" target="_blank">WWebWidget::setSelectable(true)</a> preventing selection instead of allowing it.
This caused several widgets to have unselectable text, like in
<a href="https://redmine.emweb.be/issues/14310" target="_blank">issue #14310</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14035" target="_blank">Issue #14035</a>:
fixed
<a href="classWt_1_1WBoxLayout.html#a3484fc08d50ec25c3f596cf6c9aea500" target="_blank">WHBoxLayout::itemAt()</a>,
<a href="classWt_1_1WBoxLayout.html#a3484fc08d50ec25c3f596cf6c9aea500" target="_blank">WVBoxLayout::itemAt()</a>, and
<a href="classWt_1_1WGridLayout.html#a77fef7a57e94c094ca88105874db028b" target="_blank">WGridLayout::itemAt()</a> not checking that
the given index was in the valid range, leading to segfault instead of returning nullptr.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14455" target="_blank">Issue #14455</a>:
fixed widgets in layout with
<a href="namespaceWt.html#aeb0e4f49ce4a28d8ce9b0c6005027876" target="_blank">Wt::LayoutImplementation::Flex</a>
not having their preferred size updated after being resized.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14436" target="_blank">Issue #14436</a>:
fixed some cases where widgets in a layout with
<a href="namespaceWt.html#aeb0e4f49ce4a28d8ce9b0c6005027876" target="_blank">Wt::LayoutImplementation::Flex</a>
would be partially hidden instead of shrinking.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13574" target="_blank">Issue #13574</a>:
fixed
<a href="classWt_1_1WTableView.html" target="_blank">WTableView</a> headers label
alignment when aligning to the right or the center.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14053" target="_blank">Issue #14053</a>:
fixed
<a href="classWt_1_1WAbstractProxyModel.html" target="_blank">WAbstractProxyModel</a> not using the overridden version of
<a href="classWt_1_1WAbstractItemModel.html#a4d7fa5951281dd9b623c9afd7ed9c2ef" target="_blank">WAbstractItemModel::dropEvent()</a> when handling drop events.
</li>
<li>
Fixed
<a href="classWt_1_1WRasterImage.html" target="_blank">WRasterImage</a> unable to read dataUri when using
<a href="http://www.graphicsmagick.org/" target="_blank">GraphicsMagick</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14504" target="_blank">Issue #14504</a>:
fixed
<a href="classWt_1_1WItemDelegate.html#ad846a8933d846fc43394bb6d5fd78d7e" target="_blank">WItemDelegate::editState()</a> and
<a href="classWt_1_1WItemDelegate.html#aa1519431acb606b62b9d4f8faf279d03" target="_blank">WItemDelegate::setEditState()</a>
segfaulting when the editor widget was not a
<a href="classWt_1_1WLineEdit.html" target="_blank">WLineEdit</a>. It will now log an error instead of crashing.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14427" target="_blank">Issue #14427</a>:
fixed a SIGFPE that could happen when using
<a href="classWt_1_1WLocalizedStrings.html#a2f50fd381c0757539a635a9992eebdab" target="_blank">WLocalizedStrings::evaluatePluralExpression()</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14431" target="_blank">Issue #14431</a>:
added a workaround for libc++ not supporting <code>std::chrono::clock_cast</code> yet,
as this was causing a compilation error when compiling with libc++ with c++ version 20.
</li>
</ul>
<p>Wt 4.13.0 also comes with the following improvements:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/13841" target="_blank">Issue #13841</a>:
added the ability to retrieve the currently focused widget in a Wt application using
<a href="classWt_1_1WApplication.html#a1918508a02889373a9e1fc1d872f2753" target="_blank">WApplication::focusedWidget()</a>,
or its ID using
<a href="classWt_1_1WApplication.html#a7e094aee22c9ce9ad74ed76a11e1b109" target="_blank">WApplication::focus()</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/9328" target="_blank">Issue #9328</a>:
improved the positioning of tooltips so that they do not go outside of the screen and
add a vertical scrollbar to the tooltip if necessary.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13789" target="_blank">Issue #13789</a>:
added support for more
<a href="group__signalslot.html#ga34e65660d30e69c56aa636a8856aa52d" target="_blank">Key</a>s in
<a href="classWt_1_1WKeyEvent.html" target="_blank">WKeyEvent</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14209" target="_blank">Issue #14209</a>:
removed all uses of <code>asio::strand::wrap()</code> to avoid deprecated warnings
when compiling Wt with boost 1.90.0 or later.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14459" target="_blank">Issue #14459</a>:
added more strictness to incoming GET requests. In <a href="https://redmine.emweb.be/issues/13970" target="_blank">Issue #13970</a>,
we already ensure that a <code>wtd</code> alone in a new request would be considered suspect. Now we add <code>signal</code> (in itself) as a suspect
parameter too. When combined, they are allowed.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14420" target="_blank">Issue #14420</a>:
made
<a href="classWt_1_1Dbo_1_1collection_1_1iterator.html" target="_blank">Dbo::collection::iterator</a> and
<a href="classWt_1_1Dbo_1_1collection_1_1const__iterator.html" target="_blank">Dbo::collection::const_iterator</a>
default constructible so that
<a href="classWt_1_1Dbo_1_1collection.html" target="_blank">Dbo::collection</a>
can be used inside <code>std::ranges::end()</code>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14467" target="_blank">Issue #14467</a>:
replaced the use of the deprecated <code>unload</code> event with <code>pagehide</code>
to know when a page is being unloaded by the browser.
</li>
</ul>
<h2>Release 4.12.6 (March 17, 2026)</h2>
<p>Wt 4.12.6 is a patch release that addresses the following issues:</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/14376" target="_blank">Issue #14376</a>:
fixed
<a href="classWt_1_1WTableView.html#a4e5900e1c92219763c7b5d4a9e1ac2c5" target="_blank">WTableView::itemWidget()</a>
wrongly returning unrendered widgets when used in plain HTML mode. This could then also lead to a segmentation fault when
trying to modify the headers before the view was rendered.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14066" target="_blank">Issue #14066</a>:
fixed
<a href="classWt_1_1WTableView.html" target="_blank">WTableView</a> header columns not
always having the same height as the content columns, which lead to several issues.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14319" target="_blank">Issue #14319</a>:
fixed <a href="classWt_1_1WTableView.html" target="_blank">WTableView</a> sometimes not updating after
a client-side resize.
Additionally, fixed
<a href="classWt_1_1WTableView.html#a093b661f93551c1d6f73c423ae8ef459" target="_blank">WTableView::scrollTo()</a> with
<a href="namespaceWt.html#ae0fdcefe4b1fefe747b5f423c020334aa47ec5fd00436263c0d6b91bf575ea690" target="_blank">ScrollHint::EnsureVisible</a>
inverting top and bottom.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14332" target="_blank">Issue #14332</a>:
fixed
<a href="classWt_1_1WDialog.html" target="_blank">WDialog</a>'s content being cut off when containing a
<a href="classWt_1_1WTableView.html" target="_blank">WTableView</a> with a width bigger than the dialog itself.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14293" target="_blank">Issue #14293</a>:
fixed
<a href="classWt_1_1WDialog.html" target="_blank">WDialog</a> fitting to its content in
<a href="classWt_1_1WBootstrap2Theme.html" target="_blank">WBootstrap2Theme</a> and
<a href="classWt_1_1WBootstrap3Theme.html" target="_blank">WBootstrap3Theme</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13958" target="_blank">Issue #13958</a>:
corrected a JavaScript error when using <a href="namespaceWt.html#aeb0e4f49ce4a28d8ce9b0c6005027876" target="_blank">Wt::LayoutImplementation::Flex</a>
with a disabled ancestor widget.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13692" target="_blank">Issue #13692</a>:
fixed JS layouts in <a href="classWt_1_1WStackedWidget.html" target="_blank">WStackedWidget</a>
not being updated after being switched in with an animation. This would lead to the
content of the layout being fitted to the size of the old container.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14352" target="_blank">Issue #14352</a>:
fixed compilation error that could happen when using clang with C++20 with the
<code>WT_CPP17_FILESYSTEM_IMPLEMENTATION="std"</code> option.
</li>
<li>
<a href="https://redmine.emweb.be/issues/14395" target="_blank">Issue #14395</a>:
added the scope to some <code>target_compile_definitions</code> where they were missing.
</li>