Improvements in Web Browser Compatibility

SharePoint's New Version Improves Web Browser Compatibility

OpsanBlog — Wed, 19 Jul 2006 23:49:46 GMT

Sharepoint 2007 + Firefox = No rich editing

Kevin Dente's PuppiesAndIceCreamBlog — Thu, 20 Jul 2006 00:19:04 GMT

Wow, talk about perfect timing. I was just about to complai&hellip;er&hellip;blog about this, and one

Browser support in WSS v3

Portals — Thu, 20 Jul 2006 09:29:53 GMT

re: Improvements in Web Browser Compatibility

Ben Skelton — Thu, 20 Jul 2006 11:03:20 GMT

Will features be trimmed for each browser? For example - no point showing "Explorer View" or anything like that for someone that is using Safari or Firefox. It is just distracting to see features that launch a dialog saying that "the functionality isn't supported in your browser". Doesn't make the peeps happy!

Also - glad to see you guys are allowing Firefox and Safari users to input HTML. Although not a perfect solution it is much better than the warning message we received before. Hopefully we will get true rich-text editing for these browsers at the same time you improve the control to output XHTML compliant code :)

SharePoint 2007 und Browserkompatibilität

SharePoint, SharePoint and stuff — Thu, 20 Jul 2006 12:06:40 GMT

Troy Starr aus dem SharePoint-Team gibt eine Übersicht, welche Browser in der neuen Version SharePoint...

re: Improvements in Web Browser Compatibility

jeffyjones — Thu, 20 Jul 2006 17:04:19 GMT

So you still make Firefox a second-class browser? That's lame. Come on... research your actual audience, not the world at large. I can promise you more of them use Firefox. And besides, things like rich text editing and everything AJAX have been solved to work in both IE and Firefox.

re: Improvements in Web Browser Compatibility

davidacoder — Thu, 20 Jul 2006 17:46:20 GMT

You must then be the first and only company that seriously attempts to sell internet facing blog and wiki software that doesn't fully support Firefox. Good luck.

re: Improvements in Web Browser Compatibility

Thu, 20 Jul 2006 17:58:24 GMT

Please oh please give us a good reason why firefox is a Level 2 browser in this day and age!

Tech Talk PT » Blog Archive » Improvements in Web Browser Compatibility

Tech Talk PT » Blog Archive » Improvements in Web Browser Compatibility — Thu, 20 Jul 2006 19:20:34 GMT

PingBack from http://techtalkpt.wordpress.com/2006/07/20/improvements-in-web-browser-compatibility/

re: Improvements in Web Browser Compatibility

Estyn — Thu, 20 Jul 2006 20:54:07 GMT

Lack of support for firefox and the richtext editor must be a business decision and not a technical decision. There are plenty of cross-browser rich text editors available both comercially and freely.

We had the same problem with MCMS, luckliy microsoft paid for a license for the telerik control which worked without any active x controls. Why are they repeating the mistake again, now we will have to go through the hassel of installing a third party rich text editor again.

I can understand having the central admin pieces IE only, but you need to support the other browsers with a richtext editor and other basic functionlity that is available in many other solutions. Customers expect this functionality and many of them don't use IE.

re: Improvements in Web Browser Compatibility

Angus McDonald — Fri, 21 Jul 2006 10:04:39 GMT

So the 24% of Australia users that are on Firefox can go jump? Sounds like a plan to limit the adoption of SharePoint as a corporate tool.

Why, limit a paid server tool to your own free browser? You don't make a cent off people staying on IE, yet you insist that we all use it to access your expensive server apps!?

Microsoft's SharePoint treats FireFox as 2nd class citizen

ISerializable - Roy Osherove's Blog — Fri, 21 Jul 2006 14:20:47 GMT

Looks like the next version of SharePoint won&#39;t support FireFox fully.as Jeff mentiones: &quot;Every

re: Improvements in Web Browser Compatibility

dylan — Fri, 21 Jul 2006 22:25:01 GMT

I concur - there are some really great third party packages for cross-browser inline editors now. There's really no excuse to use activex junk. Even more important than the lack of cross-browser with activex, I've had clients who were on corporate networks where activex was disabled.

TinyMCE - easy as pie. You can even define the css classes available to work with. I understand that there are licensing issues with this sort of thing, but still... Having to tell my clients what browser they can use is really lame.

However, I am really really really excited about the new version of Sharepoint. This is something I've been looking forward to in the .net world for a long time now. Thanks for having at least some cross-browser support, and for making sharepoint viable as an internet portal!!

re: Improvements in Web Browser Compatibility

Troy Starr [MSFT] — Sat, 22 Jul 2006 20:58:03 GMT

Hi everyone, thanks for taking the time to give us your feedback! As I said before, I'm glad to see that there’s so much interest in our upcoming version and what browser support we will have. Let me jump right in and respond to your comments...

