167618 - Primary selection no longer works

Status: RESOLVED INVALID

(Core :: DOM: Selection, defect)

Description

[Trevin Beattie]

With the mozilla 1.1 release, I can't select any text from a web page by
dragging the mouse over it.  It doesn't get highlighted, and if another
application currently has the primary selection it stays there.

Selection worked in 1.1 beta.

If it helps, I compiled mozilla with the following configuration options:

configure  --with-system-jpeg --with-system-zlib --with-system-png
--with-system-mng --enable-default-toolkit=gtk --enable-xft --enable-crypto
--enable-extensions --disable-debug '--enable-optimize=-O2\ -march=k6'
--disable-logging --enable-strip

Comment 1

[Andrew Schultz]

Did you also compile your own build of 1.1b?  Can you reproduce this with a
.mozilla.org build?

==> Selection

Comment 2

[Trevin Beattie]

At 07:14 PM 9/9/2002 -0700, you wrote:
>Did you also compile your own build of 1.1b?

Yes, I built 1.1b from source.  I was trying to get better performance out
of it, and the extra optimizations seemed to help, but UI responsiveness is
still very sluggish (compared to Netscape 4.x).  The options may have been
a bit different -- I think I omitted "--enable-xft --enable-crypto
--enable-extensions", but I had to delete the tree after installing it due
to lack of space.

>Can you reproduce this with a .mozilla.org build?

Can I run mozilla from mozilla-i686-pc-linux-gnu-1.1-sea without installing
it?

When I tried, I got a strange box below the status bar, 1" tall, with two
lines of red text:

<broadcaster id="Communicator:WorkMode"
--^

However, selection does work in that build.  Pasting with button 3 also
seems to work consistently (bug #167617), as does keyboard focus in the URL
bar (bug #167021).  So it appears that all of the problems I've had with
the release (except for sluggishness) have something to do with the way I
compiled it.

Any suggestions as to which configure options I should try changing to
straighten things out?  I'm going to start by removing "--enable-xft",
since that had no apparent effect.

Comment 3

[Andrew Schultz]

what distro are you running (what gcc version are you using)?

--enable-default-toolkit=gtk and --enable-extensions are defaults AFAIK

the optimization you have is more than is standard (just do --enable-optimize to
get the default).  but many people do -O2 without problems.

--enable-crypto is good (no SSL without it) and shouldn't impact selection.

you might get some useful info if you don't --disable-debug, although it won't
be a particularly fast build.  you might take out the "-g" from
config/autoconf.mk (MOZ_DEBUG_FLAGS) after you run configure so the build isn't
huge.

the problem sounds so severe that this might not be a "selection", so what
version of gtk do you have (1.2.10 works for me)?

> Can I run mozilla from mozilla-i686-pc-linux-gnu-1.1-sea without installing
> it?

nope.

Comment 4

[Trevin Beattie]

Environment: RedHat Linux 7.1, kernel-2.4.9-34
Gnome 1.4.0 (built from source)
gtk+-1.2.10

Comment 5

[Trevin Beattie]

After many builds taking several hours each, I finally figured out the one
option that was causing both this bug and bugs #167021 and #167617:

	--enable-default-toolkit=xlib

I had started the first build using this option, but after getting a compile
error for using '--enable-xft' (another bug), I had reconfigured with
'--enable-toolkit-gtk' and continued the build.  The problem was that I hadn't
run 'make clean' first.  (That also indicates that the bug caused by
'--enable-default-toolkit=xlib' is somewhere in the modules compiled prior to
Xft.)

After wiping everything out and recompiling from scratch using
'--enable-toolkit-gtk', selecting works properly.

Comment 6

[Andrew Schultz]

excellent!
unfortunately this bug is INVALID (this is not a Mozilla bug)