Hot answers tagged internet-explorer
6
I've fixed it, or at least worked around it in a way that seems to solve all of our issues. When I added PDF icon support to our server, I used the following XML in the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\XML\DOCICON.XML file, as suggested in the linked KB article:
<Mapping Key="pdf" Value="pdficon.gif" /> ...
5
This seems to be a problem with the SharePoint client-side code, possibly as a result of changes to support branding. I have also seen it when trying to save a page I have edited. Your choices are:
1) Set your browser to use IE8 standards - you can do this by using F12 to get the IE developer tools panel and setting Document Mode to IE8 standards in the ...
4
This is caused by the installation of KB977724 when Office 2007 applications are also installed on the machine. There are further details about this problem on the Office Sustained Engineering site.
A hotfix to this hotfix can be downloaded from Microsoft Download Center.
3
First off, you can use $().SPServices.SPGetQueryString rather than rolling your own Query String parser. Secondly, you should be able to just set the simple select and not worry about the hidden complex select. The $().SPServices.SPComplexToSimpleDropdown function takes care of updating the complex select under the covers. Finally, you shouldn't need any ...
3
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:
RTE_DD_GetMenuFrame()
...
3
There are some known issues with IE9 and SharePoint 2007's JavaScript, etc. You might set the IE Compatibility Mode meta tag in the master page so that it forces IE 9 to render in IE 7 or 8 mode:
i.e: < meta http-equiv="X-UA-Compatible" content="IE=7" / >
http://msdn.microsoft.com/en-us/library/cc288325(v=VS.85).aspx
3
This is a notorious and well-known issue in SharePoint.
Background
Let me explain why it happens: SharePoint is a Microsoft product, as is Internet Explorer, and it's quite a customary thing when some features work in IE but don't work in other browsers. Other browsers always were and still are "partially supported" by SharePoint.
This is what happens ...
2
Publishing sites in display mode should work in IE6. The problem is with the editing controls, ribbon, etc. which won't work properly.
If you are still seeing problems with specific controls not looking quite right, you could use Control Adapters to target IE6 and modify the rendered HTML to work around any IE quirks. Generally, for publishing sites, you ...
2
I saw two good posts about this earlier in the year:
http://blogs.msdn.com/b/maximeb/archive/2010/04/01/what-sharepoint-2010-looks-like-with-internet-explorer-6.aspx
http://blogs.msdn.com/b/maximeb/archive/2010/07/30/what-can-work-with-internet-explorer-6-and-sharepoint-2010.aspx
Tags will work, but there is so much other stufff that doesn't that it makes ...
2
IE6 is not supported as an authoring browser in SP2010.
Read more on the support levels for browsers on TechNet
http://technet.microsoft.com/en-us/library/cc263526(office.14).aspx
Just saw Randy Drisgill did a nice post on this subject as well: http://blog.drisgill.com/2009/11/sp2010-branding-tip-5-handling.html
2
@DJ Monzyk
this is a follow up javascript file as reference in previous answer
function RTE_DD_GetMenuFrame()
{
var ifmMenu=null;
var elemMenu=RTE_DD_GetMenuElement();
if (null !=elemMenu)
{
if (document.frames.length > 0)
{
ifmMenu=document.frames[g_strRTETextEditorPullDownMenuID];
}
else
...
1
If fonts aren't increasing in size, then you'll need to redefine the CSS for your site to use em as units for font size, rather than explicit pixel/point font sizes.
Here's a post about the different font size units in use today:
http://kyleschaeffer.com/best-practices/css-font-size-em-vs-px-vs-pt-vs/
1
This issue was caused by the user launching Internet Explorer x64. Initially I was unable to figure out why the Visio document was being opened inside the browser. When I selected the document actions menu and selected "Edit in Microsoft Visio" I received an error
"'Edit Document' Requires a Windows SharePoint Services-compatible
application and ...
1
I still dont know what the exact cause of the problem is but I was able to get around it by doing the following:
Add a hidden iframe to the page:
<iframe id="emailiframe" src="" style="display:none;"></iframe>
In the content editor web part that contains my "feedback" link, I set the source to:
<script type="text/javascript">
function ...
1
Alternatively, it can also be a problem with permissions on the image/picture library from which the image is called. These are the following things you need to check
Permissions applied on the image and its checked out status.
Permissions of the picture library with respect to the users facing the problem.
Incase the image is located outside SharePoint, ...
1
You'll need to drop a small favicon.ico file at the root of your web application within IIS (next to the web.config) or edit the master page to link to your custom file if it's host somewhere else.
A good tutorial on this can be found here : http://blog.tedpattison.net/Lists/Posts/Post.aspx?ID=8
1
Currently, IE 10 (release preview) is not supported in SP 2010.
In the meantime, try this. Press F12, to bring up the developer tools. In the Script tab, debug ewamoss.js file to see why you are getting a null reference.
Supported browsers
1
SharePoint does this by default. You can, however, override the page title with jQuery: http://www.sharepointjohn.com/sharepoint-2007-jquery-to-fix-ugly-page-titles/
You could use this solution to create a custom page head control that includes your JavaScript to override the page title: ...
1
You don't have async: false, on the first SPServices call to get the sites, so IE is probably just behaving as expected and continues to make the new requests without anything entered into subSites.
I don't know why FF fails to run the request async, but that just shows you shouldn't use that if you want right behaviour
1
Well... its your custom branding.
Both of these buttons rely on onclick events executing javascript so its likely something is causing a javascript error on the page.
It could be that this error is happening before the click actually happens (i.e. page/modal load) so don't just look at the javascript that happens after the click.
Use IE developer toolbar ...
1
If you wanted to continue to use IE6 as the client browser then you will probably have to write your own rendering for all of the OOTB web parts which produced non IE6 compatible code.
In terms of a business case for rolling out IE7/8 then this should be a no-brainer as the time taken to write and test your own implementations of all the OOTB web parts, ...
1
This is probably related to ActiveX control or scripts that is not allowed to run doe to your security settings.
You can add your website to the trusted sites list to mitigate this problem.
More info:
http://windows.microsoft.com/en-us/windows-vista/Internet-Explorer-8-Information-bar-frequently-asked-questions
hth
Anders Rask
1
What's the managed path the site is using? We had issues with this when we had a slash (/) in the managed path. I posted on my blog explaining this issue and how I got to that conclusion. http://www.thelineberrys.com/default-category/explorer-view-not-working-and-managed-paths-3.html
If you follow similar steps in your troubleshooting as I did on my blog ...
1
I have experienced and fixed this same problem in the past by installing the February 2010 Cumulative Update:
Windows SharePoint Services 3.0 Cumulative Update Server Hotfix Package (WSS server-package)
Office SharePoint Server 2007 Cumulative Update server hotfix package (MOSS server-package)
Further information:
Rich Finn: Issue With People Picker ...
1
IE9 is not an officially supported browser for SharePoint 2007 according to the Browser Support (Office SharePoint Server) documentation.
You can force the downstream compatibility by adding a META tag to your master page(s). See Defining Document Compatibility for further detail.
<meta http-equiv="X-UA-Compatible" content="IE=7">
As an ...
1
A Couple of things you can try:
In internet explorer, uncheck the "Enable Integrated Windows
Authentication" box in the security options page.
This doesn't actually disable it, it just forces NTLM. When the
checkbox is clicked it will try to use Kerberos first, than it is
supposed to fall back to NTLM (IE7+).
I would also suggest loading up fiddler and ...
1
The way i made it work when after enabling WebClient and adding to trusted website the "explorer" feature was still not working, was very simple. The issue is in IE9 64-bit, Windows does not allow you to download it from the website but installs it automatically when you install 64-bit version. So the only thing you need to do is to go to start menu and just ...
1
In my case, the step that was missing was to add the website to my list of trusted sites in Internet Explorer. That takes the list of pre-requisites to:
Enable the WebClient service in Windows (if you're using a Windows Server environment, you need to enable the Desktop Experience feature of Windows Server)
Add the website to the Trusted Sites list in ...
Only top voted, non community-wiki answers of a minimum length are eligible