I see that many of you are disappointed that we won't provide a rich text toolbar for Level 2 browsers. I think it's safe to say that we're all disappointed about that - including the SharePoint team itself. We know that this is a very convenient feature to have, regardless of your browser. As I mentioned in the post, we've been in discussions with our customers ever since we started planning the new release, identifying what problems they're trying to solve and analyzing what parts of our previous releases have come up short. We've used that feedback to plan what we think will be the right mix of new features and improvements of existing features to make the new release very compelling. An example of this is support for creating file attachments to list items in Level 2 browsers. Customers told us that this was important functionality that we were missing in the current release and we listened by adding this support to Level 2 browsers. Since there's a finite amount of time in our schedule, some things such as the rich text toolbar didn't make it. (It's not so much a question of figuring out how to solve the problem - it's the time it takes to actually make the changes in the code, test them, fix bugs, etc.)

Another concern is that some browsers will have a downlevel experience in SharePoint. While true, I don't want people to interpret this as meaning that downlevel experience will be poor. Nothing could be further from the truth! If you use the Beta 2 build today with any of these browsers, I think you'll see a very high quality experience - better than we have in the current v2/2003 release. And as I mentioned, we've continued to improve that experience after the Beta 2 build - the Beta 2 Technical Refresh build should be even better.

Another question is why we make a distinction between Level 1 and Level 2 browsers, and what makes a browser fit in one category or the other. The biggest differentiator is support for ActiveX controls. We use ActiveX controls to improve the SharePoint experience in certain areas. For example, the ability to easily select multiple files to upload at one time and to edit list items in a datasheet view. These features are usually very difficult or impossible to implement with non-ActiveX technologies that are currently available. There are also other differentiators such as WebDAV support, which allows you to interact with your SharePoint site as if it were a network share that you've mounted.

Someone misunderstood this post to mean that SharePoint won't provide AJAX support in Level 2 browsers such as Firefox. Although I never mentioned AJAX, I'll take this opportunity to clear up any confusion here. SharePoint will use AJAX throughout the product and is supported in both Level 1 and Level 2 browsers. This includes our context menus, view filtering, etc.

Feature trimming based on browser is a tricky line to walk. For example, there may be a bug in a browser that causes feature x to fail, or browser y doesn't support a technology we need for a feature to work. So, we trim that feature from that browser. Then browser y fixes that bug or adds support for that technology, but can't access that feature because we've trimmed it. Unfortunately, we're then open to accusations of purposely crippling support of that feature in that browser. That said, we know that we can't always please everybody, so if there are specific features where we're not trimming and you'd like us to, please post a comment here to let us know. We'd love to hear from you.

Once again, thanks for sharing your feedback with us. I appreciate all of the comments you've made so far, both favorable and critical. I hope you'll continue to give us your feedback, which I'll be passing on to other members of our team to take into consideration for the v3/2007 release as well as the next release after that. I also hope you'll take this opportunity to install the Beta 2 build and try out our browser support firsthand.

re: Improvements in Web Browser Compatibility

ck — Sun, 23 Jul 2006 05:34:39 GMT

Please at least make the input forms like wiki etc... work before the final? There is no reason to make people use HTML!! Come on do right thing :)

re: Improvements in Web Browser Compatibility

Kevin Dente — Mon, 24 Jul 2006 00:47:39 GMT

Troy,
Thanks for the detailed response. I don't think anybody expects features that go beyond the capability of a browser (like multi-file upload), and therefore require ActiveX controls, to be supported on down-level browsers.

Rich-text editing, however, clearly does not fall into that category. Especially in regards to wiki's and blogs, rich editing is part of the core user experience. You've crippled those features for non-IE users. I suspect that you'll find the uptake for internet facing sites will be a disappoint for you because of that.

As for the resource argument - sorry, but that that's a tough sell. The wiki software that we use currently, Perspective, manages cross-browser rich editing, and is written by one guy as a pet project in his spare time. Microsoft is the largest software company in the world - I think you guys could have managed it.

BTW, generally I've found the Firefox support, outside of the richtext stuff, to be quite excellent in WSS 2007. That's part of why this editing mess is so disappointing.

Microsoft PacWest SharePoint Server Newsletter – July 2006

Owen Allen (MSFT PacWest) — Wed, 26 Jul 2006 09:05:25 GMT

Microsoft PacWest SharePoint Server Newsletter – July 2006

 Update on Download Availability of...

Cross-browser compatability in WSS/MOSS

Breaking Point Blog — Thu, 27 Jul 2006 13:48:12 GMT

From the Sharepoint product team blog an article setting out a compatability matrix for which bits of...

re: Improvements in Web Browser Compatibility

Stephen — Thu, 27 Jul 2006 21:37:25 GMT

First of all I have seen nothing in MOSS or WSS that "NEEDS" activeX to work. There are other ways of doing things in a more browser compatible format including multiple file uploads (Google has a really nice one in Gmail). Separating browsers into a "Microsoft" vs "Not-microsoft" world does not improve your browser support credability.

Secondly, realizing that you are using a DHTML control to create the HTML input, why not just disable the specific buttons that use the "IE only" functionality and offer a Feature to enable the simple DHTML editor in Firefox. If you aren't doing your DHTML editor base components in a browser compatible method, then change the control to use the proper browser compatible base control (i.e. div instead of iframe, etc). Otherwise you are forcing all of us internet developers to use a third party control (which I am sure Telerik will be more than happy to provide at a fee) and not even providing the same functionality that free Wiki and Blog software provide. A Wiki that doesn't support everyone is no Wiki at all.

