 | | shop.lego.com bug report —Charles Eric McCarthy
|
| | | Hi, When I go to shop.lego.com and click on my country's flag (USA), I get a javascript error, and I cannot get past the flag page. When I look at the javascript console, I see this: JavaScript Error: (URL) line 3: invalid label. FONT-SIZE: 10px; (...) (23 years ago, 8-Feb-01, to lugnet.lego.direct)
|
| | | |
| | | | | Re: shop.lego.com bug report —Cary Clark
|
| | | | This is not a JavaScript effort per se. The cascading style sheet specification is being interpreted as if it were a script instead. This is wierd. It is as if the Solaris is getting served this: <script type="text/css" (...) (23 years ago, 8-Feb-01, to lugnet.lego.direct)
|
| | | | |
| | | | | | Re: shop.lego.com bug report —Charles Eric McCarthy
|
| | | | (...) Thanks for looking atthis, Cary. I'm getting: <!-- Start topnav --> <style type="text/css" src="/styles/navigat..."></style> /Eric/ (23 years ago, 9-Feb-01, to lugnet.lego.direct)
|
| | | | |
| | | | | | Re: shop.lego.com bug report — Tomas Clark
|
| | | | Thanks for spotting this bug, Eric. It's a Netscape quirk that can be avoided, and it should be fixed soon. For the curious, the quirk is that Netscape sometimes treats style tags like script tags -- they were implemented around the same time, so I (...) (23 years ago, 9-Feb-01, to lugnet.lego.direct)
|
| | | | |
| | | | | | Re: shop.lego.com bug report — Tomas Clark
|
| | | | Update: this bug should be fixed now. Tomas Clark LEGO Direct (...) (23 years ago, 13-Feb-01, to lugnet.lego.direct)
|
| | | | |
| | | | | | Re: shop.lego.com bug report —Charles Eric McCarthy
|
| | | | (...) Thanks for the update, and for getting it fixed. However, I still can't shop! I no longer get any javascript errors. However, after I click on the USA flag and it contacts shop.lego.com, I get put right back at (URL) clears and refreshes the (...) (23 years ago, 13-Feb-01, to lugnet.lego.direct)
|
| | | | |
| | | | | | Re: shop.lego.com bug report — Tomas Clark
|
| | | | This sounds like a cookie problem -- possibly on your end, which is easier to fix, so it's the best place to start. Have you tried: - clearing out your cache (aka temporary internet files, but I believe in Netscape it's usually called cache). Always (...) (23 years ago, 13-Feb-01, to lugnet.lego.direct)
|
| | | | |
| | | | | | Re: shop.lego.com bug report —Timothy Carl Buchheim
|
| | | | | (...) rm -rf ~/.netscape/cache/* (...) UNIX versions of Netscape keep their cookies in the file ~/.netscape/cookies better than deleting the file, just edit it in your favorite editor (please, no vi/emacs holy wars here!) and delete any lines (...) (23 years ago, 13-Feb-01, to lugnet.lego.direct)
|
| | | | | |
| | | | | | | Re: shop.lego.com bug report —Charles Eric McCarthy
|
| | | | | | (...) ... (...) and (...) and William Ward wrote: (...) That was actually the first thing I tried, a long time ago. Also, my netscape cache was in a nonstandard location, but I found it. After removing all my cache files and cookies file and (...) (23 years ago, 13-Feb-01, to lugnet.lego.direct)
|
| | | | | | |
| | | | | | | | Re: shop.lego.com bug report — Tomas Clark
|
| | | | | | Yet another update: I've been told that along with the changes to the shop that were published yesterday, there were some additional code changes that will hopefully keep this "bad cookie" problem from happening again in the future. Of course, (...) (23 years ago, 15-Feb-01, to lugnet.lego.direct)
|
| | | | | | |
| | | | | | Re: shop.lego.com bug report —James Brown
|
| | | | | (...) <snip> Just an FYI, Tomas; I've noticed this error both from home & work (one is Netscape, one is IE; both on Windows 98). The standard 'bad cookie' fixes didn't seem to help (although I didn't kill my cookies at work - too much of a pain to (...) (23 years ago, 13-Feb-01, to lugnet.lego.direct)
|
| | | | | |
| | | | | | Re: shop.lego.com bug report —William R. Ward
|
| | | | (...) On Solaris, it is in the file .netscape/cookies under your home directory. It is possible that the original poster had cookies disabled, however; if so, he may need to turn them on. --Bill. (23 years ago, 13-Feb-01, to lugnet.lego.direct)
|
| | | | |
