Sergey Arkhipov

Is there any progress on this issue ? drag_to does not work with SortableJS. ``` cuprite (0.14.3) ferrum (0.13) ``` Direct use of Ferrum methods doesn't work either ``` def...

Hi, @swanson ! Thanks for replying . Maybe we are talking about different versions of gem, but in the current one (cuprite (0.14.3)) you cannot set arguments for the drag_to...

> As described in #182 -- you will need to use `forceFallback: true` option in SortableJS and also pass in an option for `steps` in drag_to (I used 10). Hi,...

@ioquatix As I mentioned above, this is the standard format for generating forms in Rails, and it works fine with rack version 2.2.8. The result should be exactly as shown...

Hi, @matthewd I won't insist, but it is quite logical to use this format for some fields. It is especially useful for various JSON fields, when the value for each...

Inside view ```html ```

> This is a bug in the application that needs to be fixed, not a bug in Rack. That it worked in older versions of Rack is accidental. @jeremyevans, I...

@matthewd , Thank you for the detailed explanations of the difference in the objectives of the methods. In version 2.2.8, the field named ""article_version[body[answer1]]"=>"" returned by parse_query was successfully and...

@jeremyevans Another way leads to increased complexity of forms, when there is a layout of nested elements of standard arrays and hash into simple names, which leads to an additional...

@jeremyevans As I said, we are using rails 7.0.8, which in turn uses rack 2.2.8, and everything is working fine. With the release of the new Rails 7.1.1, a scheduled...