Closed GoogleCodeExporter closed 9 years ago
Thanks for your feedback!
I run the same configuration but of course don't have this problem, so I need
some
more information.
Does this behavior occurs on every page or only on specific ones?
Original comment by Rudolf....@gmail.com
on 12 Jul 2009 at 4:03
I find it happens on only one site: HTTP://dictionary.reference.com
Original comment by joefiesta@verizon.net
on 24 Jul 2009 at 1:24
I should add that it doesn't actually happen on that page. After going to
dictionary.reference.com, enter a word to be looked up in the dictionary.
Then, from
the page to which you are taken you should find that you can re-create the
problem.
Original comment by joefiesta@verizon.net
on 24 Jul 2009 at 2:48
I should also add that I use the NOSCRIPT addon (1.9.6.9) and dissallow scripts
to
run at REFERENCE.COM.
Hmm, more info. If I allow scripts to run at REFERENCE.COM, the problem
disappears.
I presume, then, that disabling the NOSCRIPT addon should make the problem disappear
as well.
Original comment by joefiesta@verizon.net
on 24 Jul 2009 at 2:58
Thanks for your feedback!
But even if I run the same NOSCRIPT configuration I could not reproduce the
error :-(
I think I will add a remark under my Known Issues section that there could be
side
effects with noscript
Original comment by Rudolf....@gmail.com
on 2 Sep 2009 at 7:52
Hello. I have just discovered that I can no longer re-create this behavior at
dictionary.com. They are constantly changing their web site, and I strongly
suspect now that the problem was the result of something they were doing.
Please close this issue. I have other (new) issues with Dictionary.com but (1)
I am not sure they are caused by MLB and (2) not sure they are worth reporting.
Should I change my mind, I will open a new ticket.
Thank you.
Original comment by joefiesta@verizon.net
on 2 Jun 2011 at 1:03
Original comment by Rudolf....@gmail.com
on 9 Jun 2011 at 7:51
Original issue reported on code.google.com by
joefiesta@verizon.net
on 11 Jul 2009 at 2:00