auto-tab-discard
auto-tab-discard copied to clipboard
rNeomy
Bookmarking a discarded tabs gives a wrong URL
Steps to reproduce:
- Open a tab
- Go to any page you prefer. i.e. github.com, then switch to another tab
- Wait until the tab gets discarded automatically or just force discard
- Open the tab again. navigate to a different URL. i.e. duckduckgo.com, then switch to another tab
- Wait for auto discard or just force discard the tab again.
- Now just rightclick->bookmark tab (without switching to the discarded tab). You'll see the bookmark having duckduckgo.com as a title but github.com as a URL ##
It's not only bookmarking: You'll see the same result if you have an addon that can show you a tab's URL without loading it.
Like this, you can never get the correct URL when you save/bookmark discarded tabs unless you reload them. I tried Dormancy and it exhibits the same behaviour, so this could be an issue with firefox' discard API but I leave this in the dev's hands for further testing.
cheers
Thanks for the report. This is a core API issue. I just submitted a bug report to Mozilla. Please follow https://bugzilla.mozilla.org/show_bug.cgi?id=1528895
Thanks for the report. This is a core API issue. I just submitted a bug report to Mozilla. Please follow https://bugzilla.mozilla.org/show_bug.cgi?id=1528895
Greased the wheels for you and confirmed that bug so the component triage owner is notified.
I can't be certain why a few weeks ago https://bugzilla.mozilla.org/show_bug.cgi?id=1528895#c1 I found 1528895 not reproducible. Maybe I should have run Firefox without extensions, or in safe mode, at the time. Moving on …
… yesterday, 1522184 and 1528895 became duplicates of:
– the cause of which is identified ☑
In addition to the people whose contributions to the various issues/bugs are visible: I'd like to publicly thank @gijsk – it was through his encouragement and direction behind the scenes that I found myself in Mozilla chat in good time.
An ordinary person might have glanced at an "extensions conflict" involving seven separate extensions and thought, "You're on your own there, mate!" :-) … instead, an extraordinary response from @rpl in Mozilla chat included the mozregression that got the ball rolling. @FilipePS is thanked for showing interest in extensions other than his own; https://github.com/FilipePS/Traduzir-paginas-web/issues/92#issuecomment-786097267 helped to expedite the diagnoses in bug 1694699. Last but not least: thanks for the work by @Rob--W including 🎉 relevant commits to the Mozilla code bases.
https://bugzilla.mozilla.org/show_bug.cgi?id=1498432#c11
https://hg.mozilla.org/mozilla-central/rev/c021c6541346
Status: ASSIGNED → RESOLVED Closed: 2 years ago → 3 days ago status-firefox88: --- → fixed Resolution: --- → FIXED Target Milestone: --- → 88 Branch
@alkumaish Firefox 88 was released a few days ago. Please confirm that Mozilla has fixed this issue.