Has anyone had any problems recently with a page that contains a tab rendering really slow? It's only with IE and just started happening out of the blue maybe a few weeks ago. The only way to get around it was to add the web site to the Trusted Sites list. Without it added, a page could take a few minutes to load where it use to take a second.it works fine in Firefox and I even created a new site with a page that just contains just an empty tab. The page takes a 15 seconds for it to load.
Don't know if some MS security update has broken something...but it happens on every PC in my office.
Bob
Well...the problem has to do with Nortons Anti-Phishing. Turn it off and eveything works fine. God only knows why it's slowing only the pages with a tab control in them
Have there been any updates since October on this issue:
Ultrawebtab 8.3.20083.1009 on IE 7 with Norton IS version 15 Phishing Protection.
With phishing protection on, it takes 12-15 seconds to render a webtab with minimal tabs and no content in the panels. With phishing protection on it takes, say, half a second.
I don't think demanding our users turn phishing protection off is a viable option.
And the solution is:
The DummyTargetURL property of the webtab, which feeds the webtab's iframes. The default property "BLOCKED SCRIPT''" creates this attribute tag: src="BLOCKED SCRIPT''". Delete the attribute or put in a reference to a local file and all is well.
I set DummyTargetURL to ''. You have to use the single quotes. If you just empty it, it reverts to default.
I don't yet know if this will have an impact of webtab functionality - I suspect it won't but have asked Ifragistics support for a ruling on the question.
This also explained why every infragistics.com page with a tab interface was painfully slow to load. A quick source check found the same attribute value. My guess is that there a lot of webtab endusers out there with IE7 and Norton who experience the same - Ifragistics should probably take note and change the default (and the property on their site's pages).
Hi,
Thanks for this solution, it was driving me crazy for a while.
I do have one suggestion for this solution. I was experiencing a strange issue when I set the DummyTargetURL to ''; I would see a Page Not Found flash across my tab when I first clicked on it, then it would load the appropriate page. If I changed DummyTargetURL to be about:blank (which renders a blank webpage) the Page Not Found message disappeared.
I don't know if anyone else had this strange symptom for the above solution, but if you did, I think this might help resolve it.
Again, thanks.
Mark