[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: [Fwd: [Bug 73851] Web pop-up windows open in new tab when using
From:       Henrique Pinto <henrique.pinto () kdemail ! net>
Date:       2004-02-19 1:22:34
Message-ID: 40340FDA.3090203 () kdemail ! net
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

James Richard Tyrer wrote:
| And if the user doesn't want to pop-up to open in the tab?

Option 1) The user does not check "Open links in new tabs instead of new
windows" and uses MMB for opening links in tabs. I believe this is the
default setting.

Option 2) We add yet another option for opening links in new tabs when
they don't point to popups and in new windows when they do. Seems
overkill to me. (Please do not remove the current behaviour, I do like
opening popups in tabs, and I'm not being sarcastic.)

In case you think option two is the better, than I'm waiting your patch
for testing, even though I don't like the idea.

|> this should be granted regardless of what the site wants.
|
|
| It isn't a question of what the site wants.  It is a question of what the
| user wants.

I guess I missed the data you provided for proving that it is indeed
what the user wants. Can you point me to the results of your research on
the topic?

| But, the only issue I intended to bring here is the possibility of using
| the two different mouse buttons for the user to choose if they wanted
| what the site intended as user activated pop-up in a new tab (button 3)
| or in a pop-up, a new window, (button 1).  Do you wish to comment on that?

Special behaviour for popups? Isn't it better to use MMB for opening in
new tabs and LMB for opening in new windows, leaving the "Open links in
new tabs instead of new windows" option unchecked?

Changing the wording of the option to refer the new behaviour would at
least be consistent, but 1) you haven't given me a single argument as to
why the complicated behaviour you proposed is better than the current
one; 2) you seem not to have convinced anyone else, either; 3) I haven't
seem a patch for the behaviour change you proposed; 4) This seems to
specialized for me for being made configurable, I think it would be
better to choose one option and make it work like that.

| It seems just so unfortunate to me.  We could do at least a little
| eXtreme Programing and instead the developers seem to think that they
| should dictate what the users want.

(I don't think this comment was meant to me, but in case it was: I'm not
a KDE developer, just a guy with a CVS account that eventually
contributes small portions of code and/or translations for the Project.
And I don't want to dictate what the users want. But what does the
option they enabled means?)

What do KDE users want? I fail to see how do you qualify better to
answer that question than any KDE developer.

If you want the behaviour to be changed, than you should convince people
it should be changed. "Users want it" is not a valid reason if you can't
provide data for backing-up that statement. Give me valid reasons and
I'll take some time for examining them, but you should be warned that my
opinion means absolutely nothing, the ones you should convince are
elsewhere.

- --
	Henrique Pinto
	henrique.pinto@kdemail.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3-nr1 (Windows 2000)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFANA/Wx5ej30+ryYARAuSlAKCrIUAHR6rwC/KBiwUMHLM/argFhACfWpiD
VqiWpQdzm5i0R3ootmRrtQE=
=G+ew
-----END PGP SIGNATURE-----

_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]