[BUG] Cannot add synonymous keywords for a parameterized URL
A workaround for this problem is listed here but it's a bug that should be fixed:
Is there a reason why you can't set multiple keywords for one same search url? https://support.mozilla.org/en-US/questions/1174931 - Sorry the forum software wouldn't allow me to reply directly to that issue ("There was an error generating the preview.")
This is a poor workaround for users. Please treat this as a bug and work to fix it.
When the user makes duplicate bookmarks with different keywords there is no indication that changing the keyword of one bookmark will change the keyword of all the other bookmarks with the same URL, leading to obvious frustration and confusion. (e.g. "Why did my other bookmark keyword that I didn't change at all suddenly stop working?")
Please properly support multiple keywords for the same URL.
The user should be able to:
a) have a comma-separated list of synonymous keywords for a single bookmark
and
b) have multiple bookmarks, each with the same URL but with different keywords
All Replies (11)
A keyword is connected to an URL in current releases and not to a specific bookmark, so you need to make sure that the URL differs.
Why would you want to use different keywords for the same URL?
Maybe try to come up with a more descriptive keyword.
If you create multiple copies of the same bookmark (link) then you will notice that they all get the same keyword although their titles can differ.
> Why would you want to use different keywords for the same URL?
For example, if you have a longer keyword for a site e.g. "wiki" for wikipedia and then you find you use it a lot so you create a shorter version ("w") but you still want the old one to work too. There's really no reason it shouldn't except that Firefox is buggy.
Yes, I realize you can work around this bug, but i'll bet that 95% of users won't even realize that their old bookmark keyword was changed. In other words, it is poor UX should be fixed.
Please treat this as a bug. It is a bug. It is poor UX that can be fixed. Please treat it as a bug.
You can leave feedback and comments via "Help -> Submit Feedback"
Firefox's internal Help button opens a tab here:
https://support.mozilla.org/1/firefox/56.0.1/WINNT/en-US/firefox-help
Which automatically redirects to:
https://support.mozilla.org/en-US/products/firefox?as=u&utm_source=inproduct
Which takes me back to here where I posted this. "Submit Feedback" does not appear on any of these pages.
Can you be more specific about which "Help" you're talking about?
pengo மூலமாக திருத்தப்பட்டது
On Windows 7, when I click "Submit Feedback" I get redirected here: https://qsurvey.mozilla.com/s3/FirefoxInput/
What you seem to be doing is to click item in the Help menu named "Firefox Help". Further down in the help menu list below "Troubleshooting Information" you will find "Submit Feedback".
- you can tap the Alt key or press the F10 key to show the hidden Menu Bar with the Help temporarily.
You can also click the '?' in the "3-bar" Firefox menu button drop-down list.
Firefox uses this URL internally:
- app.feedback.baseURL
https://input.mozilla.org/%LOCALE%/feedback/%APP%/%VERSION%/
This translates to:
And redirects to the above posted URL on the qsurvey.mozilla.com website.
"WONT FIX"
https://bugzilla.mozilla.org/show_bug.cgi?id=453789
WTF IS WRONG WITH YOU PEOPLE REFUSING TO FIX YOUR BUGS SERIOUSLY
pengo said
"WONT FIX" https://bugzilla.mozilla.org/show_bug.cgi?id=453789 WTF IS WRONG WITH YOU PEOPLE REFUSING TO FIX YOUR BUGS SERIOUSLY
You did see this, right:
I don't think this feature would be useful to enough Firefox users to consider including it in the product by default.
With only two replies in 9 years, I think he was right.
Mozilla has limited resources and there are THOUSANDS of open bugs that need fixing for DAILY USE CASES that annoy dozens of people. Seriously.
jscher2000,
You're asking me to explain to you why fixing bugs that silently break features, and not calling them "feature requests" is important. Who are you trying to help?
WHERE DOES THIS FROWNY FACE ICON GO? THAT IS NOT A BUG TRACKER. IT'S A GARBAGE DUMP TO IGNORE USERS. FFS DO YOU KNOW HOW FRUSTRATING IT IS TO FINALLY FIND THE CAUSE OF YOUR BROWSER MALFUNCTIONING AND TO BE TOLD IT'S BECAUSE YOU NEED TO IMPLEMENT YOUR OWN FUCKING BROWSER EXTENSION FOR IT NOT TO FAIL SILENTLY. WTF. IT'S NOT A FUCKING FEATURE REQUEST YOUR SOFTWARE IS BROKEN.
This bug has been known about for nine years. Don't give me some bullshit about prioritizing.
It's hard enough to find the actual Firefox bug tracker. Don't talk to me about how many people have experienced the bug. Most users who experience it will just experience the browser acting weird and have no idea why. You're not helping anyone here.
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
I can see you're frustrated, but you already know the support forum cannot solve this problem.
pengo said
You're asking me to explain to you why fixing bugs that silently break features, and not calling them "feature requests" is important.
...
Do I really have to write out fifty fucking use cases to explain ways that ordinary users are affected by having a field in their bookmarks silently deleted?
Well, when I compare the bug you linked to with what you are repeating over and over and over, I do see something different. Unlike the previous bugs, you're saying there is a problem of data loss that justifies a new feature, rather than merely wishing for something. Why not file a new bug titled something like:
Add Keyword for Search breaks/deletes existing keyword for the same URL without notice
and see whether that makes anyone view it more sympathetically. Suggestions: Do not mention the old bugs, or rail on the developers you want to help you.
And if you want to find other users who will "vote" for your bug to get fixed, try a social approach:
They refuse to fix it. I'm just a user. I'm not starting a twitter campaign to convince firefox developers to fix the bugs of software that is clearly broken and they are aware is broken.
I'm just not using firefox any more. Goodbye and thanks for your attempted help.
Good bye.