Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 165
  • Last Modified:

When using mouseover images and display: none/block in HTML, NS & Mozilla don't know the page has loaded

Can anyone explain to me why NS 7+ and Mozilla's load bar in the bottom right of the browser window show that the page is still being read from the server when I use mouseover images, or toggle a block of html from display: none to display: block?

The page has definitely loaded, and the onLoad event fires correctly.

Thanks.
0
metalaureate
Asked:
metalaureate
  • 7
  • 5
1 Solution
 
COBOLdinosaurCommented:
Is this happening on specific sites or all pages?  Pehaps you could post a link to a site where it is happening.

Cd&
0
 
metalaureateAuthor Commented:
http://www.untangledmanager.com/services/judemo/wbf.asp

(this is my site)

Open one of the "Click for answers" buttons and watch the load-progress bar.
0
 
metalaureateAuthor Commented:
Oh, on *all* pages.
0
Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

 
COBOLdinosaurCommented:
Its the scripting.  The xbrowserAPI is has a problem.  The browser is expecting an additional packet that is never being delivered; or the script it messing up the path.

When I see the page and then look at the code, my first though is that there is about 3 times as much as should be need for a page that simple.  The browser is probably tipping over its own feet.  

When I see dynamicdrive script I generally go in the other direction.  They generally work i a limited way and I have even recommended them for amteur use, but they are generally to inflexible and unmaintainable to be usful in a professional environment.

Before you do anything, I would recommend you run the page through a validator to make sure it has no errors; because using tables for layout is an invitation to bugs.  Then play around with the scripting to see if it will give you some clue as to what the browser thinks is not being returned, or what the ASP in not returning.  As far as I can tell everything is being returned, so the load bar is not much more than an annoyance at this point.

Cd&
0
 
COBOLdinosaurCommented:
The places where you have the problem are both using the xbrowserAPI, so that almost certainly is where the problem is triggering from, but something else in the page could very well be setting up whatever it is chokeing on.

Cd&
0
 
metalaureateAuthor Commented:
Hi,

I don't think xbrowserAPI can have anything to do with it, for the following reasons:

1) I have copied the entire contents of xbrowserapi into the web page and I still get the problem.

2) See http://www.untangledmanager.com/dev/cinch.htm This uses xbrowserapi to cinch and uncinch a table containing an image, and the problem does not occur...

Weird, huh?
0
 
COBOLdinosaurCommented:
Weird?  No.  You have merely eliminated one possibility as a cause. It is a simple piece of isolated code be executed on plain basic page.  I am sure that would have been tested during development of the script.

What you have is a set up with many points of failure.  The problem my not be a single one in isolation , but rather a loadin gof the gun somewhere else and the trigger gets pulled elsewhere.  In the end it turn out that there is no bug in the page, but that it presents in such a way that a browser bug, server bug, or ASP bug, trips on it.

If the issue is critical then the way to proceed is to start removing things until the error stops and see if you can isolate the exact cause.  Could take hours, or day, or even weeks; but most certainly there is an answer.  Solving it is a matter of deciding how resource to invest in finding the solution.

Cd&
0
 
COBOLdinosaurCommented:
BTW,

I've done a couple of searches hoping to get lucky, but nothing shows up that is helpful.  Someone else might come along who has work through it in the past.

Cd&
0
 
metalaureateAuthor Commented:
Hi Cd&

It's not a critical problem; just annoying to me. I think it is just a bug in Mozilla. I have seen the behavior on other sites that uses style: none/block, by they are too embrassing to post the links here, if you get my drift.

0
 
COBOLdinosaurCommented:
Yeah I get the drift. ;^)  Those sites are generally very heavily scripted as well. Whereas there are thousands of sites using none/block.  If there were a bug in none/block that would be the kind of class one bug that would generate a lot of documentation, and there is not even buzz like that, so it almost certainly has to be script related.

Cd&
0
 
metalaureateAuthor Commented:
Cd&,

Ok, I've been doing some more testing. The issues has nothing to do with style:none/block; that was a red herring. Any JS change of an image src attribute causes the problem.
0
 
COBOLdinosaurCommented:
It was an interesting exploration, but I don't know that anything actually got solved.  Perhaps zero PAQ?

Cd&
0
 
Computer101Commented:
PAQed, with points refunded (500)

Computer101
E-E Admin
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now