As discussed in #120, this PR adds JavaScript to override the default, hardcoded back button URL for every page of the UI.
If JavaScript is disabled in the browser, the underlying back button functionality continues to work in its usual slightly-quirky fashion :)
I wanted to encapsulate the JS in a separate file (/static/back.js) but I ran into a strange issue where the HTML beyond the <script src="/static/back.js"></script> tag would not render (even though it was present in the source). Since the JS is simple and brief, I went with the fallback option of rendering it in a <script> tag with Maud.
As discussed in https://git.coopcloud.tech/PeachCloud/peach-workspace/pulls/120, this PR adds JavaScript to override the default, hardcoded back button URL for every page of the UI.
If JavaScript is disabled in the browser, the underlying back button functionality continues to work in its usual slightly-quirky fashion :)
I wanted to encapsulate the JS in a separate file (`/static/back.js`) but I ran into a strange issue where the HTML beyond the `<script src="/static/back.js"></script>` tag would not render (even though it was present in the source). Since the JS is simple and brief, I went with the fallback option of rendering it in a `<script>` tag with Maud.
hmm strange about the html bug. something about html syntax?
would also prefer separate js files to js within script tags in general, but also doesn't matter much since its a small amount of code
hmm strange about the html bug. something about html syntax?
would also prefer separate js files to js within script tags in general, but also doesn't matter much since its a small amount of code
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
notplants
As discussed in #120, this PR adds JavaScript to override the default, hardcoded back button URL for every page of the UI.
If JavaScript is disabled in the browser, the underlying back button functionality continues to work in its usual slightly-quirky fashion :)
I wanted to encapsulate the JS in a separate file (
/static/back.js) but I ran into a strange issue where the HTML beyond the<script src="/static/back.js"></script>tag would not render (even though it was present in the source). Since the JS is simple and brief, I went with the fallback option of rendering it in a<script>tag with Maud.hmm strange about the html bug. something about html syntax?
would also prefer separate js files to js within script tags in general, but also doesn't matter much since its a small amount of code
I tried tinkering with it for an hour and couldn't figure it out. Very weird.