asp:Menu control only works in IE. Solution = install Firefox
Found this page today:
Workarounds for "FDBK10939:asp:Menu control only works in IE"
- Install Firefox
- Install user agent spoofer from the updates site like SpoofX or similar.
- Set your useragent spoofer to fake that you are using IE when visiting MS websites.
- Poof, the problem magicly dispears and the menus work.
Heh. Thats looks like some free-for-all solution posting system, where someone that is not a Microsoft employee posted a solution to a problem.Comment by pepp5 at November 17, 2004 11:34 PM | Permalink
Henrik, my trunk Firefox build sometimes freezes for a while, when I'm visiting your blog. Do you know the cause of this? (do you even experience this problem?)
The page already seems to be almost loaded, when the freeze happens.
I have the same problem as Martijn - and with the official Firefox release (I did not have 1.0 since long enough to tell if it still happen, but for sure previous version including RC2 had it...)Comment by franCk at November 18, 2004 01:45 AM | Permalink
does it happen on the frontpage as well? or only on the entry pages like this page?Comment by Henrik Gemal at November 18, 2004 02:49 PM | Permalink
I don't really know, actually. Sorry. I think the frontpage, but I'm really not sure.
It only happens sporadically, otherwise I could maybe find the cause of this freeze.
I'm using yesterday's trunk build (as always, normally).
Hmm, just got it again on the frontpage. A freeze with 100% cpu for some 20 seconds. In the status bar I saw: Transferring data from http://www.pcworld.com, or something like that.Comment by Martijn at November 18, 2004 10:30 PM | Permalink
I think I know the cause.
It seems that this http://gemal.dk/js/titles.js script is to blame.
You have approximately 2700 links with a title on the frontpage of your blog, I mean this one:
Apparently that dom script lets Mozilla freeze for quite some time (I only have a 800MHz, I would think it is not that bad on faster computers).
With IE6, I don't habe a problem, so I would call this a bug, I think.
Ok, I've filed
on this issue.