Thanks, Carey! I was asked to provide some sort of a link to BMC's site that specifically states incompatibility. I would agree that the flaw is in Safari somewhere. I was able to get it load and work somewhat using the latest Safari WebKit, however it seems that it is not fully compatible yet. There are some javascript errors which is what I believe the issue is.
Gene > From: Carey Matthew Black <[EMAIL PROTECTED]> > Reply-To: <[email protected]> > Newsgroups: public.remedy.arsystem.general > Date: Thu, 1 Mar 2007 09:59:33 -0500 > To: <[email protected]> > Subject: Re: Apple Safari Web Interface > > Gene, > > The fact that Safari is not on the compatibility matrix shows that it > is not supported. ( What more do you need to tell your management that > it is not supported?) > > Based on what David said, I think it sounds like the flaw in Safari is > scheduled to be fixed in a future version of it and after Safari is > fixed BMC will either make corrections in the Mid-Tier to work with > those fixes or all should be "better" without changes. ( He was a bit > vague on those details, but that is ok too.) > > > However, ( and I do this very rarely because I have no personal > experience with the product ) there is/was an "alternative web client" > out there too. As I remember it, they claimed to be a full replacement > for the Mid-Tier and that they were totally "standards based" and > would work with any browser. ( Please read their marketing information > for yourself. That is just my memory of their marketing information > talking. ) > > If you have to have support for Safari faster than "mid-2007" then you > might take a look at that product offering. < goes a way and searches > for alterurnative web client web site... but failes to find it. hum... > It was out there somewhere... > > > > Maybe the company that did/does offer a Safari compatible web client > interface could stand up and let Gene know your still out there? > > -- > Carey Matthew Black > Remedy Skilled Professional (RSP) > ARS = Action Request System(Remedy) > > Love, then teach > Solution = People + Process + Tools > Fast, Accurate, Cheap.... Pick two. > > > > On 3/1/07, Gene Ushinsky <[EMAIL PROTECTED]> wrote: >> David, >> >> Is there an official page/KB article somewhere that states that Safari is >> not currently supported? I have been asked by my superiors to have something >> to show. >> >> Also, since you did figure out what the problem was between Safari and >> Remedy, can you share what the problem is? Is it even possible to fix with >> the current version of Safari? >> >> Thanks. >> Gene >> >> >>> From: "Easter, David" <[EMAIL PROTECTED]> >>> Reply-To: <[email protected]> >>> Newsgroups: public.remedy.arsystem.general >>> Date: Mon, 29 Jan 2007 18:39:03 -0800 >>> To: <[email protected]> >>> Conversation: Apple Safari Web Interface >>> Subject: Re: Apple Safari Web Interface >>> >>> >>>> but have yet to figure out what it is. >>> >>> Actually, BMC did work with Apple and figured out what it is. Apple is >>> making changes to the Safari browser in Leopard (Mac OS X 10.5) and BMC >>> is scheduled to pick up support for Safari in the mid-2007 release of AR >>> System to take advantage of those changes. >>> >>> >>> Thanks, >>> >>> -David J. Easter >>> Sr. Product Manager, Service Management Business Unit >>> >>> BMC Software, Inc. >>> >>> >>> -----Original Message----- >>> From: Action Request System discussion list(ARSList) >>> [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black >>> Sent: Monday, January 29, 2007 4:57 PM >>> To: [email protected] >>> Subject: Re: Apple Safari Web Interface >>> >>> Gene, >>> >>> Safari does not work. It is not supported. And the last time I heard a >>> voice from BMC say "Safari" was to say that it does not have a "debug" >>> type environment that will allow them to figure out what is wrong with >>> it. :) >>> >>> Basically BMC holds that what they are doing is "standards based" and >>> that there must be something that Safari does not support, or correctly >>> support that is the root problem. They think it is something "simple", >>> but have yet to figure out what it is. (Thus it is not >>> supported.) >>> >>> >>> Personally I would love to see a feature in the Mid-Tier that would >>> allow a person to figure out if the browser is on the "Supported" >>> list, on the "not supported, but is known to mostly work", or on the >>> "nope... that is broke" list of browsers out there BEFORE the user >>> actually attempts to login to the ARS server. However, such a feature is >>> also "unsupported" too. >>> >>> -- >>> Carey Matthew Black >>> Remedy Skilled Professional (RSP) >>> ARS = Action Request System(Remedy) >>> >>> Love, then teach >>> Solution = People + Process + Tools >>> Fast, Accurate, Cheap.... Pick two. >>> >>> >>> >>> On 1/29/07, Gene Ushinsky <[EMAIL PROTECTED]> wrote: >>>> ** >>>> I am somewhat new to Remedy and may not ask the question correctly >>>> but here it is. >>>> >>>> We have a 6.x installation of Remedy that has a web interface to it. >>>> Seems that IE6 and FireFox 2 work quite well with it. However, Apple's >>> >>>> Safari 2.x doesn't. There is nothing on the screen - the page is >>> blank. >>>> >>>> Is this is a known issue? Is this something we need to fix on site, >>>> as it is part of our setup and forms we use? Any help and pointers >>>> would be appreciated. >>>> >>>> Gene >>>> >>>> geneushinsky >>>> OIT - Service Desks Support Manager >>>> [EMAIL PROTECTED] | MB 161A | 801.422.2716 > > ______________________________________________________________________________> _ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the > Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
