RapidSpell popup box getting access denied - RapidSpell Web ASP.NET - Forum

Have you noticed it being specific to a particular browser?

Sorry I didn't answer your question explicitly: "Is there an IIS setup or user profile setting I need to look at?"

There isn't, the problem is client side.

Do the machines where this is happening have any popup blockers installed? Usually popup blockers are OK because they allow popups called directly from a user event like a button click. But, I'd look there first.

Another option, if you're using v5 is to use a jQuery UI based dialog instead of a popup window. See "Using jQuery UI...." https://keyoti.com/produ...mples/JSmode/Dialog.htm

One thing about that though is it only applies if you use our Javascript based usage, it's not possible from the older Server Control based usage.

One other thing, are you doing anything across domains, i.e. the page with the textbox is one one domain and the spell checker popup is loading from a different domain/subdomain?

Do you see any other messages in the JS console?

Fair question, but like a lot of things involving computers - it doesn't always make sense (by which I mean, they do things they're not supposed to do). Just seems like blockers would be a good place to start.

The popup is definitely closed between spell check launching, right?

Which version of RapidSpell are you using?

Thanks
Jim

Here's my view of the situation which I intend as guidance on what to do next;

-You have some client machines with this problem (I don't know if they're all accessing the same web app.)

-There aren't any settings that we know of that affect this issue.

-We can dig in and try to figure out what the problem is, and it could be a) some config issue on those machines (eg this) or b) it's something in our code that could be fixed, but....

-You're using a version we don't support anymore (in terms of patches etc) (so 'b' above is a dead end)

-However, you're entitled to at least v3.8 https://keyoti.com/downl...-NET-3-8-0-Setup-UD.msi which might have it already fixed.

-If you have maintenance you can upgrade to v5 for free, otherwise you could trial v5 and purchase an upgrade if it fixes the problem.


So yes it is puzzling that most IE's work, but just some clients don't. In theory they should all work the same, but Windows is complex, and even if you can point the finger at a specific issue with IE, you probably can't resolve that since your clients are using old versions of IE (I assume since you're using an old version of our software that didn't support IE11).

Jim