sergiotarxz

@Viglino It is not called but the filter affects anyway highly to the performance every time it is rotated the map using: ``` this.map.getView().setRotation((this.compassHeading(alpha, beta, gamma) - this.rotationOffset)) ``` Anyway...

Can I take this issue? And if so should I copy what mojo.js does? Am I supposed to create the missing unit tests? And if I should create the unit...

      Right new Left Old.

Also this pull requests fixes a bug where `tap for more` was not changing to `tap for less` on click.

There is a screenshot I have not posted 

I added use strict to the javascript and discovered a bunch of errors.

I just discovered there was a code path I was not testing, I tested it and fixed the following: * Added popper.js. (Required by tooltip) * Ensured tooltips actually work....

@kraih Would you be in favor of moving the embedded javascript in the template to a file? Maybe in another pr.

The result for `json_message_has` in the negative case is: ``` is_deeply \@args, ['ok', undef, 'has value for JSON Pointer "/test0"']; ``` Which appears sightly inconsistent with other negative cases being...

I think it is not my fault these two test fail: ``` @github-actions linux / perl (5.22) (pull_request) Failing after 2m Required [Details](https://github.com/mojolicious/mojo/actions/runs/7862274388/job/21451556660?pr=2153) @github-actions linux / perl (5.30) (pull_request) Failing...