Update js_of_ocaml upper bounds in preparation to release 6.0.0

[vouillon]

No description provided.

[mseri]

Thanks

[mseri]

Would it be possible to paste here the errors in some representative cases?

[vouillon]

JavaScript numbers are not longer mapped to OCaml floats but are given type Js.number Js.t. This causes most of the errors.

A few JavaScript properties (and method parameters) were wrongly given type int. This has been fixed by ocsigen/js_of_ocaml#1747. This incompatible changes breaks the latest release of eliom and eliom-toolkit.

incr_dom.v0.15.1:

# File "src/js_misc.ml", line 40, characters 15-25:
# 40 |   Float.( >= ) rect##.top 0.
#                     ^^^^^^^^^^
# Error: This expression has type
#          Js_of_ocaml__.Js.number_t = Js_of_ocaml__.Js.number Js_of_ocaml.Js.t
#        but an expression was expected of type Core.Float.t = float

eliom.11.1.0:

File "src/lib/client/eliommod_dom.ml", line 697, characters 15-62:
697 |   { html_top = Dom_html.document##.documentElement##.scrollTop
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error: This expression has type Js_of_ocaml__.Js.number_t = Js.number Js.t
       but an expression was expected of type int

ocsigen-toolkit.4.1.0:

File "src/widgets/ot_picture_uploader.eliom", line 329, characters 38-50:
329 |               (fun ev -> float_of_int ev##.clientX)
                                            ^^^^^^^^^^^^
Error: This expression has type
         Js_of_ocaml__.Js.number_t = Js_of_ocaml__.Js.number Js_of_ocaml.Js.t
       but an expression was expected of type int

[mseri]

Thanks a lot