97419 - right mouse button doesn't work

Status: VERIFIED WORKSFORME

(SeaMonkey :: UI Design, defect)

Description

[Rainer Mager]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3+) Gecko/20010814
BuildID:    20010829

Pressing the right mouse button doesn't bring up a context sensitive menu or do
anything visible. This is true for right-clicking on normal HTML pages and
images. I haven't tried anything further.

Reproducible: Always
Steps to Reproduce:
1. right click
2. despair


Actual Results:  nothing

Expected Results:  display of menu

Comment 1

[R.K.Aa.]

The build ID you report is from "tomorrow", 29th, yet bug is filed on the 28th.
How come? 

Comment 2

[R.K.Aa.]

Ahh never mind:i read the next bug about CVS build.

Comment 3

[Rainer Mager]

Besides, I'm in Japan. My 29th starts long before your's does. ;-)

Comment 4

[R.K.Aa.]

It's a good idea to give official build ID's *or* the time you pulled in EST
("Mozilla") time. You see that time quickly by browsing checkins in bonsai as
you start the pull.

I'm unable to reproduce this bug on Linux with a current CVS (6 hours old) - in
other words newer than yours. Also: The build ID i see when i do help/about
mozilla is 20010818, so the official user string is update compared to your 
build. This was also the case also yesterday when i compared to the string in
this bug.  I wonder if your pull has failed somehow. Did you try a clobber? Both
this and bug 97419 are well known bugs from a couple of weeks ago and both are
fixed. I'd try a new pull and clobber if I were you.

Works for me.

Comment 5

[Rainer Mager]

Probably silly questions but...

What is bonzai. And how do I do a clobber?

I always build with a 'make -f client.mk' as is described on the Linux build 
page. Is there a better way?

Comment 6

[Rainer Mager]

Ok. I did a complete rebuild (clobber_all then make again). And this now works now.

My new question is, should I always do a clobber? When is it ok not to?

Comment 7

[sairuh (rarely reading bugmail)]

rainer, i'm not sure what the best answer is wrt when to clobber... rkaa/pchen?

but, with respect to this particular issue, i'm gonna mark as wfm since a
workaround was found.

Comment 8

[R.K.Aa.]

Under ideal circumstances a build should always be clean, so NOT clobbering is
for the lazy of us who wants to save some time.

Luckily, over 95% of the time there's no need to build clean. The past weeks
took a clobber or two though, but that's a bad record.

Before despairing and a "make clobber", it's worth testing whether it's just a
new dependency issue: Removing all in and under the dist dir might work. Saves
lots of time.

If something goes astray, I usually try to find out whether a clobber might be
required by paying attention in the newsgroups or on irc, and browse bonsai and
bugzilla bug-comments concerning recent checkins etc. Bugzilla is invaluable.

Unless I really smell a rat, I also compare to "the next" official build before
filing a bug. If the bug is in an official build too, file it if it isn't filed
already.

If the bug is not in the official build: time to think, read and possibly
clobber before filing, unless you have a fairly strong hunch what's causing it.
These are my own "rules of the thumb" anway - FWIW.

Comment 9

[sairuh (rarely reading bugmail)]

mass verification of WorksForMe bugs: to find all bugspam pertaining to this,
set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM".

if you think this particular bug is *still* an open issue, please make sure of
the following before reopening:

a. that it's still a problem with ***recent trunk builds*** on the all
appropriate platform[s]

b. provide clear steps to reproduce (unless a good test case is already in the
bug report), making sure it pertains to the original problem (avoid morphing as
much as possible :)

Comment 10

[Steve Fink [:sfink] [:s:]]

Attachment: gcc hazard bug workaround: avoid std::declval (see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97419 )