Desktop shortcuts all lead to the same page as first shortcut with that title tag, on Windows 10
Categories
(Core :: Widget: Win32, defect)
Tracking
()
People
(Reporter: omgitsraven, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0
Steps to reproduce:
- Visit this page: https://ravenworks.ca/temp/shortcutbug/page1.htm
- Drag the lock icon in the URL bar onto your desktop (or a Windows Explorer window)
- Rename the resulting shortcut to "one"
- Visit this page: https://ravenworks.ca/temp/shortcutbug/page2.htm
- Drag the lock icon in the URL bar onto your desktop (or a Windows Explorer window)
- Rename the resulting shortcut to "two"
- Visit this page: https://ravenworks.ca/temp/shortcutbug/page3.htm
- Drag the lock icon in the URL bar onto your desktop (or a Windows Explorer window)
- Rename the resulting shortcut to "three"
- Double-click the shortcut labeled "one", and observe the URL that opens in Firefox.
- Double-click the shortcut labeled "two", and observe the URL that opens in Firefox.
- Double-click the shortcut labeled "three", and observe the URL that opens in Firefox.
Actual results:
The URLs that will open, respectively, will be:
- https://ravenworks.ca/temp/shortcutbug/page1.htm
- https://ravenworks.ca/temp/shortcutbug/page1.htm
- https://ravenworks.ca/temp/shortcutbug/page3.htm
Expected results:
The URLs that should open, respectively, would be:
- https://ravenworks.ca/temp/shortcutbug/page1.htm
- https://ravenworks.ca/temp/shortcutbug/page2.htm
- https://ravenworks.ca/temp/shortcutbug/page3.htm
To say it less verbosely: if you make a URL shortcut on your desktop, and then you go to a totally different page that happens to have the same title tag, and make a new shortcut in the same folder (after renaming the original shortcut first since otherwise it would be impossible), the second will share the same URL as the first.
This is definitely on creation rather than on opening -- you can right-click the shortcuts and go to 'properties', and see that the saved URLs match. And it really seems to be title tag, and not domain or page filename that causes this conflation -- the examples above all have different page filenames but the first and second will have the bug; and they're all on the same domain, but the third will NOT have the bug!
Comment 1•4 years ago
|
||
I can't seem to reproduce your issue on Windows 10 with Firefox Release v81.0, v81.0.2, v82.0 or Nightly v84.0a1.
Can you retry to reproduce while using the browser in safe mode?
(https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems)
Which version did you use to reproduce the issue? v81.0.2?
Reporter | ||
Comment 2•4 years ago
|
||
Bizarre; I just tested again and now it's not happening for me either! (Not in safe mode, or after re-enabling add-ons!)
I was on some version of 81 at the time, though I don't remember which; I've updated to 82.0.2 since then. So this means one of two things:
- either the update to 82 fixed it (which would be a wild coincidence, since this bug has been bothering me for years, on multiple machines; I just only finally got around to reporting it)
- or, there's some other circumstance that triggers the bug (It was happening for me consistently when I filed the report, but maybe it only starts happening after something else has happened first, and rebooting clears it again until the circumstance has occurred again?)
I guess at this point I'll just keep an eye out; if the bug ever happens to me again in 82 or above, I'll chime in again and we'll know that there's some other precondition; if not then maybe 82 happened to have the fix??
Comment 3•4 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Reporter | ||
Comment 4•4 years ago
|
||
Hey, I'm not sure how to close this, but: it definitely hasn't happened for me since updating to 82. That's so wild, that there happened to be an update with a fix IMMEDIATELY after I finally got around to reporting the bug... (I swear it was happening in 81! I tested carefully! :P)
Anyway, if I ever run into it again I'll come back and ask to re-open it, but in the meantime it's probably safe to close this. Thanks!
Comment 5•4 years ago
|
||
The severity field is not set for this bug.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Reporter | ||
Comment 6•3 years ago
|
||
It's been a while, but I wanted to check in: this finally happened to me again. And I have two new pieces of information:
- Restarting Firefox did NOT fix it
- Restarting Windows DID fix it
So it's quite possible this is a Windows bug?
Just wanted to leave this information here in case anyone else starts running into this and finds this thread... I'd still love to get this addressed somehow, though I understand if it's outside of what Firefox can fix
Description
•