You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As ignition.js is compiled and contains lots of stuff, I could not figure out what is the purpose of the URI fragment, which is being appended when Ignition takes over rendering of the exception page. Is it required for Ignition to function properly or could it be removed?
It causes some small inconveniences when Ignition rewrites an already existing URI fragment and instead of a simple refresh, even a back won't work (it looks like that previous URI is not pushed to the browser's history).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi!
As ignition.js is compiled and contains lots of stuff, I could not figure out what is the purpose of the URI fragment, which is being appended when Ignition takes over rendering of the exception page. Is it required for Ignition to function properly or could it be removed?
It causes some small inconveniences when Ignition rewrites an already existing URI fragment and instead of a simple refresh, even a back won't work (it looks like that previous URI is not pushed to the browser's history).
Beta Was this translation helpful? Give feedback.
All reactions