You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Get https://github.com/akzhan/jwysiwyg (Wysiwyg plugin)
2. Created a plugin to include spell check
3. In IE, getting annoying secure dialog box.
What is the expected output? What do you see instead?
All the functionality works, I used fiddler and firebug to make sure there is
no call to http.
I removed spell check and annoying dialog is not seen. As soon as I put it
back, the annoying dialog comes up.
Here is what I have inside wysiwyg instantiation.
$(".rte").wysiwyg("addControl", "spellcheck", {
groupIndex: 11,
icon: '/scripts/images/spellcheck.png',
tooltip: 'Spell Check',
exec: function() {
$(this.editorDoc.body).spellchecker({
wordlist: {
action: "after", element: $(this.editor)}
}).spellchecker("check");
}
});
What version of the product are you using? On what operating system?
Latest
Please provide any additional information below.
I am using your spell check plugin in asp.net website, therefore, instead of
php page, I have ashx page that handles the spell checking from google. I
verified the google link, it goes to https site. So all look good there.
I repeat all the functionality works, the only issue I have is that annoying
dialog.
Thanks for looking into it.
Have a good day.
Original issue reported on code.google.com by soven...@gmail.com on 4 Mar 2011 at 6:34
The text was updated successfully, but these errors were encountered:
Never mind. This is actually issue with wysiwyg plugin, the way, custom
controls are written. Since I just directly injected spell check plugin into
wysiwyg source code and I don't get annoying box anymore.
I will bring this upto them.
Thank you and sorry if I wasted any of your time.
Awesome plugin, I must say. Kudos to you guys.
Original comment by soven...@gmail.com on 4 Mar 2011 at 7:14
Original issue reported on code.google.com by
soven...@gmail.com
on 4 Mar 2011 at 6:34The text was updated successfully, but these errors were encountered: