Home > front end >  Js to compatibility mode to open the web page
Js to compatibility mode to open the web page

Time:12-25

 
<meta HTTP - equiv="X - UA - Compatible" content="IE=11; IE=10; IE=9; IE=EDGE "/& gt;


<script>
The function openFileIIs (filename) {
Try {
Var obj=new ActiveXObject (" wscript. Shell ");
If (obj) {
Obj. Run (" \ "" + filename +" \ "", 1, false);
Obj=null;
}
}
The catch (e) {
Alert (" please determine whether there is the drive letter or file ");
}

}
OpenFileIIs (" F: \ \ fk1 - FK INFOS \ \ INF Application. The Web \ \ ExcelPrinterTemplate \ \ finished qr code. BTW ");
</script>

Asp.net to open the client demand is another bartender file, use js must be compatibility mode, just want to click on the print button, open a new window is compatibility mode and then open the file, but how the default page is compatible mode, and online content="IE=11; IE=10; IE=9; IE=EDGE "didn't work

CodePudding user response:

This should be the Intranet users, suggest change implementation scheme, sign up for a deal, awakens the program over the web,

Similar to QQ, WeChat, ali prosperous, through the web, and specify user chat after wake up...

CodePudding user response:

The
Hello World, 1/f, reference response:

Can I create a bartender. Reg, content is as follows:
The Windows Registry Editor Version 5.00//Registry tools Version information
[HKEY_CLASSES_ROOT \ bartender]
@="bartender"//agreement with the name of the
"URL Protocol"="C: \ \ Program Files \ \ Seagull (x86) \ \ BarTender Suite \ \ bartend exe"//but the path of the application, can only be exe Program
[HKEY_CLASSES_ROOT \ bartender \ DefaultIcon]
@="C: \ \ Program Files \ \ Seagull (x86) \ \ BarTender Suite \ \ bartend exe, 1"
[HKEY_CLASSES_ROOT \ bartender \ shell]
@="open"
[HKEY_CLASSES_ROOT \ bartender \ shell \ open]
@="open"
[HKEY_CLASSES_ROOT \ bartender, shell, the open and the command]
@="" C: \ \ Program Files \ \ Seagull \ \ (x86) BarTender Suite \ \ bartend exe \ "" % 1 \ ""//the application path, parameters of % 1
Bartender: in CMD didn't open is what's the problem

CodePudding user response:

This part after import agreement didn't see, you can manually editing the registry, after successfully exported to other machine use,

Or try WebRunLocal
  • Related