[Bug 248861] [maintainer-update] www/wt update to v3.7.0

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248861

            Bug ID: 248861
           Summary: [maintainer-update] www/wt update to v3.7.0
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: info at babaei.net

Created attachment 217468
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=217468&action=edit
www/wt v3.6.1 to v3.7.0 patch file

Release 3.7.0 (August 3, 2020)

Wt 3.7.0 adds support for multiple X axes to the charts, among other fixes and
tweaks.
Security related

Wt now rejects GET requests for Ajax-enabled sessions that are not for
resources, as an extra means to prevent session hijacking attempts. Patch
provided by Bruce Toll in issue #7585.
Multiple X axes

WCartesianChart: similar to how Wt 3.3.11 added support for multiple Y axes, Wt
3.7.0 adds support for multiple X axes, too. Instead of trying to squeeze
another int argument into functions like WCartesianChart::map, we decided to
add overloads that take two WAxis references.
Minor features

    WFileResource: added a log message when failing to open a file. Previously,
it would not be very clear why nothing was downloaded.
    Added the MIME type for .txt files to wthttp, so that they are displayed in
the browser rather than prompt a download.

Bug fixes

    Wt:: Auth:
        Issue #7518: previously, it was not possible to set
AbstractStrengthValidator to non-mandatory. This has now been fixed. It now
also correctly reports InvalidEmpty when the input is left empty.
        Fixed an issue where slots connected to Login::changed() would still
have the old session id, which would afterwards be updated, causing resource
urls created in the slot to have the wrong session id.
    WPaintedWidget: fixed an issue where combining incremental painting
(PaintUpdate) with images could cause the first paint event to be discarded,
resulting in an incomplete result.
    Previously, having multiple instances of WGoogleMap could cause JavaScript
errors. This has now been resolved.

-- 
You are receiving this mail because:
You are the assignee for the bug.