Promoting a Frame Navigation to a Page Visit is not working

1

Hey there, hoping you’re having a good day. So, i’m starting with a dummy project to test out the behaviour of frames.

I’ve followed the docs on how to replace urls with turbo frames.

here is my first page

<%= turbo_frame_tag "content", class: "w-full flex justify-center items-center" do %>
  <%= form_for @article, html: { class: "w-6/12" } do |f| %>
    <%= f.label :body %>
    <%= f.text_area :body, class: "resize-none w-full h-full" %>

    <button data-turbo-action="advance" type="submit" class="bg-indigo-500 px-4 py-2 text-white rounded-full">
      Confirm
    </button>
  <% end %>
<% end %>

And my second page layout

<%= turbo_frame_tag "content", class: "w-full flex justify-center items-center" do %>
  
  <%= form_for @article, html: { class: "w-6/12" } do |f| %>
    <%= f.label :title %>
    <%= f.text_field :title, class: "resize-none w-full h-full mb-4" %>

    <%= link_to "Back", new_article_path, data: { turbo_action: "advance"} %>
    <button type="submit" class="bg-indigo-500 px-4 py-2 text-white rounded-full">
      Set Title
    </button>
  <% end %>
<% end %>

Weird thing is, when pressing “Confirm” on the first page, the browser url is not updated.

Screenshot 2022-06-17 at 23.24.54
Screenshot 2022-06-17 at 23.24.542158×480 17.4 KB

When pressing confirm, the frames change successfully, but the url is not.

Screenshot 2022-06-17 at 23.25.12
Screenshot 2022-06-17 at 23.25.122144×582 19 KB

What makes this way more odd is that have a very similar setup with another project and everything is going fine.

Any idea why this might be happening?.

Thanks

2

Different library versions?

3

The first one(older project) uses webpacker. This new one uses importmaps, so it imports directly from cdns.

# Hotwire's SPA-like page accelerator [https://turbo.hotwired.dev]
gem "turbo-rails"

# Hotwire's modest JavaScript framework [https://stimulus.hotwired.dev]
gem "stimulus-rails"
4

What URL are you expecting? Stupid question - could it be that you’re not persisting the record in between the first and second step so you’re still working with a new record in which case /articles/new would seem appropriate?

5

Actually i am. The first url is articles/new. Then, it hits a controller that creates the record, and redirects to articles/:id/title