HTTP 303 Redirects with anchor not respected

Steps to Reproduce:

• Redirect after a form submission (via HTTP 303) to a location that contains an anchor (e.g. Location: /path#anchor).

Observed Behavior:

• The redirection occurs, but strips the anchor from the resulting page (e.g. /path instead of /path#anchor)
• This results in any page rendering dependent upon this anchor to fail.

Expected Behavior

• Redirect and expose the full path with the anchor in the resulting page’s address bar.

Workaround

• Disable turbo on that particular form submission.

Wild Guess Hypothesis I suspect that the subsequent redirection fetch (from Turbo) strips the anchor tag from the underlying HTTP request (as expected), but when the page is re-hydrated, the address bar URL (pushstate) is not updated to reflect the original anchor.

[nickjj]

I’m seeing this behavior when performing any type of redirect after a successful form submission and the problem goes away if I disable Turbo. I’m also not using Rails so this is isolated to the JS library itself. I’m using beta 7 and I’m also not using frames or streams here. This is a basic full blown HTTP redirect.

Reproduceable steps:

1. import * as Turbo from "@hotwired/turbo";

2. Create a form where after the POST comes in, redirect to /#foo

3. The #foo will get stripped out from the redirect

4. Comment out the line from step 1 and do the same thing and now the anchor is kept in tact.

It’s worth pointing out params are kept in tact in either case. I’m only losing the anchor with Turbo.

[stebo]

I can confirm that this is an issue and I find it quite an unexpected behavior and would love to use my anchors. Adding a tailing /does not solve the issue for me when doing redirects in the controller:

redirect_to '.../posts/433545#comment_221760128', status: :see_other
# gets redirected to /posts/433545

redirect_to '.../posts/433545/#comment_221760128', status: :see_other
# gets redirected to /posts/433545/

In both cases the anchor is lost. Using 301, 302, 303 makes no difference. The only solution right now is to set data-turbo=falseon the form.

Any ideas how to fix this?