Mac computer can not pull up the menu
Hi Folks.
I've found the problem
It's a bogus file - Believe it or not there is something inside the menu_data.js file that the Mac doesn't like.
Not sure what it is (don't really care
) But. . . If you copy the contents of the file and paste them into a new file it works, at least it does with UltraEdit on XP
Don't ya just love IE on the Mac
Anyway, let me know how you get on
Cheers
Andy
I've found the problem

It's a bogus file - Believe it or not there is something inside the menu_data.js file that the Mac doesn't like.
Not sure what it is (don't really care

Don't ya just love IE on the Mac

Anyway, let me know how you get on
Cheers
Andy
Tank U, oh great Master from the East (well, east of me, anyway!).Andy wrote:I've found the problem![]()

Not something I would have thought of. Assuming maybe an accidental invisible character of some kind (whatever), why didn't it go with the copy?Andy wrote:It's a bogus file - Believe it or not there is something inside the menu_data.js file that the Mac doesn't like.
Not sure what it is (don't really care) But. . . If you copy the contents of the file and paste them into a new file it works, at least it does with UltraEdit on XP
Hate it. M$ pulled out because they couldn't fix the dopey thing (IMHO).Andy wrote:Don't ya just love IE on the Mac![]()
John
Yeah, it happend before so I had a hunch (that's the "idea" type of hunch and not the "weird growth on ones back" type of hunch, in case you were wondering)
What I normally do for testing is pull the site down with IE (File-Save As) and then edit the .htm file to point to the dev copy of the menu. Then I can play with it and tweak it till its fixed.
It had to be something to do with the file. I took EVERYTHING out of it and it still returned an error. It's the most bizzare of problems... stoopid Macs
What I normally do for testing is pull the site down with IE (File-Save As) and then edit the .htm file to point to the dev copy of the menu. Then I can play with it and tweak it till its fixed.
It had to be something to do with the file. I took EVERYTHING out of it and it still returned an error. It's the most bizzare of problems... stoopid Macs

Found it
You have some blank lines before the first actual code line (_menuCloseDelay=500). Looking at it in ASCII mode, in the very top line there is a mysterious invisible o;? lurking there (just those 3 characters). No idea what they represent, but I don't see them in other _data files I just looked at. Also don't know why they didn't move over when Andy did a copy/paste, but it looks like you could also try just deleting those blank lines.

You have some blank lines before the first actual code line (_menuCloseDelay=500). Looking at it in ASCII mode, in the very top line there is a mysterious invisible o;? lurking there (just those 3 characters). No idea what they represent, but I don't see them in other _data files I just looked at. Also don't know why they didn't move over when Andy did a copy/paste, but it looks like you could also try just deleting those blank lines.
John
-
- Super Advanced
- Posts: 77
- Joined: Fri Jun 27, 2003 5:38 pm
- Location: TCI
It's the very first code line (after the mentioned blank lines) in your menu_data.js...Surfergirl wrote:forgive me but I can not find (_menuCloseDelay=500) in menu_data.js - I tried copy and paste into new file and he still cannt see das menu
Code: Select all
_menuCloseDelay=500 // The time delay for menus to remain visible on mouse out
_menuOpenDelay=150 // The time delay before menus open on mouse over
_followSpeed=5 // Follow scrolling speed
_followRate=40 // Follow scrolling Rate
_subOffsetTop=10 // Sub menu top offset
_subOffsetLeft=-10 // Sub menu left offset
_scrollAmount=3 // Only needed for Netscape 4.x
_scrollDelay=20 // Only needed for Netcsape 4.x
Before that you have 3 blank lines. It's in the first blank line that I found that invisible stuff. Since the c/p didn't work, try completely removing those 3 blank lines and resaving the file.
Also, he might have to clear his browser cache. With that piece of junk browser it's entirely possible he's still looking at a cached version of the page. Another trick is to hold down the Shift key while hitting the refresh button in the browser.
John
-
- Super Advanced
- Posts: 77
- Joined: Fri Jun 27, 2003 5:38 pm
- Location: TCI
I just pulled your menu data at /HortonRealty/milonic/menu_data.js and there are still 3 blank lines above the first menudelay stuff. Remove the lines entirely so that the file starts like this...
So basically _menuCloseDelay is the VERY first line in the file, and remember, dont copy the Line1,Line2,... that I put in the example. 
Code: Select all
Line1: _menuCloseDelay=500
Line2: _menuOpenDelay=150
Line3: _followSpeed=5 // Follow scrolling speed
Line4: _followRate=40 // Follow scrolling Rate

Dave Hergert
Software Engineer
"Helping to make the menu better, one
at a time."
Software Engineer
"Helping to make the menu better, one

-
- Super Advanced
- Posts: 77
- Joined: Fri Jun 27, 2003 5:38 pm
- Location: TCI
Don't see it that way here, Dave. The blank lines are gone (remember, she's moved to a new URL), and so are the goofy characters.
However, looking at the file exactly the same way I did earlier (changing the suffix to .txt, and opening it in Word as US-ASCII), I now see an unprintable character (open box) between every character in the file. I did not see that before using the same setup.
However, looking at the file exactly the same way I did earlier (changing the suffix to .txt, and opening it in Word as US-ASCII), I now see an unprintable character (open box) between every character in the file. I did not see that before using the same setup.
John
-
- Super Advanced
- Posts: 77
- Joined: Fri Jun 27, 2003 5:38 pm
- Location: TCI
-
- Super Advanced
- Posts: 77
- Joined: Fri Jun 27, 2003 5:38 pm
- Location: TCI
-
- Super Advanced
- Posts: 77
- Joined: Fri Jun 27, 2003 5:38 pm
- Location: TCI