943,978 Members | Top Members by Rank

Ad:
You are currently viewing page 3 of this multi-page discussion thread; Jump to the first page
Apr 13th, 2008
0

Re: JavaScript Fix

Oh, also, in response to an IM with tgreer, you can't use the Adblock extension for FireFox to block the /scripts/style.php file because it only lets you disable javascript files that have a .js extension. You will have to use the [search]hosts file[/search], where you reroute http://www.daniweb.com/scripts/style.php and http://www.daniweb.com/scripts/menu.php to localhost. Disabling these two files is the only way to block the menu dropdown and the tooltips without any side effects or JavaScript errors on the page.
Administrator
Staff Writer
Reputation Points: 1422
Solved Threads: 162
The Queen of DaniWeb
cscgal is offline Offline
13,645 posts
since Feb 2002
Apr 13th, 2008
0

Re: JavaScript Fix

Quote ...
2 seconds? Do you have proof of this? The default time for Windows tooltips is 400 ms and is a setting in the registry
many people/system tuners change this to make the start menu pop up quicker
Moderator
Featured Poster
Reputation Points: 1800
Solved Threads: 575
Moderator
jbennet is offline Offline
16,520 posts
since Apr 2005
Apr 13th, 2008
0

Re: JavaScript Fix

That's why I said "the default time" But the start menu popup speed and tooltip speed are two different settings.
Administrator
Staff Writer
Reputation Points: 1422
Solved Threads: 162
The Queen of DaniWeb
cscgal is offline Offline
13,645 posts
since Feb 2002
Apr 13th, 2008
1

Re: JavaScript Fix

>you can't use the Adblock extension for FireFox to block the /scripts/style.php file because it
>only lets you disable javascript files that have a .js extension.

Huh? I block .php files all the time with the Adblock extension. And just to test it now, I blocked both style.php and menu.php, and the drop-down menus and tooltips don't appear anymore.
Team Colleague
Reputation Points: 2240
Solved Threads: 338
Vampirical Lurker
John A is offline Offline
5,055 posts
since Apr 2006
Apr 14th, 2008
0

Re: JavaScript Fix

That's weird. tgreer said it wouldn't work.
Administrator
Staff Writer
Reputation Points: 1422
Solved Threads: 162
The Queen of DaniWeb
cscgal is offline Offline
13,645 posts
since Feb 2002
Apr 14th, 2008
1

Re: JavaScript Fix

Screenie:
Click image for larger version

Name:	Picture 1.png
Views:	23
Size:	59.4 KB
ID:	5811
Team Colleague
Reputation Points: 2240
Solved Threads: 338
Vampirical Lurker
John A is offline Offline
5,055 posts
since Apr 2006
Apr 14th, 2008
1

Re: JavaScript Fix

Don't listen to tgreer. He doesn't post here anymore, anyway.
Team Colleague
Reputation Points: 227
Solved Threads: 37
Made Her Cry
tgreer is offline Offline
1,697 posts
since Dec 2004
Apr 14th, 2008
0

Re: JavaScript Fix

Click to Expand / Collapse  Quote originally posted by cscgal ...
> But your site makes the tip appear almost immediately. The standard tip takes 2 seconds on FF.

2 seconds? Do you have proof of this? The default time for Windows tooltips is 400 ms and is a setting in the registry. It affects all Windows-based apps including the Start Menu, Explorer, Internet Explorer, etc. For FireFox to have a different setting, I guess they don't use the Windows-based tooltips but instead their own application-specific ones? Our tooltips used to be 250 ms and we just upped it to 500 ms, to make it on par with the Windows default.
I don't really know how to prove it, but I put a digital clock next to the screen. But human reaction time is .35 to .85 seconds, so I can't get it any closer. I am seeing three different times on automatic displays on these pages:

- A period too short to measure on the dropdown menus.
- about half a second on the DaniWeb tooltips.
- About 1.5 seconds on the Windows screen tips (e.g. on the DaniWeb link in the upper left corner).

Another difference is that the Daniweb tooltip takes time (about 1/2 second) to completely appear.

I want you to imagine the following:

A website loads a full screen if information. Then a tooltip appears, and immediately the rest of the screen clears. Then the information loads again. And every time a tooltip appears or disappears, this same thing happens again.

I know the actual screen doesn't do that, but that is what happens to the text image in my visual cortex.

Quote ...
> When I post, the reply that the page has been posted never comes. The loading-whizzer keeps spinning, until I get a "The host is not responding" error. So I don't know if the post has gone through. So I post it again (If I check first, I lose the post text from the posting window), and sometimes end up with two posts.

This used to happen to me every so often (like once a week). The post ALWAYS went through, so I would just refresh the page and the post would show up. If you're afraid it won't, just copy your post to the clipboard before refreshing. This isn't something that happens quite often though, right?
In my case, the post went through about 3/4 of the time. It is now happening about once a week. It seems to coincide with the page delays because an ad loads late.

Quote ...
> Because of my low-level dyslexia, I use the mouse pointer to follow my reading, so I don't lose my place or repeat lines. The tips prevent that, by covering the text I'm trying to read. That share box does the same thing in the original post of each topic.

Is it possible for you to move your mouse pointer either over or directly below the line you're trying to follow? The tooltips never cover up any of the line that is initiating them.
I'm doing something like that, but it takes longer.

Quote ...
> I have since determined that the scroll problem, the disappearing cursor, and the 100% CPU are the same thing - the ad-hog stealing cycles.

I'm not sure why you're experiencing these, but since they're ad-related, this has nothing at all to do with whether JavaScript features are enabled or disabled, as the ads load the same either way.
Originally you said the rounded corners script was causing the scroll and disappearing insertion point troubles, and disabling JavaScript cured that. Now I think they are ad-related. They seem to come and go with the activity of the various ads.
Reputation Points: 730
Solved Threads: 181
Nearly a Senior Poster
MidiMagic is offline Offline
3,314 posts
since Jan 2007
Apr 14th, 2008
0

Re: JavaScript Fix

> Originally you said the rounded corners script was causing the scroll and disappearing insertion point troubles, and disabling JavaScript cured that.

That was when we were using this fancy JavaScript to create the rounded corner effect, which was having a bunch of unforseen side effects. We don't use that JS anymore. It was causing all different side effects on different computers so everything strange going on, I blamed on it.
Administrator
Staff Writer
Reputation Points: 1422
Solved Threads: 162
The Queen of DaniWeb
cscgal is offline Offline
13,645 posts
since Feb 2002

This thread is more than three months old

No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.
Message:
Previous Thread in DaniWeb Community Feedback Forum Timeline: bad rendering
Next Thread in DaniWeb Community Feedback Forum Timeline: Tab width within Code tags





About Us | Contact Us | Advertise | Acceptable Use Policy
Forum Index | Build Custom RSS Feed


Follow us on Twitter


© 2011 DaniWeb® LLC