Larry_Kuck

I am converting over from Internet Explorer to Firefox, and transferring my log-in data to the Firefox browser.

When I visit the Surpass Hosting Client Area, I am looking at clogin.php, which displays a link in the top right, "need help? visit our support center. ======"
where ===== is a long thin box set to be level with the upper half of the words in the link.

MSIE7 displays this same link with a red x left of the words, and then a box outline around the link. A mouse-over properly highlights the link. The red x indicates a missing image.

Back to the Firefox view, a mouse-over will cause the screen content to jump downward, and the link disappears. To its right, there is a missing-image icon followed by the thin box ===== centered vertically on the right of the image icon.

If I hang around long enough I get the link back and can click it before it goes away again.

I have the W3C HTML Validator installed, and it lists a whole bunch of errors on the page.

My suggestion is that your page writers use Firefox and all of its available development tools, write good code and then deal with inferior browsers like all versions of MSIE and early versions of others. And either remove the reference to the missing images or restore the images.

Similar jumpiness has been seen on this Post New Tread page that I write this note in, but there are only 2 errors in your source code on this page. Now that I've populated the edit box with this post, there is no jumpiness that I can reproduce. Perhaps that was due to missing images not yet loaded from the server.

I test the site I host with Surpass Hosting with Firefox first of all, then Opera and Safari for Windows, as well as MSIE7.

Jumpiness may be eliminated simply by specifying height and width of missing images, so that as a page loads, the image has space reserved for it. Another thing I do is float a container DIV with width and height specified, and then place the image inside the div. That can ensure the page won't bounce around as the mouse is dragged over it. Also ensure that you don't change font-sizes with a mouse-over, which also may force other content to move to accommodate the differing size of a block of text.

The same comments that I made about clogin.php apply to the client-area script once the user is logged-in.

Brandonnn

could you provide a link to your initial problem? or is this a private link? A before and after screenshot would definitely help.

I'm using Firefox 2 and 3 Beta on Both Windows, OS X, and Ubuntu 7.10. I haven't seen any jumpiness. Could you be more specific as to where the jumpiness occurs.

BTW Most people don't follow W3C validation... & IE7 is a total different animal than Firefox so you might have to just get used to the difference in the way Firefox renders pages.

__________________
poof

Larry_Kuck

The address in question is:
http://whmap.surpasshosting.com/clogin.php

and I have uploaded two screenshots of the top right corner of the page. The mouse pointer was not included in the Mouseover, but I managed to get the mouse pointing to where the link was, and capture the screen before the link reappeared. The box I represented with ===== is actually the box that is supposed to surround the link.

Agreed Firefox is different from MSIE. Too bad that MS can't pool enough talent together to create a good browser to put in its Windows OS, and chooses instead to build one that supports sloppy page design of the past.

A business should strive to put up a site, not necessarily standards-perfect, but one that won't break when a good browser looks at it.

These screenshots prove there is something in need of improvement.

Attached Images

	clogin-php-top-right-firefox2-winXP.png (27.6 KB, 27 views)
	clogin-php-top-right-MOUSEOVERfirefox2-winXP.png (26.5 KB, 25 views)

Brandonnn

hmm... i will notify miss Kayla. Thanks for the link.

__________________
poof

Larry_Kuck

Hi Brandon,
Let me thank you for your further explanation in my email; I followed that link, and I was advised to follow the link at the bottom of the page, because I've been signed-up since before May 2006. That took me back to this busted page in question.

Once I am migrated into the new billing system, which I am currently discussing with Accounting, I would imagine that I will begin using this new page!

And the issue of this thread will be moot.