re: Improvements in Web Browser Compatibility

Andrew Emmett — Mon, 31 Jul 2006 16:54:02 GMT

Forgive me for being blunt, but what the hell are you MS guys thinking. I honestly believe that there is something else at work here. Why on earth can you not provide cross-browser rich text editing. If it comes to it, just buy an effin control from a third party (or buy the third party). It's not like MS is strapped for cash! Come to think of it, what about the editor you are using on Live.com!! Its not a fully featured, but at least end users dont have to be able to write raw HTML! Don't get me wrong, WSS 3.0 is great, but I think you guys are sticking your head in the sand about this one. I astonishes me how you seem to think this is acceptable. I for one would be happy to wait an extra month or two for this feature.

re: Improvements in Web Browser Compatibility

Girish J Bhatia — Thu, 10 Aug 2006 03:01:31 GMT

Not to say much, but Troy has proved his point here that he cannot satisfy the Majority as it affects one Tag or the other. E.g. To every action there is an equal and opposite reaction. If Troy tries to introduce Cross-browser rich text editing there will be lot of ManHours spent which i feel is useless b'coz when a browser is already available which does the same functionality then why?

Secondly MOSS2007 is already is in its Beta 2 and now the time has come for RTM which where one cannot make 100 changes for the cross-browser rich text editing feature for that too another browser and then test it and over and above affects other features etc...

Girish J Bhatia [MSFT]
SharePoint Lover

re: Improvements in Web Browser Compatibility

RLConsulting — Fri, 11 Aug 2006 03:27:06 GMT

Hello,

I would appreciate your feedback on the following "bug" I've noticed when browsing a MOSS 2007 Picture Library (http://www.miraclecorners.com/Pictures%20Gallery/Forms/AllItems.aspx):

1. When browsing with IE 6.0.3790.1830 (on Windows 2003), the browser simply stalls and the iexplorer.exe process has to be shut with Task Manager
2. When browsing with Firefox 1.5.0.3 on the same W2K3 box, it works like a charm

It seems strange to me that MS products fail at browing SharePoint data when not-MS product succeed...

re: Improvements in Web Browser Compatibility

dylan — Tue, 22 Aug 2006 20:54:02 GMT

Just curious - you mention that the content editor will use activex. This is an issue I'm currently dealing with for one of our clients. They are on a hospital network that disables activex. Will 2007 continue to be unusable by them? This is a pretty major problem for us, since most of our clients will be using this same network. We can't expect them to know html.

re: Improvements in Web Browser Compatibility

Suzanne Oliver — Wed, 20 Sep 2006 00:05:30 GMT

Where can I get information on compatibility with versions of Windows and Office? I have a client who is considering deploying their Intranet on MOSS but they have users from many different offices using varying versions of Office and Windows

SharePoint en Firefox | KennethVerburg.nl - Information Engineer in het Wild

SharePoint en Firefox | KennethVerburg.nl - Information Engineer in het Wild — Thu, 21 Sep 2006 16:25:29 GMT

PingBack from http://www.kennethverburg.nl/2006/09/20/sharepoint-en-firefox/

WSS 3.0 in... Camino!?

The Alistair Speirs blog - SharePoint, MOSS 2007 and .NET notes from the field — Mon, 02 Oct 2006 14:33:37 GMT

Well, news this week is that IBM regards mac as a 'resurgent platform' and will improve Lotus Notes support...

re: Improvements in Web Browser Compatibility

Anon — Mon, 09 Oct 2006 00:43:47 GMT

Please give us a rich-text editor that works in browsers other than IE! SharePoint even has some of the Linux gurus I know very impressed, but lack of rich-text editing (especially in the Wiki) remains a constant embrassment. If some free forum and CMS solutions can manage a cross-browser rich text editor, I'm sure a company with resources like MS can come up with something similar. That's all I ask! :)

re: Improvements in Web Browser Compatibility

Wilbur Harvey — Wed, 18 Oct 2006 00:37:51 GMT

Sharepoint is pretty useless when trying to use it from Linux or Mac. Many of us are trying to get sharepoint removed from our company for that reason.

re: Improvements in Web Browser Compatibility

Shafieda — Wed, 18 Oct 2006 12:58:36 GMT

Hi,

I'm doing some research for a client. We are considering to advise SharePoint 2007 for their new intranetsite.

Where can i find more information about webbrowsers compatibility (other than the ones mentioned)? I'm especially trying to figure out if SharePoint Server 2007 cross browser support supports different Macintosh webbrowsers:

Camino, iCab, OmniWeb , Safari, Shiira, SunriseBrowser, Flock, Lynxlet, Mozilla, Netscape, Opera, SeaMonkey, WaMCom, WannaBe.

And what about a Macintosh that has MS Windows XP as OS?

And does SharePoint Server 2007 also supports other Microsoft webbrowsers (AtomNetPE, AvantBrowser..) besides Internet Explorer 6.0+?

Regards,

Shafieda Kallan

SharePoint Server 2007 の対応ブラウザ

SharePoint & .NET Techブログ — Tue, 24 Oct 2006 07:04:36 GMT

