Correct behavior: go to manage bookmarks, choose a bookmark, edit its properties, and fill in a word in the "custom keyword" field. Now when you type that word into the URL bar and press enter, it should take you directly to that bookmarked web page. As described in bug 18719, correct behavior for internet keywords is to first check the bookmark custom keyword list and if not there, then go to the keyword server. Right now, it just goes to the keyword server. Assigning to Judson Valeski since this may be in the web shell and cc'ing RJC since he is the guy who implemented custom keywords.
changing component to "Bookmarks" and QA to Claudius.
Component: Browser-General → Bookmarks
QA Contact: asadotzler → claudius
Hmmm... this works for me in a build on Win98 from the early morning of 2/23/2000.
I think this no longer has anything to do with valeski Current behavior: I have no idea why this is so but maybe the error code will mean a lot to you. Currently on all platforms, if you modify the custom keyword property of an existing bug and then try that keyword, all works fine. However, if you create a new bookmark, give it a title, url, and keyword, when ou try that custom keyword you get the following error: Alert: NC is not a registered protocol Because the browser url field looks like it just tried to load NC:BookmarksRoot#$12abcdef where 12abcdef is a hexadecimal number all platforms, 2000022408 builds
Summary: Custom keywords in Bookmarks not working → Custom keywords for new Bookmarks not working
Do we care about this for beta?
Target Milestone: M14
is this still a problem johng?
yes, this still happens with 2000022808 builds
OS: Windows 95 → All
Hardware: PC → All
Putting on PDT- radar for beta1.
Assignee: valeski → rjc
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
I'm marking this bug FIXED.
this is fixed only because you can no longer specify a keyword upon new bookmark creation. VERIFIED with the 2000033009 builds
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.