-
Notifications
You must be signed in to change notification settings - Fork 290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hide instant redirection page from history #742
Comments
@reashetyrr what do you think? |
Can I work on this? |
Sure! |
@0xc60f i made the changes but i dont know how to check if its working or not. Theres no guide for setting up the project locally |
@ArslanYM, use the mv-3 branch, Reashetyrr did a webinar on developing for fastforward https://www.youtube.com/watch?v=cwaUa48YCXs&t=620s |
@NotAProton I am able to successfully build the extension but my question is how do i check if my changes are working or not. I dont know how to do that |
@ArslanYM The extension is built in the builds folder, load it into your browser and test it. You can find example links in PRs to the mv3 branch like #913. You can also directly open the before navigate page by using this link https://fastforward.team/bypassed?target=https%3A%2F%2Fexample.com/ with fastforward (MV-3) installed |
@NotAProton will this work to fix the current crowdbypass block issue for chrome or even firefox? basically instead of extension://ldcclmkclhomnpcnccgbgleikchbnecl/html/crowd-bypassed.htmlget= we use i seem to recall the old precursor to fastforward seems to use a similar method for crowdbypass i maybe recalling something wrong though |
This issue is stale because it has been open for 30 days with no activity. To undo this, make some activity on this issue or create a new one. |
Bump |
Does this still happens on MV3? |
This issue is stale because it has been open for 30 days with no activity. To undo this, make some activity on this issue or create a new one. |
It's going back to original page, but the redirection page history are still saved. |
It's really annoying to click on a bit.ly link or something, and then not have the back button work because the previous page is the redirection HTML and not the page you were on.
Thankfully, it should be really easy to fix. I think either adding this in before-navigate.js should do it:
window.location.replace(url);
or this:
history.deleteUrl()
The text was updated successfully, but these errors were encountered: