Open rvantonisse opened 5 years ago
FWIW I think I would prefer to just load the main page as without hash instead – that is what happens on ”normal”, not JS-enhanced web pages when a fragment is not found.
Do we still want to add a "Page not found" view to the generator page? Right now the behaviour is in line with what @yatil proposed: whenever an unfamiliar hash is used, it defaults to the "Create Statement" page. In my opinion this is desired behaviour and this issue can be closed.
It works partially. Here are directions to recreate the bug:
Is this easy to fix (recognize that "Preview your accessibility statement" button was not pressed)?
Another version of that bug:
This issue should now be fixed, pushed as part of PR #150
The issue only seemed to appear on chrome, not safari and also affected the "Skip to Content" button at the top of the page. The generator now defaults to the main "create" page whenever the hash is changed to something unfamiliar.
When using hashed urls without "create" or "preview" in it, the generator looks like it is not functioning (blank page).
Redirect all other hashed urls to a "Page not found" view