Either there are some errors or you're not describing the full picture.

“Fragment” is just the part after the # in the URL. It’s designed to let web pages have a table of contents at the top of the page, with links to sections farther down the page.

The part before the # is the web address of the page itself, and the fragment after the # is the name of an anchor tag within the page. So if the fragment is the only thing that changes, the browser stays on the same page and (in the old days) just scrolls to the section indicated by the fragment.

Modern web apps hijack that functionality so they can use the fragment as the marker for different web app screens. It works really well, and you can even bookmark specific screens within your web app.

ok, thanks for that

In the context of the reitit router, I don’t think I need to worry about it

Yeah, looks like you’ve got that all up and running correctly.

ok, here…

Before clicking, here’s the URL:

Do you use :button inside of a :form?

good question, but no.

Just input fields in a div.

here’s the url before:

and after:

OK, so the URL is the same. Then where does the white page come from? What renders it?

I’m using a base setup from luminus template, which sets up re-frame and reitet front-end router

Ah, my hate for templates is tingling. :)

It doesn't matter what you use - check what is rendered.

ok another clue

The page is blank

However, a force refresh brings it back up again

It seems like you have something akin to

(when condition
   [main-app-component])

let me see..

If the URL is not changing, then it means it's purely within your app's state and has nothing to do with requests. E.g. try to manually dispatch the event that fires when the request is successful - it should lead to the blank page just as well.

ok

BTW that "check what is rendered" is still meaningful even if you see a blank page. There might still be DOM elements (visible via regular DevTools) or React elements (visible via React DevTool extension).

I really dislike Chrome, but I’ll start it up and try the react devtools

So.. after rendering, the react tools say I have the re_frisk element on the page and nothing else.

Check your components, from the root down the path that is supposed to be rendered with that URL. Somewhere there should be a condition that's false.

Also, check if you have any JS console filters in the browser - maybe there are errors but you have accidentally filtered them all out.

Got it!

It’s been a while, but I forgot the reg-event-db handlers need to return the updated db, and I had a console log statement as the last line in the function.

Thanks for your help!

Ha! Yep, that happens. :) HPH

I’ve had buggy reg-event-db handlers that failed to update app-db correctly and screwed up the display.

You need a (.preventDefault evt) on your form submit-handler

For example, if it returns nil instead of returning an updated db

Oh, if you have form elements on your page, yeah, that could be doing it to.

With :http-xhrio you don’t need to use forms, you can just use inputs and buttons directly.

But it seems that he’s not returning db from the event actually it might be either

Or like Lu said, add .preventDefault to the form submit handler.

When you refresh the page, the app-db is created anew. It's a clean slate, that's it. Whatever you set to run when that particular page is loaded, will run, and the value of app-db will be created from that.

I can't really suggest any reading other than the excellent re-frame documentation.

Ok I'll read the documentation.. thks