Closed Bug 264129 Opened 20 years ago Closed 20 years ago

Plugins embedded in html behave like regular images on click and keys (can't type in Flash)

Categories

(Core Graveyard :: Plug-ins, defect)

PowerPC
macOS
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: steveab, Unassigned)

References

()

Details

(Keywords: helpwanted, regression)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041012 Camino/0.8+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041012 Camino/0.8+ It appears that even when the focus is on the Flash movie, (ie, you've clicked on something in the Flash movie, to which Flash has responded), Camino is intercepting keypresses that the user is expecting to manipulate the Flash movie with. Reproducible: Always Steps to Reproduce: 1. In the example, let it all load, and choose an avatar. 2. Use your cursor (arrow) keys to start walking around the room. Actual Results: Pressing the DOWN arrow key will scroll the whole browser window down, too. Expected Results: Pressing the DOWN arrow key should just effect the Flash movie.
Conformed using Camino 2004101508 on 10.3.5. If you make the window narrow enough, it will scroll left and right as well. Hitting space, which usually pages down, does not make it page down (as it should be). Looks like the bug is specific to arrow keys.
Confrimed using FF 20-10-2004 and Camino 20-10-2004 Nightly Trunk Builds. This works fine in the FF 1.0PR version.
Severity: normal → blocker
Keywords: smoketest
Product: Camino → Browser
Version: unspecified → Trunk
This appears to be platform-specific. It works fine on win32 builds.
What's the regression window for this?
Severity: blocker → normal
Keywords: smoketest
Blocks: 265461
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.8a5?
*** Bug 265461 has been marked as a duplicate of this bug. ***
*** Bug 270113 has been marked as a duplicate of this bug. ***
I'm changing the severity and the summarary to make sure this bug refelects the true nasty nature of this bug. This bug causes all websites that contain flash to be non functional becuase on click causes the page to scroll (try this webpage http://www.alv3n.com/esc/), using keys in flash or java games doesn't work as they should etc. etc. This should be a blocker for what ever new version will be based on the current trunk.
Severity: normal → major
Summary: Using the cursor keys to navigate a Flash movie also causes the browser window to scroll up or down. → Plugins embedded in html behave like regular images on click and keys.
Given that very few people can reproduce this (by dint of most of us not having Mac hardware about), it's really hard to get anywhere on this until someone who can actually reproduce it narrows down the regression window (as requested 3 weeks ago in comment 4).
Since nobody seems to care I will try to track down a regression date tonight.
If I didn't care, I wouldn't be commenting.
Oeps, I didn't ment it that way, I ment tracing the date. So far July looks like the bad month. More info comming.
(In reply to comment #11) > Oeps, I didn't ment it that way, I ment tracing the date. So far July looks like > the bad month. More info comming. Hmm.. I tried a build from august in which the issue I reported in bug 270113 behaved properly. However, the arrow key issue was still present and clicking on a flash object still gave it an annoying dotted border.
OK the appearance of the dotted border around flash objects in html pages appeared between 23 and 27 july trunk builds. Later on, not sure when, clicking on the flash object caused the browser to always scroll to the top of the object.
Yeah, I'm still looking for that. Looks like late August.
(In reply to comment #13) > OK the appearance of the dotted border around flash objects in html pages > appeared between 23 and 27 july trunk builds. That's not what this bug is about. > Later on, not sure when, clicking on the flash object caused the browser to > always scroll to the top of the object. That's also not what this bug is about. This bug is about key events in the flash object scrolling the browser window.
According to Asa this bug is the same, I'll be glad to reopen my own bug. Anyhow here is more info. Between 25 and 27 august the dotted border got worse then it was, as from the on the border was shown all around the object.
Okay, the scroll thing first shows up between the august 31 and september 1 builds. One detail that may or may not be relevant is that the late august builds showed a full border around the flash object when clicked on (this is the behavior in current builds as well), but the earlier builds only showed a partial border.
> According to Asa this bug is the same, I'll be glad to reopen my own bug. That might be needed if fixing this one doesn't fix yours, yes. > Okay, the scroll thing first shows up between the august 31 and september 1 > builds. What are the timestamps on those builds (including the hour)?
(In reply to comment #17) > Okay, the scroll thing first shows up between the august 31 and september 1 > builds. Exactly, I jus checked and I can confirm that aswell. > One detail that may or may not be relevant is that the late august > builds showed a full border around the flash object when clicked on (this is > the behavior in current builds as well), but the earlier builds only showed a > partial border. Indeed I pinned this down by the following: Partial border showed up between 23 and 27 july trunk builds. Full border showed up between 25 and 27 august trunk builds.
Timestamps for Camino: 31-08-2004 - 16:20:00 01-09-2004 - 14:19:00
Wait. Is this "scroll thing" the fact that we scroll on click? Or the original bug reported here?
(In reply to comment #21) > Wait. Is this "scroll thing" the fact that we scroll on click? Or the original > bug reported here? Yes, that's the scroll on click, which is supposedly related to this bug (the duped bugs in comments 5 and 6).
Could you please find the regression window for _this_ bug? Given the wide spread of dates involved in the various problems here, I am pretty sure they are not very related to each other.
hm, I can repro the issue in comment 0 using firefox 0.8, which came out 06-Feb-2004.
Flags: blocking1.8a5? → blocking1.8a5-
...and even occurs on firebird 0.7.1.
Jasper? In comment 2 you said this wasn't an issue in Firefox 1.0?
(In reply to comment #26) > Jasper? In comment 2 you said this wasn't an issue in Firefox 1.0? In FF 1.0 (Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/ 1.0) The same page originally reported does this: 1. Click anywhere on the Flash movie. 2. Keyboard keys, including cursor and spacebar, all go to the Flash movie. 3. Click outside the Flash movie (way down below the footer--there's a blank green area that's techinically part of the movie). 3. Keyboard all goes to the HTML page -- cursor keys scroll page, etc.
(In reply to comment #26) > Jasper? In comment 2 you said this wasn't an issue in Firefox 1.0? it's present in the old firebird builds because they were from the trunk, iirc. the aviary branch isn't affected but it goes pretty far back on the trunk--way past the last camino nightlies we have (july).
OK.... So can people narrow down when this broke on trunk, then?
Embedded Quicktime movies alos show the dotted border. Why is that?
can we get some traction on this? mac trunk builds are basically unusable because of this bug. this is a very serious regression and the fact that it's gone untouched for so long is disappointing. this is a mozilla plugin bug it should NOT be assinged to me.
Assignee: pinkerton → nobody
Severity: major → blocker
Flags: blocking1.8a6?
Keywords: regression
QA Contact: core.plugins
Mike, I've spent a month now trying to find out when this broke, in the face of people hijacking the bug and apparent general apathy on the part of people who can reproduce the original problem reported here. I'm willing to help find the checkin that regressed this and help figure out why it caused this problem, but I can't reproduce the bug, and I have been given no indication where to even start looking. Any help you can manage, either yourself or by convincing someone with Camino builds around to narrow down the regression window, would be much appreciated.
This is getting hard to keep track of, we may be dealing with a separate Camino issue from the Seamonkey one. Camino 2003030613 (v0.7 release) - Issue not present Camino 2004062308 (v0.8 release) - Issue present as originally reported Camino 2004070108 (v0.8+) - Issue present as originally reported (oldest Camino nightly I can find) Seamonkey 20040714 (1.8a2 release) - Issue not present Seamonkey 20040817 (1.8a3 release) - Issue present as originally reported So, it seems that Camino was affected by the time the branch was cut for 0.8 (this May), but Seamonkey wasn't affected until sometime between the 1.8a2 and 1.8a3 releases (late July - early August). It would be nice if someone had a hidden stash of old nightly builds. ;-) Additionally, somebody should reopen Bug 265461 and/or Bug 270113 as it's not likely they're related to this one, judging by the regression timetables.
One other thing I noticed: when pressing the arrow keys in affected Seamonkey builds, the page scrolls as long as the key is held down. However, Camino only scrolls on the initial keypress.
> It would be nice if someone had a hidden stash of old nightly builds. ;-) You mean other than http://archive.mozilla.org/pub/ (mozilla/ or camino/ depending on which you want) ?
ender, can you try to narrow this down to a smaller regression window?
too late for 1.8a6. blocking-
Flags: blocking1.8a6? → blocking1.8a6-
Keywords: helpwanted
Flags: blocking1.8b?
*** Bug 257488 has been marked as a duplicate of this bug. ***
FWIW, I can type into Flash in a Firefox 1.0 build (branch) but not trunk.
Summary: Plugins embedded in html behave like regular images on click and keys. → Plugins embedded in html behave like regular images on click and keys (can't type in Flash)
Probably a dup of bug 257488.
Depends on: 257488
Fixed by the patch in bug 257488.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Flags: blocking1.8b?
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.