Is it me, or…? (Mozilla 1.7.1)

Topic

New Reply

I visited this W3C site using Mozilla 1.7.1 and found the page scrolled extremely slowly. The same page visited using IE scrolled normally.

Mark (MarkJ) Johnston’s recent wedding site visited using IE exhibits mouse-over effects on the left side navigation links. Mozilla 1.7.1 does not.

Does anyone else experience this, or is it just me?

Cheers,

Reply | Quote

Replies

Any chance you’ve disabled JavaScript? (I have Firefox, so I’m not sure I can point you to it in your dialogs.)

Reply | Quote

Hi Jefferson,

Just Checked… I do have JavaScript enabled for the browser, disabled for mail and newsgroups. One other symptom I experience with the scrolling at W3C is that the scrolling effect is buffered. I can hold down the arrow-down button then release it and the (slow) scrolling continues. The same is true for the scroll wheel. These Lounge threads, on the other hand, scroll very swiftly.

Cheers,

Reply | Quote

Is there a JavaScript console in Moz 1.7.1? In Firefox, it’s on the Tools menu, but in NS 4.x, I think you had to type about:javascript into the address line. Anyway, if the browser things there is an error in the script (either in the page or in an include file), maybe it is refusing to do the mouseovers?

Reply | Quote

There is a JavaScript and a Java console in Mozilla 1.7. I have never used either, however. How would I use these and what should I be looking for?

Cheers,

Reply | Quote

If the browser encounters a script error, it should be listed in the JavaScript console. I think it gets cleared when you close all active windows of the browser, but until then, it just accumulates. In Firefox, the errors are clickable and open the source code to the offending line. This is so much faster and handier than Microsoft’s script de######, which only deals with the “current” error, but obviously much simpler and less powerful than a true de###### can be.

However… the W3C page doesn’t use any script, so maybe there is a problem with something in the stylesheets???

Reply | Quote

Neat stuff, Jefferson. I turned on the JavaScript console and went to MarkJ’s wedding site. Still no mouse-over effects and no JavaScript errors. I am getting errors trying to reply to you, however. I’ll try to attach a Scrn Prnt .

Don’t know much about CSS so I’ll live with the slow scroll there.

Cheers,

Reply | Quote

Paul, those errors relate to some stuff in the Lounge’s compose page and the pop-up tag panels. Nothing fatal. They reflect a world that predates modern versions of Netscape/Mozilla. Would be nice to fix, but I suspect no one has the energy to do a major rewrite at this point. Too many other projects.

Reply | Quote

Paul, those errors relate to some stuff in the Lounge’s compose page and the pop-up tag panels. Nothing fatal. They reflect a world that predates modern versions of Netscape/Mozilla. Would be nice to fix, but I suspect no one has the energy to do a major rewrite at this point. Too many other projects.

Reply | Quote

Neat stuff, Jefferson. I turned on the JavaScript console and went to MarkJ’s wedding site. Still no mouse-over effects and no JavaScript errors. I am getting errors trying to reply to you, however. I’ll try to attach a Scrn Prnt .

Don’t know much about CSS so I’ll live with the slow scroll there.

Cheers,

Reply | Quote

If the browser encounters a script error, it should be listed in the JavaScript console. I think it gets cleared when you close all active windows of the browser, but until then, it just accumulates. In Firefox, the errors are clickable and open the source code to the offending line. This is so much faster and handier than Microsoft’s script de######, which only deals with the “current” error, but obviously much simpler and less powerful than a true de###### can be.

However… the W3C page doesn’t use any script, so maybe there is a problem with something in the stylesheets???

Reply | Quote

There is a JavaScript and a Java console in Mozilla 1.7. I have never used either, however. How would I use these and what should I be looking for?

Cheers,

Reply | Quote

Is there a JavaScript console in Moz 1.7.1? In Firefox, it’s on the Tools menu, but in NS 4.x, I think you had to type about:javascript into the address line. Anyway, if the browser things there is an error in the script (either in the page or in an include file), maybe it is refusing to do the mouseovers?

Reply | Quote

Hi Jefferson,

Just Checked… I do have JavaScript enabled for the browser, disabled for mail and newsgroups. One other symptom I experience with the scrolling at W3C is that the scrolling effect is buffered. I can hold down the arrow-down button then release it and the (slow) scrolling continues. The same is true for the scroll wheel. These Lounge threads, on the other hand, scroll very swiftly.

Cheers,

Reply | Quote

