Problems with Tripadvisor

[imajica]

I have been having problems with Tripadvisor lately. I found this topic: https://forums.informaction.com/viewtop ... 672#p88672 that talks about it with a fix. However, for me it does nothing. I have to disable the XSS function for tripadvisor to work properly. I am running FF 55.0.3 and NoScript v5.0.9

Any ideas on how to get TA to work properly without disabling XSS

Thanks

[barbaz]

Please check the Browser Console (Ctrl-Shift-J) when this issue happens and post here any messages related to NoScript.
(related messages usually start with either "[NoScript" or "[ABE]"; if you don't know what's related, turn off CSS warnings and post everything else you see)

[imajica]

This is what i get when i load: https://www.tripadvisor.ca/Hotel_Review ... tionId=101

The image will load, but FF freezes and takes about 1-2 minutes before it is usable. If i disable XSS then it works perfectly

I am trying to post the log, but when i hit submit i get a message saying something i am trying to post is triggering the anti spam.

[barbaz]

I checked the link, and I see the same behavior as you. The workaround from the other thread does not stop the problem.

After applying the workaround in the other thread, I saw nothing related in the Browser Console (Ctrl-Shift-J).

However, I was able to work around the problem. The following steps assume you have *not* applied the workaround from the other thread. If you did apply the other workaround, just adjust what you already added to match the values below.

So, instead of using the workaround in the other thread, try this -

1) NoScript Options > Advanced > ABE > USER, add

Code: Select all

Site .bluekai.com tpc.googlesyndication.com s.pinimg.com
Deny

2) NoScript Options > Advanced > XSS, add these exceptions

Code: Select all

^https?://tags\.bluekai\.com/
^https?://tpc\.googlesyndication\.com/
^https?://static\.tacdn\.com/.*_moniker/

Does it now work for you?

[imajica]

that seemed to do the trick.

Cool.. Many thanks!

[barbaz]

You're welcome!

Moving this thread to NoScript Development as a possible bug report.