Closed Bug 59606 Opened 24 years ago Closed 24 years ago

bookmarks partially broken

Categories

(SeaMonkey :: Bookmarks & History, defect, P3)

Product:
SeaMonkey
Component:
Bookmarks & History
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: pat, Assigned: bugs)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.13 i686; en-US; m18) Gecko/20001108
BuildID:    2000110821 (Trunk)



Reproducible: Always
Steps to Reproduce:
1a. click on a bookmark inside a folder on the personal toolbar
- or-
1b. click on any bookmark using the bookmarks dropdown on the personal toolbar
(you have to activate that button in preferences first)

Actual Results:  nothing happens, console spits out:
JavaScript error:
chrome://navigator/content/navigator.js line 646: node has no properties

Expected Results:  bookmarked site opens.

Accessing the bookmarks via the bookmarks menu in the menubar works fine.

Nominating for RTM despite this workaround. This makes the personal toolbar
almost useless if you have more than a handfull of bookmarks
Worksforme. Reporter, what skin were you using? Can you reproduce it with
another skin? Clicking only once on a bookmark in the sidebar is not supposed to
do anything, but clicking twice is supposed to open the bookmark (and that's
what it does for me).
Fabian.
If you're going to nominate for RTM, you might as well put the rtm keyword in
the keywords field :-)

However, RTM is about regressions on the branch. As your comment states, you see
this on the trunk. Could you test the branch and see if it happens on there too,
and if so, add the rtm keyword to the keywords field?
Also, could you test the 2000-11-09-0x-Mtrunk when it comes out? I strongly
suspect this has already been fixed.
I apologize to the reporter, I was testing with yesterday's build.. yeah right.
I hereby promise I will never say a bug worksforme anymore while using
"yesterday's" build.
Fabian.
Fabian, are you saying that you do see this bug now with todays build?
CC:ing myself, I was going to report it.
This might indeed been fixed by <a href="mailto:alecf@netscape.com">alecf</a> ´s
checkin at 21:30 yesterday (which I saw after I reported the bug) . Will test
again with tonight´s build.
Jake : No, it worksforme with today's build (2000110804). I just hadn't
downloaded the latest build at the time I wrote my comment.
Fabian.
Looks like this has been fixed. Worksforme w/ build 2000110921. Please verify.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
FIXED is reserved for bugs in which a coder looked at the bug and checked in
code to fix the problem.  Being that no code was specifically checked in to fix
this it should be WORKSFORME...
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Completing status change to WORKSFORMW
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → WORKSFORME
mass-verifying WorksForMe bugs which haven't changed since 2001.12.31.

set your search string in mail to "EmperorLondoMollari" to filter out these
messages.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.