Just reporting in with a partial solution. Jefferson and Al were both correct in wondering if I had turned off JavaScript support. While I did have JavaScript enabled, I had certain JavaScript commands disabled. Among them was one that prevented the onMouseOver event on MarkJ’s site from working.

Still have not found a solution (nor the cause) for the slow scrolling on the W3C site.

Cheers,

Reply | Quote

Just reporting in with a partial solution. Jefferson and Al were both correct in wondering if I had turned off JavaScript support. While I did have JavaScript enabled, I had certain JavaScript commands disabled. Among them was one that prevented the onMouseOver event on MarkJ’s site from working.

Still have not found a solution (nor the cause) for the slow scrolling on the W3C site.

Cheers,

Reply | Quote

Any chance you’ve disabled JavaScript? (I have Firefox, so I’m not sure I can point you to it in your dialogs.)

Reply | Quote

First check on Jefferson’s question, ’cause I’m running Moz 1.7.1 and the two pages you mentioned behave OK for me in both Moz and IE 6. It took only a few seconds using the down-arrow key, to scroll from the top of the page to the bottom.

(This is a footnote, just in case you weren’t aware. This is not applicable in the case of Jennifer and Mark’s site, but (unless they’ve changed it lately) Mozilla does not display POP UP text for the HTML tag for ALT= but will display the popup for TITLE= To deal with it, I use both for anything I code, such as my license plate signature.)

Reply | Quote

Hi Al,

This is strange. As I indicated to Jefferson, JavaScript is enabled. Most sites I visit work properly (as far as I can determine), yet these two don’t. I will review my preferences again to see if anything is amiss.

I am aware of the ALT/TITLE issue. I had a post (can’t find it now) in one of these forums complaining that the little graphics at the end of post titles on the forum index pages only use the ALT tag and not the TITLE tag. I could be wrong here, but I think that post was addressed to you at about the time you became a WMVP. I thought that as you were a dyed-in-the-wool Mozilla fan, you could use your influence as a WMVP to convince the powers-that-be to adopt both the ALT and TITLE tags.

Cheers,

Reply | Quote

The ALT tag is for people who don’t view images (whether because they want a faster browsing experience or because their browser is reading the page to them).

The TITLE tag is for tooltips for mouse users. I guess the question is: do those images need tooltips? If so, we can put those on our “to do” list.

Reply | Quote

I kinda like the idea of keeping things granular. As you implied, not all images need tooltips-but all images need ALT tags IMO. And I’ve written some ALT tags that would be fairly inappropriate as tooltips. (Of course if I was thinking about the ALT tag as a tooltip I would have probably written it differently.)

Reply | Quote

It seems to me that the purpose of the little graphics is to convey information. That information is not always self-evident from the graphic itself. I think the ALT tags were used here to produce a tool tip identifying the meaning of the graphic. In your post below, I know the picture frame icon indicates your post has a graphic attached. However, it took me a while to determine that the other graphic indicated you had edited the post. A TITLE tag tool tip would have immediately made it apparent. Just my .

Cheers,

Reply | Quote

It seems to me that the purpose of the little graphics is to convey information. That information is not always self-evident from the graphic itself. I think the ALT tags were used here to produce a tool tip identifying the meaning of the graphic. In your post below, I know the picture frame icon indicates your post has a graphic attached. However, it took me a while to determine that the other graphic indicated you had edited the post. A TITLE tag tool tip would have immediately made it apparent. Just my .

Cheers,

Reply | Quote

>do those images need tooltips? If so, we can put those on our “to do” list.

We should probably hold off on the “to do” list. There has been an extension available for Firefox (& all its Mozilla predecessors) that enables tooltips for icons.

Reply | Quote

What extension is that ? Thanks.

Reply | Quote

Hi John

It is Popup ALT Attributes

Reply | Quote

Great – got it thanks.

BTW: I’m not sure if this is undocumented or not, but I discovered that if you double click in an empty area on the tab strip, a new tab opens up with your home page. (This may need the Tabbrowser Preferences installed.)

Reply | Quote

That looks like a base feature Leif, I don’t have any tabbrowser extensions loaded… and I’m able to dbl-click for a new tab.

Of course, I’m a keyboard jockey, and the CTRL-T is simple enough for me .

Reply | Quote

Double-clicking in the tab bar does nada for me on Firefix 0.9 (patched). Then, I do have Tabbrowser Extensions configured to close the active tab – on a middle mouse button click.

Reply | Quote

I think it depends on your preferences. I have Close tab on double click installed, so that’s what happens when I double click a tab. Actually, I liked the extensions with 0.8 better.

Reply | Quote