SharePoint Server 2007の対応ブラウザに関する正式なドキュメントを見たことはないですが、SharePoint Team Blogに、この件に関する投稿があり、そこに対応ブラウザについて書いてました。

re: Improvements in Web Browser Compatibility

David Ramsay — Fri, 27 Oct 2006 23:31:11 GMT

You state - An example of this is support for creating file attachments to list items in Level 2 browsers - in improvements, does this mean you accpet that there is a problem in current version of WSS?

If so why don't you patch in a fix because this is causing real problems!!!

Web 2.0 Browser Unterst??tzung bei Microsoft « PrivatesPortal

Web 2.0 Browser Unterst??tzung bei Microsoft « PrivatesPortal — Sun, 29 Oct 2006 20:40:43 GMT

PingBack from http://portaleco.wordpress.com/2006/10/29/web-20-browser-unterstutzung-bei-microsoft/

Cross-browser authoring

Microsoft SharePoint Products and Technologies Team Blog — Wed, 15 Nov 2006 01:33:53 GMT

One of the most popular blog entries was the web browser compatibility one where folks were very vocal

Cross-browser authoring

Arpan Shah's Blog — Wed, 15 Nov 2006 03:21:10 GMT

[I cross-posted this on http://blogs.msdn.com/sharepoint as well] One of the most popular blog entries

SharePoint: Cross-browser authoring

Dan on eScience & Technical Computing @ Microsoft — Wed, 15 Nov 2006 08:48:03 GMT

How timely this post is...at SC06 I was just having a discussion with someone (who would like to remain

SharePoint: Cross-browser authoring

eScience @ Microsoft — Wed, 15 Nov 2006 08:48:03 GMT

How timely this post is...at SC06 I was just having a discussion with someone (who would like to remain

re: Improvements in Web Browser Compatibility

Tim — Tue, 19 Dec 2006 08:03:00 GMT

The lack of "Rich Text" toolbar or editing will be a key limitation for not recommending Sharepoint based solution for my education institution customers as they will continuously have considerable Mac and Linux seats.

re: Improvements in Web Browser Compatibility

LLiu — Wed, 20 Dec 2006 11:52:40 GMT

Tim, please read about our resolution to the web browser compatibility issue at http://blogs.msdn.com/sharepoint/archive/2006/11/14/cross-browser-authoring.aspx.

re: Improvements in Web Browser Compatibility

Gavin Guinane — Fri, 12 Jan 2007 18:45:34 GMT

Any ideas if Mozilla 1.7 will be supported on Linux?

List of MOSS 2007 ActiveX controls (created searching the visible code)

Jose Barreto — Tue, 27 Mar 2007 01:15:59 GMT

List of MOSS 2007 ActiveX controls (created searching the visible code). I was looking for a list for all ActiveX controls used by Microsoft Office SharePoint Server (MOSS) 2007, but it seems like this list is not available at this time...

re: Improvements in Web Browser Compatibility

John — Sun, 08 Apr 2007 22:18:41 GMT

Please wake up! I work for a large ISV and:

a) Most of our customers block ActiveX controls by policy.

b) ALL of our customers have at least a few senior executives using another browser than IE.

c) We just discarted MS CRM since it works only with IE. In fact, I was shocked to learn that the next version still supports only IE.

d) we stopped using/integrating with sharepoint because of complaints from our own customers. Management aaked us to find a "more standard solution that works correctly across browsers"

PS: and in the same breath MS joins the OpenAJAX Alliance...

re: Improvements in Web Browser Compatibility

dave warnes — Thu, 12 Apr 2007 19:04:25 GMT

I've been using the newest beta version with both internet explorer 6 and 7. One odd quirk that I have come across is that in IE7, when attempting to view documents in a library in the explorer view, nothing shows on the screen. It's as if it doesn't see any documents. However, that issue is not present in IE6.

re: Improvements in Web Browser Compatibility

bpropes — Tue, 24 Apr 2007 23:19:00 GMT

I'm having some issues with some clients in Canada, that when trying to access the documents in Edit View (Explorer View) get the following error: "Your client does not support opening this list with Windows Explorer. "

Is there any known workaround for this? I've Googled like crazy and had zero luck and the so-called KNowledge Base article on MSDN gives two reasons, neither of which is the problem!

Is this a browser issue? ActiveX problem? DLL corruption or registry error?

If anyone can shed light on this please reply!

Thanks!

re: Improvements in Web Browser Compatibility

Afzel Alihoessein — Sat, 28 Apr 2007 11:44:49 GMT

Yes You Can Try It!.

SharePoint 2007 for

I Know That The Systeem Will Work .

Just Read To Instuctions On You Screen.!

re: Improvements in Web Browser Compatibility

Matt — Mon, 21 May 2007 16:21:52 GMT

I'm not sure if this is the right area to post but im having some trouble with explorer view... and im not sure if it has to do with browser compatibility or vista. i'm leaning towards vista though. anyway heres my issue:

When trying to switch to explorer view within a document library I receive multiple logon prompts and eventually an error within internet explorer that

says page cannot be displayed. I receive this same error when I try to cancel the logon prompt as well.

Currently I am running windows vista enterprise with IE 7 and our SharePoint server is running WSS version 3.

