Closed
Bug 105330
Opened 24 years ago
Closed 23 years ago
Image rollover doesn't work on MM JS
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect)
Tracking
()
RESOLVED
FIXED
Future
People
(Reporter: filiperf, Assigned: jdunn)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.5) Gecko/20011011
BuildID: 2001101117
Using Mozilla 0.9.4 or 0.9.5, image rollover on Macromedia JS does not work as
expected. 0.9.3 (and 0.9.2?) worked just fine. The URI above is just one
example. Any page I've encoutered using those scripts didn't work as NS
3.x/4.7x, MSIE 5.01/5.5, or Opera 5.1x.
Reproducible: Always
Steps to Reproduce:
1.Load page
2.Place mouse over image (linked)
3.Remove mouse from over the image
Actual Results: Images were veeeeeeeery slow to "roll".
Expected Results: Should "roll" on-the-fly.
I'm not sure if this is a real bug, or if something is wrong with MM code. Also
I'm no sure if this is a Javascript Engine issue or Browser-General one.
Comment 1•24 years ago
|
||
imagelib
Assignee: asa → pavlov
Component: Browser-General → ImageLib
QA Contact: doronr → tpreston
Comment 2•24 years ago
|
||
this worksforme on win98. Could you try with a new profile perhaps?
Comment 3•24 years ago
|
||
This code
function MM_findObj(n, d) { //v3.0
suggests very stringly that the page was created with an old version of
macromedia which does not support the w3 DOM and only supports layers and d.all
Therefore, --> Tech Evangelism
P.S. Doesn't WFM Win2k 20011018 with a recent profile
Assignee: pavlov → nitot
Component: ImageLib → Europe: West
Product: Browser → Tech Evangelism
QA Contact: tpreston → caillon
Version: other → unspecified
| Reporter | ||
Comment 4•24 years ago
|
||
Tried with new profile, new version MM code (4.01), and the result is the same.
Build 2001110209/trunk works just fine on this department... :-(
Comment 5•24 years ago
|
||
Nothing wrong with the JS, AFAICT. The images also roll quickly for me.
back to imglib for further triaging.
Assignee: nitot → pavlov
Component: Europe: West → ImageLib
Product: Tech Evangelism → Browser
QA Contact: caillon → tpreston
Version: unspecified → other
Comment 6•24 years ago
|
||
Filipe, are you saying that this bug is not present in build 2001110209/trunk?
Or did I misunderstand your comment? Are people seeing this on anything _but_
Win2k?
| Reporter | ||
Comment 7•24 years ago
|
||
Boris, you're right. Build 2001110209/trunk worked fine for me. After that some
I've tried (sorry but I don't remember the build numbers...) did not work. And
the same with 0.9.7: is still slooooooow.
Comment 8•24 years ago
|
||
Filipe, could you possibly test with a current nightly?
| Reporter | ||
Comment 9•24 years ago
|
||
Boris: I've tried with 2001122603, and the result is the same - slow. It seems
that the preload of the rollover images is not done, and the download of them
only starts when the mouse is placed over one. IE 5.5SP2 acts a bit like the
same, but faster (IE 5.0 is fine). NS 4.79 is perfect. Hope this helps.
Comment 10•24 years ago
|
||
confirming since this is still a problem with current builds
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Reporter | ||
Comment 11•24 years ago
|
||
2002011509 (mozilla-win32-svg-mathml.zip from
http://ftp.mozilla.org/pub/mozilla/nightly/2002-01-15-08-trunk) is fine.
| Reporter | ||
Comment 12•24 years ago
|
||
2002011604 (mozilla-win32-installer-sea.exe from
http://ftp.mozilla.org/pub/mozilla/nightly/2002-01-16-15-trunk/) is also OK.
Comment 13•24 years ago
|
||
this seems to be fine now. anyone still seeing this?
| Reporter | ||
Comment 14•24 years ago
|
||
From 2002011509 to 2002011913 that's OK with me.
Updated•24 years ago
|
Target Milestone: --- → Future
Updated•23 years ago
|
Component: ImageLib → Image: Layout
| Reporter | ||
Comment 15•23 years ago
|
||
With 2002102808-trunk/win images simply don't "roll". Don't know if it's related
to Bug 176259 or some other new/uncofirmed ones.
| Reporter | ||
Comment 16•23 years ago
|
||
2002110108-trunk/win is close to be fine: good on first load, veery slow on
second visit; but I still don't know if this is related to this bug or not.
| Assignee | ||
Comment 17•23 years ago
|
||
"mass" re-assigning of bugs from pav to myself
Assignee: pavlov → jdunn
| Assignee | ||
Comment 18•23 years ago
|
||
Ok, I inherited this... and can't seem to see the problem
using moz 1.0 or the trunk. I did think about the known
javascript failing to preload problem, but if you are seeing
that kind of delay I am assuming you are either on a very
slow machine or a very slow connection. I tried it on my
200MhzPII but the roll over looked fine using moz 1.3a.
I am stumped... can you think of anything else about your setup
that might help me figure this out? thanks
| Reporter | ||
Comment 19•23 years ago
|
||
Hi. I've tested this one again, using 1.0.2, 1.3a, and 2003020508-trunk, all of
them on Win2K Pro SP3; the profiles used for each one were freshly created at
the end of the installation process; in the cache preferences, I selected "Every
time i view the page" (and uncheked "Prefech" on 2003020508-trunk).
With every one, I started out at the URI referenced, then browsed arround the
www.isa.utl.pt, ciisa.isa.utl.pt, www.brpi.net, and Mozilla web sites. After
some 5 minutes of browsing reloading, I've returned to
http://www.isa.utl.pt/deasr/ and browsed some more pages under that path; them,
on 1.0.2, 1.3a (and 1.2.1, my standard) the rollover action became slow, and I
could notice some network activity on my PC every time the mouse floated over
the rollover images (it didn't happened at first); 2003020508-trunk was fine.
Hope this helps...
Comment 20•23 years ago
|
||
Filipe, so you're basically saying that it's not a problem with current builds
but only with old ones?
| Reporter | ||
Comment 21•23 years ago
|
||
Well, if you're not considering 1.0.2, the stable build I believe, nor the other
two releases, 1.2.1 and 1.3a, yes. It only worked for me on the latest trunk
build. I've provided 1.0.2, 1.2.1 and 1.3a as references.
Comment 22•23 years ago
|
||
Right. The only one of those being actively developed (and hence getting fixes)
is the current trunk build. ;)
| Reporter | ||
Comment 23•23 years ago
|
||
OK. That's fine with me. In my humble opinion, though, 1.0.x branch should get a
fix too (I didn't test that branch builds, but I can you or Jim fell it's
necessary).
Comment 24•23 years ago
|
||
Well, _if_ someone can take the time to track down what fixed this and _if_ it's
a really safe patch it _may_ go on the 1.0 branch.
But mostly 1.0 branch is only taking severe crash (not many of those) and
security fixes.
| Reporter | ||
Comment 25•23 years ago
|
||
OK, OK! I've already said it's fine with me... :)
| Assignee | ||
Comment 26•23 years ago
|
||
I am going to mark this fixed. As Boris mentioned the
1.0 branch is stability only. If I didn't have all the
other bugs backed up on my plate, I would definitely look
to figure out which bug/fix took care of this problem.
However, given the world we live in, I am going to settle for
it being fixed.
If you happen to see this again (especially check 1.3 Final
when it comes out), feel free to re-open.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 27•23 years ago
|
||
OK! I will. Thanks, and thank you all for you work.
| Reporter | ||
Comment 28•22 years ago
|
||
Errr... Maybe some bad news. 1.3 is out, and I tested it on this one. It got
more complicated to demonstrate, and I changed the URL too, to reflect the new
testing.
1. Open http://www.brpi.net/
2. Browser arround that site for a few pages (reuse some, as there are so few...)
3. Open a second Tab on the same site
4. Switch tabs and use the navigational logo (top left)
5. When switching from one tab to another, most of the times, it is slow on the
rolls; sometimes is not.
As this is weird, and very particular, I didn't re-open it. If you feel it's
worth to do it, please do so. Thanks.
Updated•7 years ago
|
Product: Core → Core Graveyard
Updated•7 years ago
|
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•