Closed Bug 223174 Opened 21 years ago Closed 15 years ago

text-box and non-navigational clicks cause pop-ups

Categories

(SeaMonkey :: UI Design, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: chris.pickett, Assigned: jag+mozilla)

References

(Blocks 1 open bug, )

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007

please try the "non-navigational click test" and the "element events test" at
this url.  i get popups in both cases.  according to the page author, there
should be no popups in these situations.

Reproducible: Always

Steps to Reproduce:
onMouseOver is a dupe of bug 152167, I couldn't find any dupes for clicking on
non-navigational elements...

(Assuming no dupes for it are found) should this bug be changed to be only for
clicking on non-navigational elements, or should it be marked invalid?
Okay, I'm sorry, I should have made two bugs (or rather I should have found the
mouseover one).

If you want, I'll resubmit it, but let's just change the summary and forget the
mouseover bit.
Summary: mouseover and text-box clicks cause pop-ups → text-box and non-navigational clicks cause pop-ups
-> XP Apps

Confirming, I couldn't find a dupe either after some fairly thorough searches. I
did come across bug 212163 (wontfix), but it's specific to Firebird rather than
Mozilla. I guess it's up for debate whether this is an intentional loophole
since there are valid uses for this feature.
Assignee: general → jag
Status: UNCONFIRMED → NEW
Component: Browser-General → XP Apps
Ever confirmed: true
QA Contact: general → pawyskoczka
I think it depends on what you click on.  The item in question in the Firebird
bug 212163 is a button.  But should you get a pop-up from clicking on a text box?

In bug 152167, somebody mentioned having a whitelist (bug 159036) of acceptable
pop-up creating actions, maybe that's the way to go (because there will always
be elements not caught by a blacklist, you'll go on fixing bugs like this forever).

I would feel best if this bug was marked dependent on bug 159036, but left open
until the issues at the URL I gave go away.
I suggest wontfix.  Sites can make links look like textboxes and textboxes look
like links, so distinguishing between "navigational clicks" and
"non-navigational clicks" won't gain you anything.  Furthermore, I think I've
seen sites use <div> onclicks to open new windows legitimately (because the site
author didn't know about "sidebar a {display:block}").
"text-box and non-navigational clicks cause pop-ups"

Just for the record, not when you install MultiZilla...
Blocks: popups
Product: Core → Mozilla Application Suite
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.