So far I have tried the registry hack to allow basic authentication, I have restarted and confirmed the web client service is running, have added our intranet URL to the trusted sites zone within IE, and numerous other things all without luck.

any help would be greatly appreciated.

-Matt

Sharepoiint with Unix (Font)

Umesh — Wed, 23 May 2007 14:26:39 GMT

Font on the quick launch is not displayed. instead squares are there. What can be the problem?

re: Improvements in Web Browser Compatibility

QRS — Wed, 23 May 2007 18:29:36 GMT

Same problem with IE7/Vista Ent. and WSSv3

Any ideas would be appreciated.

Thanks

re: Improvements in Web Browser Compatibility

Chuck — Wed, 30 May 2007 21:48:06 GMT

Other than no WYSIWYG support for Firefox, has anyone else noticed that Firefox will not properly display (in edit mode) a table created in a Wiki ? All I get is markup language like:

<tbody>

<tr>

<div>Requirements</div></td>

re: Improvements in Web Browser Compatibility

Frustrated with your proprietary platform — Thu, 07 Jun 2007 22:01:09 GMT

Internet Explorer takes advantage of proprietary technology that is only compatible with Windows workstations. Firefox is standards-based and works on most platforms. And your team has given Firefox and Opera the made up status of "Level 2 Browser"? This is completely ridiculous!

Just so you know my background, I'm a VB.net/MSSQL/ASP.net developer who has decided to move to OpenSource for development. The only reason I still use Windows is because I have customers who I've developed projects for in your proprietary platform. I've made the switch to Linux personally, and hope to professionally soon. Oh, Microsoft, what could have been.

For those of you who are tired of Windows and Microsoft's proprietary development platform, please consider Linux. The community support has been a pleasure. And people in the OpenSource community (for the most part) are not trying to exploit you and your wallet like Microsoft.

re: Improvements in Web Browser Compatibility

tchuta — Mon, 11 Jun 2007 12:42:20 GMT

Well, I find it abit frustrating there no WYSIWYG support for firefox. However, I hope the shapepoint team will soon make this possible.

re: Improvements in Web Browser Compatibility

MSDev — Mon, 02 Jul 2007 23:34:49 GMT

We are a Microsoft Shop and we deploy Microsoft Technologies throughout our infrastructure where we can. Our Graphical department use all macs. Guess what, they us Safari and Firefox. We through SPS2007 would fix some of the compatiblity issues but as usual with most Microsoft products, it's failed to deliver. Shock and awe failed to shock us (Business as usual) and awe (wha' did sorry, was asleep, did someone drop a pin?)

Can someone at microsoft buy a clue (or company) and fix this easy problem? This will definately make an impact.

re: Improvements in Web Browser Compatibility

Jose Ultsch — Wed, 25 Jul 2007 17:39:07 GMT

My company (>1000 employees) is looking at adopting a new CMS and MS Sharepoint came up high on the list but the Firefox debacle is a non-starter so I guess we'll have to look at other products. Too bad as the Sharepoint features are really nifty.

re: Improvements in Web Browser Compatibility

disgruntled with MS — Tue, 11 Sep 2007 15:24:26 GMT

It is amusing that MS still uses ActiveX as an excuse not to support its products competing browsers. ActiveX is a crutch that MS uses to get around having to come up with clever, smart solutions to designing web applications. the only other reason to use ActiveX now that web application programming is very mature and robust is to purposely limit browser support. I want to adopt Sharepoint (and Exchange really) as I like it very much, but I just can't bring myself to do it when MS is still using the same old tired excuses to not give us what we want to pay for.

I could list 100 web applications that use "a rich text editor with an easy to use rich text toolbar" and have cross browser support, but for lack of time and space lets just throw google docs, joomla, drupal, and ALL of the nuke portals out there. Pathetic.

re: Improvements in Web Browser Compatibility

Paul Munro — Thu, 13 Sep 2007 21:25:45 GMT

This is just plain wrong. We are a school that needs to implement a VLE solution that (just as it happens) will use Sharepoint 2007. We are also going through a massive new build and have decided (being an Arts status school) to go Mac. Guess what? We have (apparently) chosen "level 2" browsers. Well, I make no apology for now considering Moodle and other solutions. Microsoft- you *need* to fix this. Even if we weren't going Mac, we disable Active X!!!!

Meh.

re: Improvements in Web Browser Compatibility

Sarah Gonzales — Wed, 03 Oct 2007 17:27:15 GMT

Folks, aside from all the complaints about the rich text editor, which I agree with, but is really just a minor convenience, the BIG lack of support for Firefox or Safari or browsers other than IE is the INABILITY to version documents and check documents in / out of Sharepoint 2007. This is a massive deficiency - if I'm missing something, please reply, but in my book - the inability to check documents in / out of Sharepoint using any browser other than IE is a show stopper for our overall adoption.

Your client does not support opening this list with Windows Explorer.

Philip Waters — Fri, 05 Oct 2007 18:02:49 GMT

I think it is a Vista Problem too.

The authenticating three times happened when I changed the IIS application to accept basic authentication.

There was also another workaround where you have to enable a fake proxy on the IE client and bypass url's starting with * so they don't go through the proxy.