I think it depends on your preferences. I have Close tab on double click installed, so that’s what happens when I double click a tab. Actually, I liked the extensions with 0.8 better.

Reply | Quote

Double-clicking in the tab bar does nada for me on Firefix 0.9 (patched). Then, I do have Tabbrowser Extensions configured to close the active tab – on a middle mouse button click.

Reply | Quote

That looks like a base feature Leif, I don’t have any tabbrowser extensions loaded… and I’m able to dbl-click for a new tab.

Of course, I’m a keyboard jockey, and the CTRL-T is simple enough for me .

Reply | Quote

Great – got it thanks.

BTW: I’m not sure if this is undocumented or not, but I discovered that if you double click in an empty area on the tab strip, a new tab opens up with your home page. (This may need the Tabbrowser Preferences installed.)

Reply | Quote

Thanks Tony. Will give it a try. And BTW, congratulations on the WMVP promotion.

Reply | Quote

Thanks Tony. Will give it a try. And BTW, congratulations on the WMVP promotion.

Reply | Quote

Hi John

It is Popup ALT Attributes

Reply | Quote

What extension is that ? Thanks.

Reply | Quote

>do those images need tooltips? If so, we can put those on our “to do” list.

We should probably hold off on the “to do” list. There has been an extension available for Firefox (& all its Mozilla predecessors) that enables tooltips for icons.

Reply | Quote

The ALT tag is for people who don’t view images (whether because they want a faster browsing experience or because their browser is reading the page to them).

The TITLE tag is for tooltips for mouse users. I guess the question is: do those images need tooltips? If so, we can put those on our “to do” list.

Reply | Quote

Hi Al,

This is strange. As I indicated to Jefferson, JavaScript is enabled. Most sites I visit work properly (as far as I can determine), yet these two don’t. I will review my preferences again to see if anything is amiss.

I am aware of the ALT/TITLE issue. I had a post (can’t find it now) in one of these forums complaining that the little graphics at the end of post titles on the forum index pages only use the ALT tag and not the TITLE tag. I could be wrong here, but I think that post was addressed to you at about the time you became a WMVP. I thought that as you were a dyed-in-the-wool Mozilla fan, you could use your influence as a WMVP to convince the powers-that-be to adopt both the ALT and TITLE tags.

Cheers,

Reply | Quote

Just to bring everyone up-to-date:

I downloaded/installed Mozilla 1.7.2 then I downloaded/installed Firefox 0.9.2. Also downloaded/installed latest Sun JVM (1.4.2_05). Used both Mozilla and Firefox to access MarkJ’s wedding site. Neither exhibited the mouse-over effects exhibited in IE6.

Al, I may not have adequately explained the mouse-over effect that I’m concerned about (hence the ALT/TITLE tag discussion). The effect I’m having a problem with is the navigation links down the left-hand side of the page. In IE6 the navigation links change from white text on purple background to yellow text on purple background when the mouse hovers over the link. The white circle also changes to yellow. This does not happen when I use Mozilla or Firefox.

As to the W3C site, both Mozilla and Firefox scroll very slowly. IE6 scrolls much faster.

I’m still looking…

Cheers,

Reply | Quote

Just to bring everyone up-to-date:

I downloaded/installed Mozilla 1.7.2 then I downloaded/installed Firefox 0.9.2. Also downloaded/installed latest Sun JVM (1.4.2_05). Used both Mozilla and Firefox to access MarkJ’s wedding site. Neither exhibited the mouse-over effects exhibited in IE6.

Al, I may not have adequately explained the mouse-over effect that I’m concerned about (hence the ALT/TITLE tag discussion). The effect I’m having a problem with is the navigation links down the left-hand side of the page. In IE6 the navigation links change from white text on purple background to yellow text on purple background when the mouse hovers over the link. The white circle also changes to yellow. This does not happen when I use Mozilla or Firefox.

As to the W3C site, both Mozilla and Firefox scroll very slowly. IE6 scrolls much faster.

I’m still looking…

Cheers,

Reply | Quote

First check on Jefferson’s question, ’cause I’m running Moz 1.7.1 and the two pages you mentioned behave OK for me in both Moz and IE 6. It took only a few seconds using the down-arrow key, to scroll from the top of the page to the bottom.

(This is a footnote, just in case you weren’t aware. This is not applicable in the case of Jennifer and Mark’s site, but (unless they’ve changed it lately) Mozilla does not display POP UP text for the HTML tag for ALT= but will display the popup for TITLE= To deal with it, I use both for anything I code, such as my license plate signature.)

Reply | Quote