bug#72573: 29.4; js-mode/JSX: forward-sexp behavior at end of string in JSX fragments

[Juri Linkov <juri@linkov.net>]

>> @@ -3929,7 +3929,8 @@ js-ts-mode
>>                     (sexp ,(js--regexp-opt-symbol js--treesit-sexp-nodes))
>>                     (sentence ,(js--regexp-opt-symbol js--treesit-sentence-nodes))
>>                     (text ,(js--regexp-opt-symbol '("comment"
>> -                                                   "template_string"))))))
>> +                                                   "template_string"
>> +                                                   "string_fragment"))))))
>> 
>> But since this bug report about the default non-ts behavior,
>> I have no idea why the default forward-sexp-function moves to
>> the beginning of the next string.  Maybe this was implemented
>> because the default ad-hoc syntax parsing is not reliable and might
>> mix up string beginnings and endings.  tree-sitter has no such problem.
>
> So what is our way forward with this?  Should we install the above
> patch, or should we close this bug ans wontfix?

I pushed the above patch with small changes to master.

Since the report was about non-ts modes, and it's not easy to change
the default behavior, probably this can be closed as wontfix.