on an XP machine I was getting this error after someone installed the Office 2007 compatibility package for Office 2003. Investigating browser Add-Ons revealed they had two copies of OWSSUPP.dll. Disabling one of them made the browser crash, disabling the other fixed the problem in the subject line as well as many others.

Finally on my Vista machines that will let me save a Word Doc directly to sharepoint, but still give me an error opening up explorer view, I tried the solution

regsvr32 -u owssupp.dll

regsvr32 owssupp.dll

and I get the error "DLL Register server failed" 0x80070716

I suspect this is why i'm still having problems in Vista, I ahve yet to resolve it.

re: Improvements in Web Browser Compatibility

Andrew Walding — Mon, 08 Oct 2007 05:04:46 GMT

We have upgraded our Sharepoint 2003 to 2007 and badly need the Powerpoint slide library function. What does this have to do with Web browsers? Well, The latest version of Firefox is great, though not fully functional. Explorer crashes every time we want to edit the slide!!! We have to log onto the server and use the old version of Explorer!!!

I am not sure what is going on here - but simplification and interroperability even within the Microsoft environment is questionable. And there is little or no info on this matter anywhere.

re: Improvements in Web Browser Compatibility

Bernard Koch — Wed, 10 Oct 2007 18:34:06 GMT

We have ActiveX disabled. Is that the reason we cannot save files when running Word into a document library in MOSS? We could save documents in WSS2.0.

re: Improvements in Web Browser Compatibility

Vince Weathermon — Tue, 27 Nov 2007 21:49:04 GMT

Have 7000 users, and adoption is also critically dependent on UX users being functional on their Mozilla browsers. I was hoping that there may have been some change since this blog was published over a year ago, and that there is a roadmap for compatibility that we may see so I can avoid being fried for liking SharePoint as much as I do.

My gripes are:

