Windows 8 OutputPanel behavior - hyperlinks not opening
I recently picked up a new Windows 8 machine. Running some of my scripts on the new box, I have observed that any hyperlinks that I dump to the outputpanel do not open the links when I click on them. In particular, I am seeing this occur with file:// links. If I export the OutputPanel results to a html file and open that file in a browser, the links open fine. I suspect some sort of UAC limitation, but I'll be darned if I can locate a setting. Anyone see this behavior too?
this script exhibits the behavior
void Main()
{
Util.RawHtml("http link to LINQPad.net works from outputpanel").Dump();
Util.RawHtml(@"file link to C:\Users does not work from outputpanel").Dump();
}
this script exhibits the behavior
void Main()
{
Util.RawHtml("http link to LINQPad.net works from outputpanel").Dump();
Util.RawHtml(@"file link to C:\Users does not work from outputpanel").Dump();
}
Comments
Also noticed that Util.RawHtml takes my href=file:// and emits href:file:///
Adds a forward slash.
Also... updated to latest beta.. same behavior (v 4.43.05)
I KNOW this behavior did not occur back then. Further, I am using scripts that have been unchanged since then as well.
This would seem to further support my assertion.suspicion that this is an environment issue... some update to IE or something.
In order for this workaround to work... I would need to automate the saving to html step... so I need to get a hold of the results html that is dumped to the outputpanel. Is there a way I can do that?
Good news is that I am able to reproduce the behavior in a design environment. As I have only VS2012 installed on my new machine, I am using the later version of the WebBrowser control. In this newer version, the DocumentStream property is no longer available. However, there is a NavigateToStream method that takes the stream as an argument.
That is a start. I will try some things and will be sure to post new information if/when I come across something.
HACK : alter the URI specified by the file:// links.
instead of file://c:/whatever
make it file://127.0.0.1/c$/whatever
With regard to this vexing issue... my to do list top item currently has investigating this as the root cause...... security based settings.... http://technet.microsoft.com/en-us/library/cc782928.aspx
If anyone that is already familiar with this lockdown stuff can pipe in here with some guidance... that would be wonderful.