-
Notifications
You must be signed in to change notification settings - Fork 373
/
Copy pathReleaseNotes.html
7536 lines (6758 loc) · 343 KB
/
ReleaseNotes.html
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.11.3 (TBD)</h2>
<p>
Wt 4.11.3 is a patch release that addresses the following issue:
</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/13261" target="_blank">Issue #13261</a>:
Fixed a bug where
<a href="classWt_1_1WContainerWidget.html#a608f748cbdda763f1a11556ddad9fbe1" target="_blank">WContainerWidget::clear()</a> would not work correctly when using layouts with JavaScript implementation.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13361" target="_blank">Issue #13361</a>:
Wt should now work with boost version 1.87.0 instead of not compiling due to the use
of old boost::asio functions.
</li>
</ul>
<h2>Release 4.11.2 (January 16, 2025)</h2>
<p>
Wt 4.11.2 is a patch release that addresses the following issues:
</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/12935" target="_blank">Issue #12935</a>:
resize handles in layouts now have a fixed height or width instead of them scaling with the spacing of the layout.
</li>
<li>
<a href="https://redmine.emweb.be/issues/10903" target="_blank">Issue #10903</a>:
add support for many common MIME types. Every file of the common types will now be sent with the correct MIME type instead of the default <code>application/octet-stream</code>.
The list comes from <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/MIME_types/Common_types" target="_blank">MDN</a> (taken on September 16, 2024), and is in no way exhaustive.
A way to provide more types will be added soon in <a href="https://redmine.emweb.be/issues/13188" target="_blank">Issue #13188</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12866" target="_blank">Issue #12866</a>:
added the <code><delay-load-at-boot></code> option which can be changed in the configuration file. This option
allows developers to choose whether the loading of the application at boot should be delayed or not. Instead of
immediately calling the loading method, a small delay is introduced to allow additional JavaScript to be executed before
loading. By default this option is set to true, which keeps the delay. This delay can cause the loading of the
application to take a long time in some very specific case. Setting this option to false could however impact any
JavaScript code added at boot time.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13063" target="_blank">Issue #13063</a>:
fixed a bug where setting the HTML tag name of a
<a href="classWt_1_1WWebWidget.html" target="_blank">WWebWidget</a> could lead to a segmentation fault for some tag names.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13366" target="_blank">Issue #13366</a>:
ensure that when the application's working directory and the docroot are not the same directory, the image rendering fallback
will attempt to resolve the image relative to both locations.
This is so that clients that do not have JavaScript enabled, are still able to see the same images as JavaScript-enabled clients.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12860" target="_blank">Issue #12860</a>:
fixed a bug where a
<a href="classWt_1_1WDialog.html" target="_blank">WDialog</a> would not be centered if
<a href="classWt_1_1WDialog.html#a223f8635e38a6e9809b867f247b2185f" target="_blank">WDialog::exec()</a> was called after the <code>WDialog</code> was loaded.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/13082" target="_blank">Issue #13082</a>:
fixed styling of elements in layout not being updated in some cases if the change happened while the layout was hidden.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12951" target="_blank">Issue #12951</a>:
fixed a bug where a layout in a
<a href="classWt_1_1WPanel.html" target="_blank">WPanel</a> may not work properly during and after some animations.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12934" target="_blank">Issue #12934</a>:
fixed a bug in layouts using JavaScript implementation where a widget size could be set higher than it's maximum size, leading to additional space after that widget.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13300" target="_blank">Issue #13300</a>:
fixed a missing fallback in Wt's main JavaScript, when handling browser history navigation (using the back and forward buttons).
In case of rewritten browser history, the retrieval would fail, and encounter an <code>undefined</code> state. Throwing a JavaScript error. This error should be guarded against,
and the fallback should always kick in.
</li>
</ul>
<p>
Wt 4.11.2 also comes with the following improvements:
</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/13187" target="_blank">Issue #13187</a>:
add the possibility to configure headers that are sent in every reply. This can be defined in
the XML config using the <code>http-headers</code> tag.
It is now also possible to configure Wt to use nonces for script by setting the <code>use-script-nonce</code> to <code>true</code>,
to help protect against XSS attack. If you need to serve a script in a
<a href="classWt_1_1WResource.html" target="_blank">WResource</a>, the nonce is available through the
response parameter of the
<a href="classWt_1_1WResource.html#a3a740f8cc29e2e6e4e58defc9c88b8b6" target="_blank">WResource::handleRequest()</a> function by using
<a href="classWt_1_1Http_1_1Response.html#a5ade98a7d1e3edc76f4ffc7634a25298" target="_blank">Http::Response::nonce()</a>.
The nonce is facilitated through the <h href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP" target="_blank">CSP (Content Security Policy) header</a>.
Enabling the nonce will serve CSP headers in your responses. A minimal (fairly nonrestrictive) configuration is taken by default, namely:
<code>Content-Security-Policy: script-src 'nonce-{randomNonce}' 'strict-dynamic' 'unsafe-eval'</code>
This CSP header can be configured in the XML config under <code>http-headers</code> as well. If the nonce is enabled, only MORE restrictive CSP headers will
be allowed by the browser.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12945" target="_blank">Issue #12945</a>:
allow to use icons from
<a href="http://fontawesome.io" target="_blank">Font Awesome</a> in
<a href="classWt_1_1WIconPair.html" target="_blank">WIconPair</a>. This can be done by giving the name of the icon instead of the URI to an image in the constructor. This also means that the icons can either be a
<a href="classWt_1_1WImage.html" target="_blank">WImage</a> or a
<a href="classWt_1_1WIcon.html" target="_blank">WIcon</a>. Accessing the icons of WIconPair using
<a href="classWt_1_1WIconPair.html#a2cb1d36dea7c7f0a145a0ac2e6c2ac0b" target="_blank">WIconPair::icon1()</a> and
<a href="classWt_1_1WIconPair.html#ab3a373c00c3ba582790c31f02f6caf6b" target="_blank">WIconPair::icon2()</a> is now deprecated in favor of
<a href="classWt_1_1WIconPair.html#a3e2e9c090569bc72e859cf05bdef16d7" target="_blank">WIconPair::uriIcon1()</a>,
<a href="classWt_1_1WIconPair.html#a9c70933778493df41c4332b0c6ed4943" target="_blank">WIconPair::uriIcon2()</a>,
<a href="classWt_1_1WIconPair.html#aba22073c807ad08ef1c5122d773573e8" target="_blank">WIconPair::iconNameIcon1()</a>, and
<a href="classWt_1_1WIconPair.html#a90d9fd8fe2e8f9d1ea20efa2098b4385" target="_blank">WIconPair::iconNameIcon2()</a>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/13131" target="_blank">Issue #13131</a>:
make the refresh after
<a href="classWt_1_1WApplication.html#ac0f26388d68e9ebf5962c6bb477b4d83" target="_blank">WApplication::setLocale()</a> optional.
</li>
<li>
<a href="https://redmine.emweb.be/issues/6584" target="_blank">Issue #6584</a>:
add the <code>x-frame-same-origin</code> configuration option that allows to configure whether the header <code>X-Frame-Options: SAMEORIGIN</code> is used or not.
</li>
<li>
<a href="https://redmine.emweb.be/issues/8508" target="_blank">Issue #8508</a>:
make Wt use <code>std::chrono</code> for time zones by default when compiled with C++20 or higher, and allow automatic conversion of
<a href="classWt_1_1WTime.html" target="_blank">WTime</a>,
<a href="classWt_1_1WDateTime.html" target="_blank">WDateTime</a>,
<a href="classWt_1_1WDate.html" target="_blank">WDate</a> and
<a href="classWt_1_1WLocalDateTime.html" target="_blank">WLocalDateTime</a> from/to their <code>std::chrono</code> equivalent. In the case of <code>WDate</code> and <code>WLocalDateTime</code>,
it is only available if <code>std::chrono</code> is used for time zones.
</li>
</ul>
<h2>Release 4.11.1 (November 5, 2024)</h2>
<p>
Wt 4.11.1 is a patch release that addresses the following issues:
</p>
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12675" target="_blank">Issue #12675</a>:
Add built-in type support for
<a href="classWt_1_1Dbo_1_1JsonSerializer.html" target="_blank">Dbo::JsonSerializer</a>. This can be activated by including <code>Wt/Dbo/WtJsonSqlTraits.h</code>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13041" target="_blank">Issue #13041</a>:
Increase the default number of iteration of
<a href="classWt_1_1Auth_1_1BCryptHashFunction.html">Auth::BCryptHashFunction</a> to 12.
A warning message will also be logged when using Auth::BCryptHashFunction with less than the minumum of 10 iterations that ASVS recommends.
</li>
<li>
<a href="https://redmine.emweb.be/issues/11868" target="_blank">Issue #11868</a>:
Added the
<a href="classWt_1_1WStackedWidget.html#a8342aac06b58cdedb7b1f43132673cb8" target="_blank">WStackedWidget::currentWidgetChanged()</a> signal that is emitted when the
<a href="classWt_1_1WStackedWidget.html" target="_blank">WStackedWidget</a> changes the element that it shows.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/13106" target="_blank">Issue #13106</a>:
ensure that the correct <code>disabled</code> class is used on a per-theme basis. This wrongly affected all Bootstrap themes.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/13104" target="_blank">Issue #13104</a>:
a Bootstrap 5 <a href="classWt_1_1WDialog.html" target="_blank">WDialog</a>
is now correctly raised to the front when <a href="classWt_1_1WDialog.html#a113dd08d646491476342e5293c6e36f9" target="_blank">WDialog::raiseToFront()</a>
is called.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12813" target="_blank">Issue #12813</a>:
Added the possibility for each column of
<a href="classWt_1_1WAbstractItemView.html" target="_blank">WAbstractItemView</a> to be set resizable or not independently using the
<a href="classWt_1_1WAbstractItemView.html#a737ab9af521bad7ea7c8acd85023bb66" target="_blank">WAbstractItemView::setColumnResizeEnabled()</a> function.
</li>
<li>
<a href="https://redmine.emweb.be/issues/11855" target="_blank">Issue #11855</a>:
the loading indicator should now be shown directly when the indicator-timeout is set to 0 instead of having a few millisecond delay.
This can be set by the <code><application-settings><indicator-timeout>0</indicator-timeout></application-settings></code> property in the <code>wt_config.xml</code>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/7856" target="_blank">Issue #7856</a>:
Fix a bug where <code>change()</code> and <code>input()</code> signals would sometimes not be emitted by a
<a href="classWt_1_1WSlider.html" target="_blank">WSlider</a> with native control if progressive bootstrap was enabled.
</li>
<li>
<a href="https://redmine.emweb.be/issues/11001" target="_blank">Issue #11001</a>:
Delete the extra space that was sometimes added before the first and after last element of a
<a href="classWt_1_1WBoxLayout.html">WBoxLayout</a> if the spacing was more than twice as big as the margin.
</li>
<li>
<a href="https://redmine.emweb.be/issues/11008" target="_blank">Issue #11008</a>:
ensure that a JavaScript variable that retrieves the index of an item in a layout is called correctly.
</li>
<li>
<a href="https://redmine.emweb.be/issues/13115" target="_blank">Issue #13115</a>:
Fix a bug where a widget removed from a disabled parent widget and added to a different enabled parent widget would still appear disabled.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12174" target="_blank">Issue #12174</a>:
an automated test for Selenium has been added for the widget gallery. This will ensure that for all used widgets, a base case is tested, and JS errors are less likely to be merged.
This is an internal tool, but added to the public repository, as an example. This is likely something many developers would find useful.
</li>
</ul>
<h2>Release 4.11.0 (October 1, 2024)</h2>
<p>
Wt 4.11.0 is a major release. That focuses on authentication and WebSockets.
</p>
<p>
First Wt is now able to support MFA in its authentication system. It is easily enabled with a single call to <a href="classWt_1_1Auth_1_1AuthService.html#aad075b232ddafe52a4953f3c341e6e75" target="_blank">AuthService::setMfaProvider()</a>. By default an implementation for TOTP is included. This offers a way to enable an additional layer of security for your applications. Instead of remembering a single password, users can be made to enter a short code that changes often, as an additional authentication step.
Developers are also able to implement this feature in any way they see fit via the interface <a href="classWt_1_1Auth_1_1Mfa_1_1AbstractMfaProcess.html" target="_blank">AbstractMfaProcess</a>. A couple examples are provided in the source code, and the <a href="../../tutorial/auth.html" target="_blank">authentication tutorial</a>.
</p>
<p>
If you like using WebSockets, there is good news! Wt was already able to communicate with its server over WebSockets. This was, however, limited to only its communication for updates regarding its framework. Now you are able to use them in whatever custom way you see fit. Developers can set up endpoints (both session-private or public) that listen to incoming requests. The browser (or another client) can then use those endpoints to connect to said resource. A connection has now been established, and messages can be send back and forth.
</p>
<h3>New features</h3>
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11705">Issue #11705</a>:
MFA (Multi-Factor Authentication) is now supported by means of a default implementation of TOTP (Time-Based One-Time Password). This feature can be enabled by <a href="classWt_1_1Auth_1_1AuthService.html#aad075b232ddafe52a4953f3c341e6e75" target="_blank">AuthService::setMfaProvider()</a>, and the length of the expected code can be managed via <a href="classWt_1_1Auth_1_1AuthService.html#a8a1821d0e0824a648aee4c509a2bc7d1" target="_blank">AuthService::setMFACodeLength()</a>.
Once enabled, users are allowed (but not forced) to use MFA. A developer will have to create a way that allows users to set their secret key, or override the functionality that decides whether the MFA step ought to be shown to the user during the login process (<a href="classWt_1_1Auth_1_1AuthModel.html#af2083a59fc1458c1fb0020bec0cdf959" target="_blank">AuthModel::hasMfaStep()</a>). Alternatively, they can also set <a href="classWt_1_1Auth_1_1AuthService.html#a5c708962311456a67c07e25c03247b23" target="_blank">AuthService::setMFARequired()</a> to <code>true</code>, which will force all users to have MFA enabled.
If enabled and required, a user will see the <a href="classWt_1_1Auth_1_1Mfa_1_1TotpProcess.html" target="_blank">TotpProcess</a> when they pass the regular login. This will happen after password login. Developers can use this process to enable MFA on a per-user manner, without globally enforcing it.
This widget shows them a QR code and a secret key initially for them to store in an authenticator app or browser extension. Once stored, it will no longer show them this code or key, unless invalidated (by means of <a href="classWt_1_1Auth_1_1User.html#ac65b7e7277df1d8cd4805e0b4d13b29d" target="_blank">User::removeIdentity()</a>, which will take the same name as the <code>setMfaProvider()</code>).
<p>The above approach will be the default flow that Wt uses if MFA is enabled (and/or required). Developers are able to provide a custom implementation as well, using the <a href="classWt_1_1Auth_1_1Mfa_1_1AbstractMfaProcess.html" target="_blank">AbstractMfaProcess</a> class. It is encouraged to look at the examples under <code>examples/authentication/mfa</code> in the source code, to have a concrete idea on how to use the class correctly.</p>
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12461" target="_blank">Issue #12461</a>:
Developers are now able to connect to a public or private resource using the <a href="https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API" target="_blank">WebSocket protocol</a>. While WebSockets were already integrated into Wt, they were only used to stream updates between the server and the client as an alternative to long-polling.
Now they can actually be used by developers for custom purposes. The <a href="classWt_1_1WWebSocketResource.html" target="_blank">WWebSocketResource</a> is used to create a new endpoint. This can be global (static), when linked to the WServer itself, or session-private (dynamic) when exposed in the WApplication.
When a connection from the client side is established, a <a href="classWt_1_1WWebSocketConnection.html" target="_blank">WWebSocketConnection</a> is created. This serves as a way to track a singular connection between the server and a client.
</li>
</ul>
<h3>Other improvements</h3>
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/10382" target="_blank">Issue #10382</a>:
Added customization support for the upload mechanism of
<a href="classWt_1_1WFileDropWidget.html">WFileDropWidget</a>.
It is now possible to customize the server-side upload mechanism by returning a custom WResource from
<a href="classWt_1_1WFileDropWidget.html#a149fa0f12016c615c1763046dc2f7333">WFileDropWidget::uploadResource()</a>
to be uploaded to.
At the client side, uploading can be modified by setting <code>wtUseCustomSend</code> and defining <code>wtCustomSend()</code>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12320" target="_blank">Issue #12320</a>:
allows for the "Cache-Control" header to be specified for the <a href="classWt_1_1WServer.html">WServer</a>. This is to be passed as a command-line option when running the <code>WServer</code>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11600" target="_blank">Issue #11600</a>:
added unit tests for <a href="classWt_1_1Form_1_1WAbstractFormDelegate.html">WFormDelegate</a> classes.
</li>
</ul>
<h3>Bug fixes</h3>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/12367" target="_blank">Issue #12367</a>:
Fix a bug where the checkbox in a
<a href="classWt_1_1WPopupMenu.html" target="_blank">WPopupMenu</a> would not be checked if a
<a href="classWt_1_1WMenuItem.html" target="_blank">WMenuItem</a> was clicked, and not the
<a href="classWt_1_1WCheckBox.html" target="_blank">WCheckBox</a> or its label. Also fixes a bug where the signal of a <code>WMenuItem</code> checkbox would not be emitted after switching between the item being checkable or not.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12676" target="_blank">Issue #12676</a>:
although technically an improvement, since it was left for so long, it became a bug with Boost 1.85.0.
The version retired the <a href="https://live.boost.org/doc/libs/1_84_0/boost/filesystem/convenience.hpp" target="_blank">boost/filesystem/convenience.hpp</a> header. And also removed some <a href="https://www.boost.org/doc/libs/1_84_0/libs/filesystem/doc/reference.html#path-deprecated-functions" target="_blank">deprecated functions</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12737" target="_blank">Issue #12737</a>:
cancel every action on a socket before closing it to avoid reading on a closed socket.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12323" target="_blank">Issue #12323</a>:
does no longer cause an issue when a <a href="classWt_1_1WMenu.html#a92e4b0124610afda2f48a126ebed3b66" target="_blank">WMenu::addSeparator()</a> was added, together with using <a href="classWt_1_1WBootstrap5Theme.html" target="_blank">WBootstrap5Theme</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12366" target="_blank">Issue #12366</a>:
Fixed a bug where some
<a href="classWt_1_1WContainerWidget.html" target="_blank">WContainerWidget</a> would send undefined information when TwoPhaseRenderingThreshold was not set to 0.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12538" target="_blank">Issue #12538</a>:
correctly implement the <a href="https://datatracker.ietf.org/doc/html/rfc5322#section-3.6.3" target="_blank">RFC5322 specification</a> for mail messages. The "To:" and "Cc:" fields are now correctly placed on a single line. With multiple addresses this results in a comma-separated list of addresses.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/9284">Issue #9284</a>:
a <a href="classWt_1_1WTableView.html" target="_blank">WTableView</a> will now render more correctly in layouts. A combination of various layouts could lead to the table not setting its size correctly, or even not having a consistent size (apparently randomly deciding
to fill in all available space, or to shrink to fit its content). This led to the issue where scrollbars were sometimes not visible, or were placed in a wrong location. By default, a table will now size correctly, and place the scrollbars accordingly, namely at the edges of its container.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11954" target="_blank">Issue #11954</a>:
resolve a fairly big memory leak when using Pango. Pango is a library that is by default enabled (controlled using the <code>ENABLE_PANGO</code> build flag). This library is used to generate PDFs with the <a href="classWt_1_1Render_1_1WPdfRenderer.html">WPdfRenderer</a>.
The font map that Pango generated to track available fonts was never correctly released. Some other Pango specific objects (resulting from calls to the library), such as the context and fonts were also not always released. These objects are now managed by smart pointers to ensure proper memory management.
A single leak does remain, which seemingly comes from Pango or libfontconfig itself (see: <a href="https://redmine.webtoolkit.eu/issues/12844" target="_blank">Issue #12844</a>).
</li>
</ul>
<h2>Release 4.10.4 (March 6, 2024)</h2>
<p>
Wt 4.10.4 is a (smaller) patch release that addresses the following issues.
This release is somewhat smaller due to bigger features being in the works.
Developers can expect some bigger new features in the authentication framework soon!
</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/11685">Issue #11685</a>:
render child widgets differently when updating an existing widget. The JavaScript code that is being called by the framework to dynamically add children to an HTML element was changed so that it always appends them instead of setting the whole content. This is to avoid a widget that was added in JavaScript (with no C++ counterpart) from being overwritten if the HTML of the parent would be written to.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12283" target="_blank">Issue #12283</a>:
this corrects an additional mistake, made on top of <a href="https://redmine.webtoolkit.eu/issues/12006" target="_blank">Issue #12006</a>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12145" target="_blank">Issue #12145</a>:
a change to the internal enum class <a href="namespaceWt.html#aeb01f25d7c9d4a4498fb3dadc8d168c5">Property</a> caused an index and its value to be out of sync for a couple values.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12352" target="_blank">Issues #12352</a>:
this corrects a potential crash in Boost spirit, where a grammar parser could encounter a floating point exception, when trying to evaluate unsafe divisions.
</li>
</ul>
<h2>Release 4.10.3 (December 20, 2023)</h2>
<p>
Wt 4.10.3 is a patch release that addresses the following issues:
</p>
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12158">Issue #12158</a>:
this corrects a mistake in <a href="https://redmine.webtoolkit.eu/issues/7814">Issue #7814</a>, where the cookie path was not correctly set.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11934">Issue #11934</a>:
this corrects the rendering of a vertical <a href="classWt_1_1WSlider.html">WSlider</a> for all themes. Additionally an improvement was made that introduces <a href="classWt_1_1WSlider.html#a0405e2a5aeb71db1b112fa2ca1428cdc">WSlider::setTickLength</a>, that allows users to set the length (width or height of the line, depending on whether the <code>WSlider</code> is <code>Orientation::Horizontal</code> or <code>Orientation::Vertical</code>) of the ticks.
For the native slider, ticks have also been enabled. Although both the positioning (the side on which ticks are placed) and their length cannot be changed. Only their interval can be manipulated through <a href="classWt_1_1WSlider.html#a3497303ace2820b3bd457119cec35411">WSlider::setTickInterval</a>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12005">Issues #12005</a>:
a step value can now be set on a <a href="classWt_1_1WSlider.html">WSlider</a>, using <a href="classWt_1_1WSlider.html#a6f09f1de583156a361a090abc5ec6427">WSlider::setStep</a>.
This functions for both the native and non-native sliders. By default the step value is set to 1.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12022">Issue #12022</a>:
solves a case where a JavaScript error can occur if an invisible element on the page receives an update. This is related to <a href="https://redmine.emweb.be/issues/11669">Issue #11669</a>.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12148">Issue #12148</a>:
attributes on the main page's <html> and <body> tags can now be specified. The new functions are:
<ul>
<li><a href="classWt_1_1WApplication.html#adc77a51995fb3e8224f8bd3cbb5fab86">WApplication::setHtmlAttribute</a></li>
<li><a href="classWt_1_1WApplication.html#a555b48a49d202f1db80abc9dad91b61c">WApplication::setBodyAttribute</a></li>
</ul>
</li>
<li>
<a href="https://redmine.emweb.be/issues/12143">Issue #12143</a>:
covered an edge case of <a href="https://redmine.webtoolkit.eu/issues/12006">Issue #12006</a>, that caused JavaScript errors.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12036">Issue #12036</a>:
ensures that if a <a href="classWt_1_1WCheckBox.html">WCheckBox</a> and <a href="classWt_1_1WRadioButton.html">WRadioButton</a> have a custom style class, it remains in place after applying the <a href="classWt_1_1WBootstrap5Theme.html">WBootstrap5Theme</a>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11960">Issue #11960</a>:
remove an <a href="https://ibpp.sourceforge.io/">IBPP</a> deprecation warning.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11772">Issue #11772</a>:
some warnings in the code were fixed, so that the build process will produce less output, resulting in a cleaner build step.
</li>
</ul>
<h2>Release 4.10.2 (November 8, 2023)</h2>
<p>
Wt 4.10.2 is a patch release that addresses the following issues:
</p>
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11932">Issue #11932</a>:
when calling <a href="classWt_1_1WPushButton.html#ae919cb76993211553b50a996bdf80fe9">WPushButton::setMenu</a> after a <a href="classWt_1_1WPopupMenu.html">WPopupMenu</a> had already been added,
the second menu wasn't added to the button, and both <code>WPopupMenu</code>s were removed. Now, the new <code>WPopupMenu</code> is correctly added to the button.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11974">Issue #11974</a>: when dynamically making a field visible in <a href="classWt_1_1Form_1_1Dbo_1_1FormView.html">FormView</a> the form would only show the label and not the corresponding widget. This has now been corrected by having <code>FormView</code> override <a href="classWt_1_1WTemplateFormView.html#ab8ba5bda25fbf612903e5e0fa52f75ae">createFormWidget</a>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11984">Issue #11984</a>:
corrected <a href="classWt_1_1WTableView.html">WTableView</a>'s drag & drop functionality. When a <a href="classWt_1_1WAbstractItemModel.html">WAbstractItemModel</a>'s items have the flags for drag & drop enabled (found in <a href="group__modelview.html#ga1d77c4de293aebfacbdde124de06b8b0">ItemFlag</a>), the <a href"classWt_1_1WAbstractItemView.html">WAbstractItemView</a> has <a href="classWt_1_1WAbstractItemView.html#a0ca99b835708d990b90000917045738e">setDragEnabled(true)</a> and <a href="classWt_1_1WAbstractItemView.html#a5469c23ea1e9066e98e832ec9da2af21">setEnabledDropLocations()</a> set to <a href="namespaceWt.html#a46e584f830f2d8c9f5b16fcee7affc9b">DropLocation::BetweenRows</a>, the view will now correctly drop the items at the location indicated by the cursor, and will no longer cause an issue when moving the cursor out of the table when dragging.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11890">Issue #11890</a>:
if a user were to delete a <a href="classWt_1_1WPopupWidget.html">WPopupWidget</a>, which they can do as detailed in the <a href="classWt_1_1WPopupWidget.html#details">documentation</a>, they would encounter a use-after-free.
This has been corrected, so that the content of a <code>WPopupWidget</code> can be removed when being hidden.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11985">Issue #11985</a>:
ensures that if a <a href="classWt_1_1WStringListModel.html">WStringListModel</a> is used in a <a href="classWt_1_1WTableView.html">WTableView</a> that allows drag & drop, the content of the
model is correctly updated.
</li>
<li>
<a href="https://redmine.emweb.be/issues/12012">Issue #12012</a>:
due to an oversight in <a href="https://redmine.webtoolkit.eu/issues/10512">Issue #10512</a>, the keyboard and mouse events for a <a href="classWt_1_1WTreeView.html">WTreeView</a>'s node were missing.
</li>
<a href="https://redmine.emweb.be/issues/11882">Issue #11882</a>:
the <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/fieldset">fieldset</a> element, used by <a href="classWt_1_1WGroupBox.html">WGroupBox</a> has been corrected when using Bootstrap 5.
A default HTML value was used here, which caused the content to not be rendered correctly.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/12006">Issue #12006</a>
a JavaScript error could occur if no semicolon was added to the JS code when called by <a href="classWt_1_1WWidget.html#ab876fc1b7d2e4e5dfc631e380d406ae2">setJavaScriptMember</a> or <a href="classWt_1_1DomElement.html#a76e75e4259fee4d00f15170eb464682e">callJavaScript</a>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11897">Issue #11897</a>:
fixed a log that was not configurable. The response to a HTTP request was always logged (like <code>GET /path contentlength</code>).
All logs should be configurable, hence it is now logged under <code>info:wthttp</code>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11959">Issue #11959</a>:
the <code>GetOnePixel</code> deprecation warning from GraphicsMagick was removed.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/7196">Issue #7196</a>:
remove a deprecated Pango call. If you compile with Pango enabled, you will no longer see the warning that <code>pango_fc_font_(un)lock_face</code> is deprecated.
</li>
</ul>
<h2>Release 4.10.1 (September 20, 2023)</h2>
<p>
Wt 4.10.1 is a patch release that addresses the following issues:
</p>
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/10512">Issue #10512</a>:
ensures that the disabled state of any <a href="classWt_1_1WWebWidget.html">WWebWidget</a> or <a href="classWt_1_1WCompositeWidget.html">WCompositeWidget</a> is correctly propagated to its children.
Before, if a user set a widget as disabled that contained children like a <a href="classWt_1_1WMenu.html">WMenu</a>, a new <a href="classWt_1_1WMenuItem.html">WMenuItem</a> could be added, that was enabled.
For some of the affected widgets, this meant that the new item could not be selected, since the signal was not exposed, but in some cases, like with a <code>WMenu</code> this was still possible.
The disabled state of a widget now propagates to its children so that a disabled state can be set consistently for a parent. This doesn't actually set <a href="classWt_1_1WCompositeWidget.html#af0186120a0adf80edbc11bc600913ce0">setDisabled()</a> of the children.
This state can be set separately to manage the child's disabled state without regard to its parent.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11804">Issue #11804</a>:
the <a href="classWt_1_1WEmailValidator.html">WEmailValidator</a> was corrected. There was a missing case in the client side regex that did not allow a hyphen in the domain of an email address.
The server side regex was correct, but nevertheless the case has been added to the tests.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/7645">Issue #7645</a>:
a <a href="classWt_1_1WAnchor.html">WAnchor</a> loaded through JavaScript, with progressive bootstrap will correctly add an empty "href" attribute.
This allows the item to be selected on the page by pressing the Tab button, allowing keyboard navigation.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11848">Issue #11848</a>:
this corrects an edge-case in <a href="classWt_1_1WSuggestionPopup.html">WSuggestionPopup</a> where forcibly displaying the pop-up via C++ code would cause it to be unfiltered.
</li>
<li>
This is a combination of <a href="https://redmine.webtoolkit.eu/issues/9595">Issue #9595</a> and <a href="https://redmine.webtoolkit.eu/issues/9596">Issue #9596</a>:
where the Postgres backend will again rely on standard library functionality (which was substituted in <a href="https://redmine.webtoolkit.eu/issues/9490">Issue #9490</a> for <a href="https://www.boost.org/doc/libs/1_65_0/libs/spirit/doc/html/spirit/introduction.html">boost::spirit</a>).
This implementation, however, caused the loss of some precision with floats and doubles. The conversion from and to string now happens with the standard library <a href="https://en.cppreference.com/w/cpp/header/charconv">charconv</a>, which is available in C++17 (or in C++14 as an extension).
In case this library is not available, Wt will fall back to <a href="https://en.cppreference.com/w/cpp/string/basic_string/stof">std::stof</a> and <a href="https://en.cppreference.com/w/cpp/string/basic_string/stof">std::stoi</a>, but will still use <code>boost::spirit</code> in case of subnormals (which would result in an out_of_range exception).
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11769">Issue #11769</a>:
The MySQL backend will now correctly catch the <a href="https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html#error_er_client_interaction_timeout">ER_CLIENT_INTERACTION_TIMEOUT</a> error.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11302">Issue #11302</a>:
when closing a HTTP socket, it was possible that the server just started handling a TCP/SSL request. This resulted in a free-after-use for the listener.
The listener is now first checked, so we do not get this race condition.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11408">Issue #11408</a>:
fixed several concurrency issues in the wthttp library.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11852">Issue #11852</a>:
the <a href="classWt_1_1Mail_1_1Message.html">Message</a>'s date header was corrected. In case that a localized abbreviation was defined for the month or day, this string was placed in the header.
Some providers / exchanges may reject these emails, since they follow RFC-5322 (<a href="https://www.rfc-editor.org/rfc/rfc5322#page-14">see here</a>) and expect English names.
</li>
</ul>
<h2>Release 4.10.0 (May 30, 2023)</h2>
<p>
Wt 4.10.0 mainly features back-end improvements and some new features that provide some convenience.
There were some issues with persisting dates and time in Sqlite3.
</p>
<p>
In some cases user will have to change some things about their CMake set-up:
If users wish to use <code>OpenGL</code>, they may need to provide a <code>GLEW</code> installation with <code>GLEW_ROOT</code>,
since <code>GLEW</code> is no longer bundled with Wt.
</p>
<h3>New features</h3>
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/7279">Issue #7279</a>:
added <a href="classWt_1_1WEmailEdit.html">WEmailEdit</a> and
<a href="classWt_1_1WEmailValidator.html">WEmailValidator</a>, implementing
a <code><input type="email"></code>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/8760" target="_blank">Issue #8760</a>:
extended <a href="classWt_1_1Auth_1_1AuthWidget.html">Auth::AuthWidget</a> with the option to resend verificiation emails. When email verification is configured to be required and the email somehow got lost, the user would be stuck not being able to log in.
When the user tries to log in now, an info message will be shown saying they need to verify their email first along with a new button to resend the verification email. The user must then enter the email address again in a dialog before the email is sent.<br/>
The virtual methods <a href="classWt_1_1Auth_1_1AuthWidget.html#a42f87508868746e5ccef5695fcbd8763">AuthWidget::letResendEmailVerification()</a> and <a href="classWt_1_1Auth_1_1AuthWidget.html#af45dea06ac5751e96499d62507fea69d">AuthWidget::createResendEmailVerificationView()</a> can be used to customize the UI.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/7814" target="_blank">Issue #7814</a>:
The <code>SameSite</code> attribute of the <code>Set-Cookie</code> HTTP header is now rendered by Wt. To avoid adding yet another parameter to the <code>WApplication::setCookie()</code> method, the class <a href="classWt_1_1Http_1_1Cookie.html">Http::Cookie</a> was introduced that allows configuring all cookie attributes using setters. Objects of this type can be passed to the new <a href="classWt_1_1WApplication.html#a5a76e2ae72a7ba5624c3dc12897728f5">setCookie()</a> and <a href="classWt_1_1WApplication.html#add89ecede3de74cb2338337ca730b2dc">removeCookie()</a> methods in <code>WApplication</code>.
</li>
</ul>
<h3>Other improvements</h3>
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11384" target="_blank">Issue #11384</a>:
it was possible for
<a href="classWt_1_1Mail_1_1Client.html#af7bf43e793d265034c6cb343636b4024">Mail::Client::connect()</a> to
throw an exception if the DNS resolver failed to resolve the SMTP server's hostname. We changed this to
log an error and return <code>false</code> instead (as indicated by its documentation).
<a href="classWt_1_1Mail_1_1Client.html#a958089e2b169f9baed3107b40b958bb9">Mail::Client::send()</a> could
cause a null pointer to be dereferenced, either because a TLS connection was attempted while Wt was
built without OpenSSL, or because the user did not call
<a href="classWt_1_1Mail_1_1Client.html#af7bf43e793d265034c6cb343636b4024">Mail::Client::connect()</a> first.
<code>send()</code> was fixed to log an error and return <code>false</code> instead.
</li>
<li>
<a href="classWt_1_1WServer.html#aa17f85dc130b616b3fcf63aa857ff579">WServer::addResource()</a>
can now take a <code>shared_ptr</code> instead of a raw pointer,
enforcing that the resource lives at least as long as the server, unless removed with
<a href="classWt_1_1WServer.html#a9f5a82118198a1d2341fb89572fd8693">WServer::removeEntryPoint()</a>.
The overload that takes a raw pointer is now deprecated.
This also fixes <a href="https://redmine.webtoolkit.eu/issues/11301" target="_blank">issue #11301</a>, where there
could be a use-after-free in <code>test.http</code>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11412" target="_blank">Issue #11412</a>:
shift-click to open a new window did not work for links to internal paths. Shift-click is now handled by the browser, like ctrl- and meta-click.
</li>
<li>
<a href="https://redmine.emweb.be/issues/11604" target="_blank">Issue #11604</a>:
added a virtual destructor to <a href="classWt_1_1Form_1_1WAbstractFormDelegate.html">WAbstractFormDelegate</a>
to ensure proper deletion and explicitly removed the copy and move constructor and assignment operator.
</li>
<li>
<a href="https://redmine.emweb.be/issues/11562" target="_blank">Issue #11562</a>:
The tutorials
(<a href="../../tutorial/wt.html" target="_blank">Wt</a>,
<a href="../../tutorial/dbo.html" target="_blank">Dbo</a>, and
<a href="../../tutorial/auth.html" target="_blank">Auth</a>)
were updated to be built with Asciidoctor instead of the legacy Python implementation,
its style was updated to match the JWt website style, and the text was brought up to
date a bit. The blog example was likewise updated to use Asciidoctor.
</li>
<li>
<a href="https://redmine.emweb.be/issues/11210" target="_blank">Issue #11210</a>:
<a href="classWt_1_1WTable.html#a03df7cedfb502dcc010493d4a71ee53c">WTable::headerCount()</a>
has been made <code>const</code>.
</li>
<li>
The obsolete CMake options
<code>ENABLE_EXT</code>, <code>WT_NO_STD_LOCALE</code> and <code>WT_NO_STD_WSTRING</code>
were removed.
</li>
</ul>
<h3>Bug fixes</h3>
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11426" target="_blank">Issue #11426</a>:
<a href="classWt_1_1Dbo_1_1backend_1_1Sqlite3.html">Sqlite3</a>:
fixed multiple issues with dates and timestamps:
<ul>
<li>
Timestamps before 1970 would not be saved properly on Windows, because of limitations
of the <code>gmtime</code> function on Windows. The new implementation uses the
<a href="https://github.com/HowardHinnant/date" target="_blank">date</a>
library instead.
</li>
<li>
There was a bug in the conversion to a date time string if
<a href="namespaceWt_1_1Dbo_1_1backend.html#a834555b81f67cf1e17b6e73d1a948067">ISO8601AsText</a>
was set as the
<a href="classWt_1_1Dbo_1_1backend_1_1Sqlite3.html#a571f4019950aafc2b855d46d4e7072d5">date time storage</a>.
For timestamps before 1970 the millisecond part would be saved as a negative integer, e.g.
December 31, 1969 23:59:59.999 would be saved as
<code>1970-01-01T00:00:00.0-1</code> instead of <code>1969-12-31T23:59:59.999</code>.
</li>
<li>
There was a bug in the conversion to and from Julian days if
<a href="namespaceWt_1_1Dbo_1_1backend.html#a834555b81f67cf1e17b6e73d1a948067">JulianDaysAsReal</a>
was set as the
<a href="classWt_1_1Dbo_1_1backend_1_1Sqlite3.html#a571f4019950aafc2b855d46d4e7072d5">date time storage</a>.
The decimal part was divided by 1000, and it was ahead by 12 hours due to it using
midnight rather than noon 1 January 4713 BCE as the reference timestamp. It is now
consistent with SQLite's own
<a href="https://sqlite.org/lang_datefunc.html" target="_blank">julianday()</a>
function.
</li>
<li>
There was a bug in the conversion to UNIX timestamps if
<a href="namespaceWt_1_1Dbo_1_1backend.html#a834555b81f67cf1e17b6e73d1a948067">UnixTimeAsInteger</a>
was set as the
<a href="classWt_1_1Dbo_1_1backend_1_1Sqlite3.html#a571f4019950aafc2b855d46d4e7072d5">date time storage</a>.
The date part was discarded, and the time was saved as a number of milliseconds instead of seconds.
</li>
</ul>
</li>
<li>
<a href="https://redmine.emweb.be/issues/11578" target="_blank">Issue #11578</a>:
fixed an issue with the <a href="namespaceWt_1_1Form_1_1Dbo.html">Dbo forms</a> not correctly validating
invalid <a href="classWt_1_1WDate.html">WDate</a> and <a href="classWt_1_1WTime.html">WTime</a> values
causing the forms to clear the values. Now the forms will give a validation error and prompt the user to
correct it before saving the form.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11377" target="_blank">Issue #11377</a>:
when using wtisapi with WebSockets enabled in the <code>wt_config.xml</code>, Wt would
try and fail to establish a WebSockets connection (this is not supported by ISAPI). Wt
now disables WebSockets (and notifies this in the logs) when using ISAPI.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11423" target="_blank">Issue #11423</a>:
<a href="classWt_1_1WResource.html#a12b871c53120ad1c7c708210f60422be">WResource::internalPath()</a>
now returns the empty string for static resources, since it doesn't make sense for static resources.
</li>
<li>
<a href="https://redmine.emweb.be/issues/10485" target="_blank">Issue #10485</a>:
fixed an issue where Wt would not build on Apple platforms with <code>ENABLE_OPENGL=ON</code>.
This changes the CMake setup, so that we now rely on built-in <a href="https://cmake.org/cmake/help/latest/module/FindOpenGL.html" target="_blank">FindOpenGL</a> and <a href="https://cmake.org/cmake/help/latest/module/FindGLEW.html" target="_blank">FindGLEW</a> modules.
As a consequence, the bundled GLEW installation was removed. This means that a GLEW installation will need to be
provided when building Wt from source. CMake will find GLEW if it is installed in a standard location.
The <code>GLEW_ROOT</code> CMake variable can be used if it is installed elsewhere.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11376" target="_blank">Issue #11376</a>:
fixed an issue with redirects when using wtfcgi.
</li>
</ul>
<h2>Release 4.9.2 (April 18, 2023)</h2>
<p>
Wt 4.9.2 is a patch release that addresses the following issues:
</p>
<ul>
<li>
<a href="https://redmine.emweb.be/issues/11262" target="_blank">Issue #11262</a>:
fixed an issue where 32 bit Linux builds could cause <code>stat()</code> to
fail with <code>EOVERFLOW</code>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11424" target="_blank">Issue #11424</a>:
fixed redundant calls of
<a href="classWt_1_1WDialog.html#afe7c5f57ddb5fd1bc67334c931401e98">WDialog::setClosable(false)</a>
causing a "widget not in container" error to be logged.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/10908" target="_blank">Issue #10908</a>:
fixed an issue with
<a href="classWt_1_1WBootstrap5Theme.html">WBootstrap5Theme</a>
where the selection of a
<a href="classWt_1_1WSuggestionPopup.html">WSuggestionPopup</a>
was not updated when using the arrow keys. We also made sure to scroll the currently
selected option into view when selected using the arrow keys.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11433" target="_blank">Issue #11433</a>:
fixed a regression in the treeview-dragdrop example where dropping a file on the folder view was not working anymore.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11496" target="_blank">Issue #11496</a>:
<a href="classWt_1_1Auth_1_1Saml_1_1Service.html">Saml::Service</a>:
added missing implementation for
<a
href="classWt_1_1Auth_1_1Saml_1_1Service.html#ae6be709a6ebc43302425da239622c05b">setAuthnContextComparison()</a>
and properly implemented
<a
href="classWt_1_1Auth_1_1Saml_1_1Service.html#aa5cca89e64b80cc66fcff8f64fda4360">setNameIdPolicyAllowCreate()</a>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11379" target="_blank">Issue #11379</a>:
fixed a JavaScript error in <a href="classWt_1_1WPaintedWidget.html">WPaintedWidget</a>.
</li>
</ul>
<h2>Release 4.9.1 (January 20, 2023)</h2>
<p>
Wt 4.9.1 is a patch release that addresses the following issues:
</p>
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11230" target="_blank">Issue #11230</a>:
fixed an issue with
<a href="classWt_1_1WApplication.html#a5c811d91d3999ac881ce87bebaade864">WApplication::suspend()</a>
where widgets would incorrectly believe they were still
<a href="classWt_1_1WWidget.html#a7bffb7966160ff8a58fff9d31ef21078">rendered</a> when unsuspending.
This would cause problems with e.g. <a href="classWt_1_1WTextEdit.html">WTextEdit</a>
inside of a
<a href="classWt_1_1WTemplate.html">WTemplate</a>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11240" target="_blank">Issue #11240</a>:
fixed an issue where the lazy loading logic breaks when removing and inserting a large
number of rows in a <a href="classWt_1_1WTreeView.html">WTreeView</a>
(<a href="https://github.com/emweb/wt/pull/199" target="_blank">PR #199</a> by John Stark).
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11180" target="_blank">Issue #11180</a>:
fixes a regression in Wt 4.9.0 where
<a href="namespaceWt.html#af4b6ed5fd28b4f5fa141b153c1107349accf2281a355c2c9cd4698ac30bea7820">WidgetSet</a> mode
failed with a "classList is undefined" error.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11207" target="_blank">Issue #11207</a>:
fixes a regression in Wt 4.9.0 where
<a href="classWt_1_1WWidget.html#a5d403e0390841df77a23445b28044d5d">scroll visibility</a> didn't work anymore.
</li>
<li>
Fixed a couple of <a href="classWt_1_1WDialog.html">WDialog</a>-related regressions when using
<a href="classWt_1_1WBootstrap5Theme.html">WBootstrap5Theme</a>:
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11233" target="_blank">Issue #11233</a>:
hidden <a href="classWt_1_1WDialog.html">WDialog</a>s would remain visible.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11248" target="_blank">Issue #11248</a>:
contents of a dialog could be cut off when
<a href="classWt_1_1WWidget.html#afc4bfcc92fa39010cac8775f3332dfa5">setting the width</a>,
and
<a href="classWt_1_1WDialog.html#a0a3517bffbd049b988e80bb85ae18c46">resizing of dialogs</a>
didn't work.
</li>
</ul>
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11261" target="_blank">Issue #11261</a>:
added a missing <code>#include <algorithm></code> to <code>WModelIndex.C</code>
to fix compilation issues with Boost 1.81.0 and Visual Studio 2017.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/8223" target="_blank">Issue #8223</a>:
fixed compilation on 32-bit Raspberry Pi OS: Wt now links with <code>-latomic</code>
if necessary.
</li>
</ul>
<h2>Release 4.9.0 (December 22, 2022)</h2>
<p>
Wt 4.9.0 features a lot of changes under the hood: we have painstakingly removed jQuery from Wt,
modernized the JavaScript, and added a linter, formatter, and a new minifier in the process.
</p>
<p>
A more directly noticeable change is the fact that we gave the documentation a new lick of paint using the
Doxygen Awesome theme. Also, now that we added some tooling to customize WBootstrap5Theme, the
<a href="https://webtoolkit.eu/widgets" target="_blank">widget gallery</a>'s
primary color was updated to be more in line with Wt's website.
</p>
<h3>Backwards incompatible changes</h3>
<h4>Removal of jQuery</h4>
<p>
We removed every use of jQuery from Wt, and jQuery is now no longer automatically loaded.
This means that if you relied on the included jQuery version (for example, the <code>$</code> object or function),
you will have to make some changes to make it work with Wt 4.9.0. There are several options:
</p>
<ul>
<li>
<p>
Replace your uses of jQuery with vanilla JavaScript, which is what we did.
</p>
<p>
For example, the <code>$</code> function can often be replaced with
<a href="https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelector" target="_blank">querySelector</a> or
<a href="https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelectorAll" target="_blank">querySelectorAll</a>.
</p>
</li>
<li>
<p>
Load jQuery yourself using
<a href="classWt_1_1WApplication.html#ae88546224ed32cade783da188b145138">WApplication::require()</a>.
<a href="classWt_1_1WApplication.html#aa2add60804ff75b3798fc270050654c5">WApplication::requireJQuery()</a>
has been marked as deprecated.
</p>
<p>
For example:
<code>application->require("https://code.jquery.com/jquery-3.6.1.slim.min.js", "$");</code>.
</p>
</li>
<li>
<p>
Change your <code>wt_config.xml</code>, adding a <code><head-matter></code> section
that loads jQuery through a <code><script></code> tag:
</p>
<p>
<code>
<head-matter><br>
<script<br>
src="https://code.jquery.com/jquery-3.6.1.slim.min.js"<br>
integrity="sha256-w8CvhFs7iHNVUtnSP0YKEg00p9Ih13rlL9zGqvLdePA="<br>
crossorigin="anonymous"></script><br>
</head-matter>
</code>
</p>
</li>
</ul>
<h4>Changes to WBootstrap5Theme</h4>
<dl>
<dt>Collapsible panels</dt>
<dd>
<a href="classWt_1_1WBootstrap5Theme.html">WBootstrap5Theme</a>
has used an
<a href="https://getbootstrap.com/docs/5.2/components/accordion/" target="_blank">accordion</a>
instead of a
<a href="https://getbootstrap.com/docs/5.2/components/card/" target="_blank">card</a>
for collapsible panels since its introduction in Wt 4.6.0.
Now, <a href="classWt_1_1WPanel.html">WPanel</a> always uses a
<a href="https://getbootstrap.com/docs/5.2/components/card/" target="_blank">card</a>.
This allows all panels to have a consistent appearance, regardless of whether they can be collapsed or not.
Additionally, the
<a href="classWt_1_1WPanel.html#aefd66ff6dd8e2a1108e70efec4eab1b5">WPanel::collapse()</a> and
<a href="classWt_1_1WPanel.html#a2ac9a05172675559b6f988083a4fd666">WPanel::expand()</a> functions will now work
as expected with
<a href="classWt_1_1WBootstrap5Theme.html">WBootstrap5Theme</a>.
This change resolves <a href="https://redmine.webtoolkit.eu/issues/10364" target="_blank">issue #10364</a>.
</dd>
<dt>Bootstrap 5 theme customization</dt>
<dd>
We've made it easier to customize the Bootstrap 5 theme.
<a href="classWt_1_1WBootstrap5Theme.html">WBootstrap5Theme</a> now loads
a single CSS file that is built from
<a href="https://sass-lang.com/" target="_blank">Sass</a> source files. The
<a href="https://github.com/emweb/wt/tree/master/examples/custom-bs-theme" target="_blank">
custom-bs-theme example</a> shows how this allows the theme to be customized.
The
<a href="https://www.webtoolkit.eu/widgets" target="_blank">widget gallery</a>
makes use of this by changing the primary color from Bootstrap's blue to the purple
used in Wt's logo and homepage.
This change resolves <a href="https://redmine.webtoolkit.eu/issues/9350" target="_blank">issue #9350</a>.
</dd>
</dl>
<h3>New features</h3>
<ul>
<li>
Added <a href="classWt_1_1WProgressBar.html#abf8547894af5efc5e5789f9fa56bdc03">
WProgressBar::setValueStyleClass()</a>
(<a href="https://github.com/emweb/wt/pull/131" target="_blank">PR #131</a>
by maximiliank on GitHub).
</li>
<li>
Added <a href="namespaceWt_1_1Utils.html#a13d154e4ef34ee6f8c1a90e8aaeec0dc">Wt::Utils::htmlAttributeValue()</a>
to escape values if they are put into the value of an HTML tag.
</li>
</ul>
<h3>Other improvements</h3>
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/11067" target="_blank">Issue #11067</a>:
<a href="classWt_1_1WWidget.html#af01fbd9de70abd189c2f86171b6a1e02">animateShow()</a> and
<a href="classWt_1_1WWidget.html#a0c236e179d5b63c3c6e98cc69e28c9bf">animateHide()</a> were overhauled to use the
<a
href="https://developer.mozilla.org/en-US/docs/Web/API/Web_Animations_API"
target="_blank">Web Animations API</a>. This fixes issues with choppy animations.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/8629" target="_blank">Issue #8629</a>:
In order to ease maintenance, and make contributing to Wt easier, we changed the JavaScript
minifier from the old version of Google Closure compiler we were using to
<a href="https://terser.org/" target="_blank">terser</a>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/10966" target="_blank">Issue #10966</a>:
Added a JavaScript formatter to format Wt's JavaScript code.
Its usage is detailed in the Wt source tree at
<a
href="https://github.com/emweb/wt/blob/master/doc/development/javascript.md"
target="_blank"><code>doc/development/javascript.md</code></a>.
</li>
<li>
We gave our reference documentation a new lick of paint: we're now using the
<a href="https://jothepro.github.io/doxygen-awesome-css/" target="_blank">Doxygen Awesome</a> theme,
which also has a dark mode.
</li>
<li>
Whereas trying to construct
<a href="classWt_1_1WApplication_1_1UpdateLock.html">UpdateLock</a> with a null
<a href="classWt_1_1WApplication.html">WApplication</a> pointer would cause a null
pointer dereference before, it now simply yields an unsuccessful UpdateLock
(<a href="https://github.com/emweb/wt/pull/195" target="_blank">PR #195</a>
by Steven Köhler).
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/10395" target="_blank">Issue #10395</a>:
<a href="classWt_1_1WPanel.html#a9671893042605eb936c7301f6de09d3f">WPanel::setTitleBar(false)</a>
now automatically calls
<a href="classWt_1_1WPanel.html#ace945a192f671220a5a2cda671dc37ca">WPanel::setCollapsible(false)</a>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/9570" target="_blank">Issue #9570</a>:
All uses of <code>WT_CXX14</code> and <code>WT_CXX14ONLY</code> were removed in Wt's
source code. <code>WT_CXX14</code> is now always defined, since Wt requires
C++14. We marked <code>Wt::cpp14::make_unique</code> as deprecated, since this only
existed because C++11 lacked <code>std::make_unique</code>.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/10924" target="_blank">Issue #10924</a>:
The undocumented <code>split-script</code> configuration property was removed, simplifying
Wt's internals.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/10914" target="_blank">Issue #10914</a>:
Changed some Boost.Phoenix includes to silence deprecation warnings.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/10911" target="_blank">Issue #10911</a>:
Fixed OpenSSL 3.0 deprecation warnings.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/9252" target="_blank">Issue #9252</a>:
Fixed a deprecation warning in the Pango font support implementation.
</li>
</ul>
<h3>Bug fixes</h3>
<ul>
<li>
<a href="https://redmine.webtoolkit.eu/issues/9076" target="_blank">Issue #9076</a>:
<a href="classWt_1_1WDateEdit.html">WDateEdit</a>
gave a javascript error when opening the calendar popup if the
application was rendered in
<a href="namespaceWt.html#af4b6ed5fd28b4f5fa141b153c1107349accf2281a355c2c9cd4698ac30bea7820">WidgetSet</a>
mode.
</li>
<li>
<a href="https://redmine.webtoolkit.eu/issues/10488" target="_blank">Issue #10488</a>:
Long polling requests interrupted on the server side now no longer prevent keep alive requests from being sent,
and thus the session from timing out. This was possible when Wt is deployed behind a reverse proxy that has
a shorter request timeout than the <code><server-push-timeout></code>
configured in <code>wt_config.xml</code>.
</li>