Rich-text editing (even with ActiveX, it is lame since you can't browse to insert document links, images) and certainly should be functional on Mozilla

Wikis; very stripped down, same issue with the rich text editor, and lacking ability to provide section links and table of contents.

YGTBSM!!!!!!!!!!!!!!!!

Another victim of the Redmond marketing machine — Thu, 13 Dec 2007 21:37:02 GMT

I want to desperately believe that I simply have a client configuration issue going on here, but even using every tip/trick mentioned in this blog, I can not get this MOSS 2007 dog to even render a page to view in FF 2.0.

Jebus H. Krispies, Microsoft, this Sharepoint 2007 tool has got to be the biggest, most ginormous pile of steaming curdled cheese that has ever been excreted out of the Redmond Orifice since the Windows platform itself. The fact that your marketing group has done such a massively successful job of selling this turgid woofer to large government agencies makes me truly question the Human Condition, now more than ever.

Can you not POSSIBLY grasp the concepts of standards-based software? Have you learned NOTHING from all those complaints, lawsuits, etc over the years? It's just more of the same isn't it.... it's the Microsoft way, or the highway. That's our two options, right?

Shyeah, right! {eye-ball roll}

Please excuse me now while I go throw up. Again.

re: Improvements in Web Browser Compatibility

Jay P — Tue, 18 Dec 2007 17:37:31 GMT

Has anyone else noticed that Safari 3 that comes with the 10.4.11 update does not work with Sharepoint? Is MS going to resolve this?

re: Improvements in Web Browser Compatibility

EVI — Wed, 23 Jan 2008 12:27:00 GMT

I have quickly read threw the comments but, from what I can make of it using MOSS2007 on a MAC is not really a great way to go. Is this correct? Or is it just a browser issue?

re: Improvements in Web Browser Compatibility

Barry — Wed, 23 Jan 2008 23:20:21 GMT

well, I noticed no one who checks this periodically ever answered my question. I just gave the major thumbs down to one of MS' knowledge-base articles, which absolutely not only did not help, but was highly inaccurate!

Can anyone shed real light on this issue?

http://support.microsoft.com/kb/923906

This does not account for Mozilla browsers, but that's not even the issue. I say Mozilla browsers, because they behave the same way as half of our users' browsers -- client does not support this list in Windows Explorer view.

Can anyone please help here? Here's one thing I totally suspect as bad, but it's not scientific. We use Win2K, Office2K with SP 2007. Now, I don't have a problem, but a good many do, and I reckon it's due to the hotfixes and which order they were applied, but again, that may be a slight stretch.

re: Improvements in Web Browser Compatibility

Horst Hen — Fri, 15 Feb 2008 00:29:34 GMT

Just to make things worse. Sharepoint does not work with Opera Mini - the superior browser for mobile phones. Opera Mini is the only mobile browser which efficiently uses transcoding technology reducing the data traffic between mobile and server to about 10%. This browser beats iPhone easily. Hoewever, you just can passively browse Sharepoint pages. Most interactive Sharepoint functions don't work.I definitely know that all the interactive functions can be done without using special IE and ActiveX functions. May be MS should revisit their strategy or just hire a couple of the art developers who know the state of the art.

re: Improvements in Web Browser Compatibility

Barry — Wed, 27 Feb 2008 20:06:01 GMT

Ok, problem solved, sort of. See my post, two posts above this one -- I also thought I'd posted last year some time.

Any way, after many frustrating attempts at all of this, a very nice, and knowledgeable MS engineer spent a good amount of time on the phone with me.

Now, the irony to me was, he'd not encountered this issue with the various specs I had: Win2K for OS, MOSS2007, and IE 6, SP1.

The only irritating thing was that the Hotfix MS sent me to help rectify this would alert me that my system required IE6, SP1, which, DUUUUH, that's what I already had installed!

Any way, he walked me through it, we got a new KB going (TBD) and he had me add my SP site as a network place.

It seems that when we get new, or re-imaged PCs here that they are not picking anything up from MOSS (specifically the WebDAV part) at all that would indicate we have the shared doc privelege. Now, we were not able to only add the sharepoint root -- I did have to specifically add all of the URL.

re: Improvements in Web Browser Compatibility

greg chesney — Sat, 01 Mar 2008 21:58:29 GMT

If MS wants to paint themselves into a corner, let them. If they want users who are forced by corporate edict to use SP hate MS, let them. If they want to keep paying huge fines to the EU and have DOJ looking over their shoulder for the next decade, let them.

Gate's competitive culture still lives at MS and it's going to take a long time to get rid of that. He's gone. Monkey Boy needs to go. I wonder if there's anyone left who knows what a win-win it is to follow standards and value the respect of it's customers.

re: Improvements in Web Browser Compatibility

HemantSoni — Mon, 03 Mar 2008 11:33:31 GMT

Hi Troy,

I am using a DataView MOSS Control of Sharepoint Server in my site.

Filtering feature of this control is working well in IE. e.g. when we MouseOver a triangle comes for more options of filtering plus sorting. When we click on that it collects all unique values for that column and we can filter on that.

But same thing when we try with Firefox then sorting as a link comes on the column title but that triangle for filtering does not comes.

Please let me know some solution for this. If this is control issue then by when you will be resolving it.

Hemant Swarnkar

re: Improvements in Web Browser Compatibility

Ed Manning — Mon, 17 Mar 2008 13:54:48 GMT

So you cannot access and edit SharePoint wiki on Windows 2000 securely.

Many corporates have not yet adopted IE7, and if you are on Windows 2000 it is not an option, which is why if you have a mixture of operating systems you will stick with IE6.

However IE6 does not support AES and does not support 256 encryption.

This can easily be done on Windows 2000 with Firefox, but with Firefox you cannot edit wiki properly.

This is a serious flaw with SharePoint, and may mean that SharePoint cannot be used for my project.

It also demonstrates to a European mind why Microsoft's monopoly requires further action.

re: Improvements in Web Browser Compatibility

Susan — Wed, 02 Apr 2008 21:18:31 GMT

We have a MOSS active X problem. Our default master page needs to have the center section be a specifc size. Mandated by our Corporate Office and they will not let us change it. But the Edit in Data Sheet View Active X control will not open. It just remains on the hourglass for ever and then crashes the browser. I supect the Active X control is trying to expand and it can not because of the master page layout.. its not an option to change the master page so how can we change the Active X control to not try to expand?

re: Improvements in Web Browser Compatibility

Prabagarane — Wed, 09 Apr 2008 15:05:43 GMT

hi guys, anybody knows or any work around to implement the Upload multiple documents option in firefox, because my clients ask me to do somethings to find out a soltions to resolve this issue..but i cant find even a single solution for last one weak..

which one is the right way to implements this one. develope any webparts or deploy any user controls .. please any help me to resolve this isuee...

re: Improvements in Web Browser Compatibility

Eddie V — Wed, 30 Apr 2008 00:34:01 GMT

Hello

We are mostly a microsoft shop and moss is running great. We also have Mac users who access the site via Mozilla. I have just one issue: I have it crawling a file share located on our mac server, it crawls fine and i can access the files with a pc, but not with a mac. They come up but wont open. It their a way to crawl the mac server not using afp://ip address?

Wow. Still in denial, eh?

anonymous — Tue, 13 May 2008 21:24:10 GMT

Splitting browser support into two levels is still dividing your customers into the "haves" and "have nots" regardless of whatever splintery bones you throw to us dogs.

I cannot fathom why Microsoft doggedly follows the "we're the only browser that matters" philosophy when Google is KILLING Microsoft in its support for almost all browsers, among other things.

It's time to retire the ActiveX SDKs and start programming web sites like the rest of the world does.

re: Improvements in Web Browser Compatibility

IT Guy Taking Abuse For MS — Thu, 22 May 2008 00:26:28 GMT

I just got out of a meeting regarding SharePoint and I being the one man "IT-Dept" got royally abused because of the lack of support for both Opera and Firefox. This lack of support only fuels the hate against MS - I just don't get MS's "plan" if there is one. Imagine a gas station where you couldn't fill your tank because you have a Toyota and you were at a Ford station. Grrr ... no wonder people hate MS.

re: Improvements in Web Browser Compatibility

John — Thu, 26 Jun 2008 00:22:06 GMT

A Leopard cannot change its spots.

re: Improvements in Web Browser Compatibility

Pawel — Tue, 15 Jul 2008 21:30:12 GMT

Firefox support in SharePoint is a joke! We have office 2007 and if someone has their firefox browser set as default browser in a system, opening links from email straight to Excel documents does not work properly. The Check Out button does not show and our users keep loosing the changes they made to the document (clicking Save button does not show any warning or anything and it just looks like document was saved back to SharePoint, where it wasn't!) There is so many other things that don't work in Firefox that it's not even funny! I'm surprised that these issues are still not resolved even though SharePoint 2007 and Wss 3.0 were around for a while now

re: Improvements in Web Browser Compatibility

zullu — Mon, 21 Jul 2008 21:29:10 GMT

Anyone out there got the MOSS 2007 web sites working in FireFox 3.0.1+ and Safari 2.0+

Zullu.

re: Improvements in Web Browser Compatibility

Hassan Dibani — Fri, 01 Aug 2008 11:51:16 GMT

Ok, So MS is saying that the reason there is not RT editor for Firefox is lack of time. Fine.

It is now 2008!!! how much time does MS need to fix a single rich text editor?

In the mean time, i suggest everybody looks at this Open source share point replacement:

http://o3spaces.org/

re: Improvements in Web Browser Compatibility

Susan — Sat, 30 Aug 2008 01:43:04 GMT

I've been running Sharepoint 3.0 for quite a while now - we've worked around it's shortcomings, but anything that alienates 50% of my clientele (more specifically, an entire school district on Mac) is NOT an improvement. I would like a fix for the html rich text editor tools that apparently vanished for SP when people installed Firefox 3.0.

Fellow victims: Please help!

MS: Grrrr >;[

re: Improvements in Web Browser Compatibility

Ralph Rivas — Tue, 02 Sep 2008 21:26:29 GMT

My client is just getting off a support call to teh WiPro Folks of Microsoft (yes, we know who they are ... why bother masking it???)

The issue was with IE 6, a "level 1 browser" not able to work with the Content Editor Web Part. The mouse would not work and selection via the keyboard only worked in minimal cases. IE7 works fine. editing in HTML also works. They made the client go through 2 hours of doing the same thing over and over again concluding at the end that the client "must upgrade their machines to IE7" ... that is to say all 3,000+ machines that are on a phased roll-in due to costs. The reason given: IE 6 has some known problems. Links and support proof given: 0, none, ZERO, NOTHING, NADA, NIL ...

So ... your friendly "support" folks have just made you look bad. Care to follow up?

re: Improvements in Web Browser Compatibility

Betty Ge — Sat, 27 Sep 2008 01:30:06 GMT

But I just tested Firefox, I couldn't checkout document from Sharepoint, it said IE 6 or above is needed.

Algunas ligas de interés

Luis Du Solier G. - SharePoint en Español — Wed, 15 Oct 2008 08:02:39 GMT

Movimiento de bases de datos de SharePoint (distintas opciones) SharePoint Site Moves, Database Moves

Algunas ligas de interés

SharePoint en Español - Luis Du Solier G. — Wed, 15 Oct 2008 08:03:59 GMT

Movimiento de bases de datos de SharePoint (distintas opciones) SharePoint Site Moves, Database Moves

Algunas ligas de interés

Wed, 15 Oct 2008 08:04:32 GMT

Movimiento de bases de datos de SharePoint (distintas opciones) SharePoint Site Moves, Database Moves

Supported browsers in SharePoint

Shared Points for SharePoint... — Fri, 14 Nov 2008 13:49:18 GMT

From time to time questions about crossbrowser support comes up. The answers can be found at Technet

Microsoft SharePoint Team Blog Improvements in Web Browser Compatibility | Paid Surveys

Fri, 29 May 2009 19:04:59 GMT

PingBack from http://paidsurveyshub.info/story.php?title=microsoft-sharepoint-team-blog-improvements-in-web-browser-compatibility

Improvements in Web Browser Compatibility

SharePoint's New Version Improves Web Browser Compatibility

Sharepoint 2007 + Firefox = No rich editing

Browser support in WSS v3

re: Improvements in Web Browser Compatibility

SharePoint 2007 und Browserkompatibilit&#228;t

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

Tech Talk PT » Blog Archive » Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

Microsoft's SharePoint treats FireFox as 2nd class citizen

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

Microsoft PacWest SharePoint Server Newsletter – July 2006

Cross-browser compatability in WSS/MOSS

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

SharePoint en Firefox | KennethVerburg.nl - Information Engineer in het Wild

WSS 3.0 in... Camino!?

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

SharePoint Server 2007 の対応ブラウザ

re: Improvements in Web Browser Compatibility

Web 2.0 Browser Unterst??tzung bei Microsoft « PrivatesPortal

Cross-browser authoring

Cross-browser authoring

SharePoint: Cross-browser authoring

SharePoint: Cross-browser authoring

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

List of MOSS 2007 ActiveX controls (created searching the visible code)

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

Sharepoiint with Unix (Font)

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

Your client does not support opening this list with Windows Explorer.

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

YGTBSM!!!!!!!!!!!!!!!!

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

Wow. Still in denial, eh?

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

re: Improvements in Web Browser Compatibility

SharePoint 2007 und Browserkompatibilität