it is using web-based protocol handlers to open the file directly in word.
That's something that exists from a while now, for example, in ubuntu, you can create an html link like this to download a packet :
<a href="apt:wine" title="Get Wine">Wine</a>
The one used to open Microsoft Word is :
I've confirmed this link is a solution: http://kyleschaeffer.com/sharepoint/sharepoint-2010-scrolling/
Our scrollbar always works, scripting doesn't break, and we haven't seen any negative side effects!
Actually, you can set it up so that you can use the Rich Text in IE9 (some people believe you have to disable it completely)! You just have to override 3 functions in form.js (I created a file called form.ie9fix.js) and make sure it loads AFTER the "normal" form.js (or form.debug.js, whichever).
The functions in question:
While it's not an "official" post, the Microsoft blog, along with several other posts does state that Chrome is supported post-SP1, along with IE9 in IE8 standards mode. The addition of Chrome support in Service Pack 1 includes both SharePoint and Office Web Apps.
I have seen this issue in both vanilla environments, as well as those with some pretty extreme ...
An out of the box approach is to open the document library in Windows Explorer (Actions -> Open with Windows Explorer) select the desired files and right click on them. Then select the print option from the right click menu.
A good description on the browser support is here. Basically SP 2010 supports IE 7+ with 32 Bit and limited support on 64 bit.
Also another things is that default SharePoint master page sets the document mode to IE 8 Compatible. So even you upgrade the browser, it will work on IE 8 Compatible document mode.
It can be set with following code.
You didn't say what environment you're using, but IE 8 is not supported in Office 365:
We are testing the same thing in our farm as well. we decide to turn on the Enterprise mode(EMIE). there are many things which are not working with IE 11 in native mode.
datasheet view will not work with IE 11
trying to edit the page but it fails
certain webpart properties can not modified.
Workflow having the issue
I would also recommend you to upgrade ...
SP2 provided support for IE10. Since you're rolling out IE11, rather than placing the site in Compatibility View, try IE11's Enterprise Mode: http://blogs.msdn.com/b/ie/archive/2014/04/02/stay-up-to-date-with-enterprise-mode-for-internet-explorer-11.aspx
their is no dedicated browser for the SharePoint rather they call it supported. As per my experience best browser is always IE.
If you follow this Official documentation they mentioned Microsoft Edge, Internet Explorer 11, Internet Explorer 10, Internet Explorer 9, Internet Explorer 8 but with certain limitation with IE 11 in Edge Mode as well as Edge ...
npOpenDocuments (formerly WSSFirefox) implements SharePoint & Office integration for non-IE browsers. Now Firefox & Google Chrome browsers can open MS Office documents directly, without saving them into temporary folder first. Check-in, Check-out & co are also supported.
This works for Office 2007/2010 & ...
Perhaps you've already solved this and moved on, but since I ended up here when searching for a solution and didn't find it, I better add my solution:
A customer had exactly the same problem and the reason for it was that the customer is using a Language Pack (Swedish) on the site.
Solution: Go to the user menu (upper right corner) and switch to English. ...
Please refer following link for Browser support in SharePoint 2010, specifically refer for Mozile which says drag and drop web part feature is not supported.
hope this helps.
Do you get the same behaviour if you edit from the browser rather than SharePoint designer?
If not, I'd guess you've got SharePoint designer set to something other than utf-8 as the charset.
You can change it by going to (in Designer 2010) File > General > Page Editor Options > Default Fonts.
Pick Unicode (UTF-8).
if (null !=elemMenu)
if (document.frames.length > 0)
you have two methods! first i would try the ...
Got the answer by testing workarounds.
Just I need to write some lines of code in the OnInit() method of form.
ScriptManager sm = ScriptManager.GetCurrent(this.Page);
if (sm != null)
sm.EnablePartialRendering = false;
Anything for ScripManger cannot be changed ...
You can use ConditionalExpression property to specify your conditional browser version.
<SharePoint:CSSRegistration name="/_layouts/solutionfolder/filename.css" After="corev4.css" ConditionalExpression="lt IE 7" runat="server" />
Yes, but it depends on how you set up the environment. If the Hyper-V VM has full network access (that is, you can ping it from your client), and if you set up your Web Application to use the machine name of the VM, you can just go to http://machineName. Or, if you set up a specific hostname that is not the machine name, or a full FQDN, you can edit the ...
For chrome the variable name is different, so following should help:
var key = e.charCode ? e.charCode : e.keyCode ? e.keyCode : 0;
if(key == 13)
e.charCode is used in Chrome
I dont think you will find any browser that works best because from my experience each browser has some shortcomings when it comes to SharePoint.
If you try "Open with Explorer" in Edge it won't work there as well.
You can't force browsers to support features that aren't available. There are a lot of things that are reliant on ActiveX controls rather than ...
Like others have pointed out there is no great browser experience for SharePoint On-Prem but IE unfortunately is the best with the most OOB functionality.
You can also use chrome and use a chrome extension called IE Tab which can add a lot of the functions you lose when using Chrome vs IE. It does tend to be finicky every once in awhile but from its ...
The best browser choice really depends on the work that you want to achieve in SharePoint.
Internet explorer is really good if you want to play around with OOTB features , configure web parts but again asy friend mentioned pages will load ...
Setting it to IE=edge wouldn't fix your IE9 issues. It should be falling back to IE9 mode automatically since it's set to IE=10. Are you sure there isn't an issue in your CSS for IE9 rendering? box-shadow does work in IE9, we have it one one of our sites (in 2010 and IE9 rendering).
You can press F12 to bring up the developer tools and then try changing both the Browser Mode and Document Mode.
In particular, try changing the browser mode to Internet Explorer 10 Compatibility View and the document mode to Internet Explorer 8 standards.
For more information see this link