Stylesheet for IE 8.0 - Browser Compatability

Hi,
We have implemented CRM ISA 5.0 (B2B) application. We are now upgrading IE 7.0 to IE 8.0, so we need to have IE 8.0 stylesheet in place to incorporate all our older changes to get reflected in IE 8 style sheet. I am afraid if SAP has released note for this IE 8.0 compatibility. Can you guys kindly let us know if you aware of the latest patch for IE 8.0 compatibility.
Thanks and Regards,
Saravanan

Hi Saravanan,
this browser version isn't supported yet by SAP. You can check for which browsers the applications are released in the PAM (product availability matrix). Go to service.sap.com/pam for this.
I guess you will need to patch the coding by yourself to get IE8.0 compatibility....
Best Regards,
Peter Kraus
SAP Web Channel Consultant
http://www.leonardo-it.com

Similar Messages

Is there any tool in DW for chencking browser compatibility ?

Hello all,
I have some doubts. When i develop one website in Dreamweaver, i can check the out put design into all the browser compatibility. But I need to know is any tools having to check browser compatibility for website.
Please reply to this thread,
Regards
Abdul
www.whitehouseit.com
www.ilearnsmart.com

http://my-debugbar.com/wiki/IETester/HomePage
http://ipinfo.info/netrenderer/
You could also look at those.
Martin

I need to install Firefox 4 for browser compatibility testing, but I can only find installers for the current version and 3.6.19; where can I find what I'm looking for?

I am trying to do some browser compatibility testing using Firefox, but I can't find any installers for it here. The closest I can find are installers for 3.6.19 at http://www.mozilla.com/en-US/firefox/all-older.html. Where can I find an official installer for Firefox 4?

Solved my own problem - I can download the installer by navigating directly to http://download.mozilla.og/?product=firefox-4.0.1&os=win&lang=en-US.

EREC : Upgrading browser compatibility for SAP E-Recruiting

Hi
We are currently using E-Recruiting 603 Sp 2 (Netweaver 7), does anyone knows how to upgrade browser compatibility. Currently we are only supporting Internet Explorer and Firefox up to version 7.0 and 3.5 respectively. Does anyone how to upgrade the browser compatibility to includes the newer version of IE, Firefox, Chrome and Safari.
Expert please help.
Regards
Ridzuan

Hi Ridzuan,
We have exactly the same problem as we currently run eRecruitment on EHP3 (Netweaver 7.00).
With EHP3, SAP officially support IE and Firefox only. This doesn't help external job applicants who can be
applying using any web browser. In particular Mac users tend to use Safari as its the default browser. Its not at all
good customer service to have to tell job applicants to download and install Firefox just to be able to fill in a job application.
When we originally implemented, eRecruitment worked fine in Safari, but currently all the drop down lists, date pickers
and pop-up dialogs fail to render making it unusable. This is caused by a security restriction in WebKit (used by Safari and
Chrome) blocking frame navigation.
SAP officially support Safari as of EHP5 (which runs on Netweaver 7.02). If running via the portal you'd need Netweaver 7.2 portal or above for Safari support for the portal.
I also found a SAP Note 1642778 " which includes "Unified rendering: Support for Safari, Chrome browser", which is
relevant to EHP4 (Netweaver 7.01). Upgrading to EHP4 and above isn't a small step if you've done any significant customisation on the BSP Recruiter pages as these are replaced with new ABAP WebDynpro pages.
To date I haven't seen the unified rendering corrections back ported to Netweaver 7.00 even though they were for 7.01
and this isn't officially supported (as per the PAM as mentioned by Andy).
See https://service.sap.com/pam
Then look at the link in the middle of the page:
"Browser information for: SAP NETWEAVER 7.0, SAP EHP1 FOR SAP NETWEAVER 7.0 and SAP EHP2 FOR SAP NETWEAVER 7.0 "
This opens a PDF showing official support dependencies between browser versions and SAP versions and patch levels.
EHP3=Netweaver 7.00
EHP4=Netweaver 7 EHP1 (a.k.a. 7.01)
EHP5=Netweaver 7 EHP2 (a.k.a 7.02)
To see what patch level you're running log into the SAP GUI on the eRecruitment system, then select System->Status...
from the menu. Click the detail (maginifying glass icon on the right next to Component Version). Then look at the patch
level of the SAP_BASIS component. Compare this to the patch levels in the browser support PDF to see which versions
to upgrade to e.g. SP24 or higher for IE9 support.
We're currently patching our EHP3 system up to SP25 to help with IE9. Firefox 8 is working (as is Firefox 9 beta).
Sadly Safari and Chrome still aren't working and this is the latest patch level. SP26 is mentioned but not out yet.
Also check the browser roadmap on p17 of the browser support PDF. It makes clear they intend to support Safari and Chrome
going forward but no timescale is given.
George

CSS error, style sheet link, affects browser compatibility..

Left comfort of GoLive and tables, to CS5 Suite - Dreamweaver. Basic CSS skills, so don't have the intuitive ability to frame question well.
Regarding this particular page, I simply built, then copied the index.html page on a test site at:
http://www.screamingeagles.com/client_view/ScreamingEagles_v2/index.html
and stripped out sidebars and menu bar, and began building a form in the "main content" area.
URL to page in question:
http://www.screamingeagles.com/client_view/ScreamingEagles_v2/contact/contact.html
Noticed a "green line" in code so checked browser compatibility as follows:
-------Browser Compatibility-------------------
Found 2 errors in twoColFixLtHdr.css
Affects: Firefox 1.5; Internet Explorer 6.0, 7.0; Internet Explorer for Macintosh 5.2; Netscape 8.0; Opera 8.0, 9.0; Safari 2.0
-----------------Error found (green lined in code) as follows------------------------
Line 6: <link href="../css/twoColFixLtHdr.css" rel="stylesheet" type="text/css" />
Validation didn't give me anything to go on. Given my modest coding skills, should I just build a new page from templates as an better
alternative to bothering forum participants?
Thanks in advance,
J. Satterwhite
SatGraphics.com
Mac Pro
Adobe Creative Design Suite

Noticed a "green line" in code so checked browser compatibility as follows:
-------Browser Compatibility-------------------
Found 2 errors in twoColFixLtHdr.css
Affects: Firefox 1.5; Internet Explorer 6.0, 7.0; Internet Explorer for Macintosh 5.2; Netscape 8.0; Opera 8.0, 9.0; Safari 2.0
-----------------Error found (green lined in code) as follows------------------------
Line 6: <link href="../css/twoColFixLtHdr.css" rel="stylesheet" type="text/css" />
Validation didn't give me anything to go on.
I think that the errors are *in* the twoColFixLtHdr.css file, so you need to open that file and run Validation again.
HTH,
Randy

Browser Compatibility Error in DW CS5 assets link Please help New to Dreamweaver

Please can anyone help? Using DW CS5 -.Using Spry Menu Bar 2.0 - have it all formatted - ran Browser Compatibility -Shows my Spry link reference has error. Here is the code
<script src="SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
       <link href="SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css">
       <style type="text/css">
       body {
Error is underlined at: <link href="SpryAssets/SpryMenuBarHorizontal.css"
It is located in the page head just below the banner
I am new to dreamweaver..I do not know how to fix this code..
Running Win XP. Thank you in advance for any help you can provide.

In case you need it the link to this page is:
http://www.bountifulspinweave.com/aboutus.htm
It is spry menubar 2.0

Browser compatibility issue with IE6/7

Hello,
I created my webpage in dreamweaver on a MAC. I have viewed my page(s) A-OK in Safari and firefox however I am being told that my page is not viewing properly on Internet Explorer. I then found the browser compatibility feature to test the page in Dreamweaver. What I have found is that I have browser support problems...this is the error from my index page - which is actually on all my pages!
un-scrollable content bug:
If one or more absolutely-positioned elements are placed within a relatively positioned element with no assigned dimensions, either no scrollbar will appear at all, or it will not extend far enough to view all of the content. (Note: This bug will not affect your page if the content in the AP element does not extend beyond the height of the viewport.)
Affects: Internet Explorer 6.0
Likelihood: Possible
This bug is on line 56: <div style="position:relative">
This issue is on all my pages...please help
I am just not sure how to solve this problem - I am more of a designer than a coder. Any help whatsoever to point me in the right direction is most graciously appreciated!!!
My webpage URL is: lifeforcemd ah yes that is a .com extension - lifeforcemd.com

Hi kadarusastry,
This issue is about the browser compatibility.
Please add your SharePoint site into compatibility view in IE 9 or IE 10.
Or, use IE 8 mode in browser mode for IE 9 or IE 10.
About how to add site into compatibility view, you can refer to the link:
http://support.microsoft.com/kb/2536204
Note: the settings for IE 9 and IE 10 are same.
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Spry accordion browser compatability issues

I am building my first site and was in the process of checking each page for browser compatability. this certain page has spry accordians and I have some error messages that I don't understand.
The first one says Line 48 has 2 errors in SpryAccordian.css. I don't have any indication of what the problem is and where exactly line 48 is on the page. Is there a way for it to take you to that exact spot to show you where the problem is?
I clicked on get more info. and came to a page that doesn't seem to be addressing what my issue is. Don't understand that part.
How do I fix this and why did it happen?

Type cmd / ctrl + , for the go to line number window in DW.

Browser Compatibility Issue with IE9 and IE 10

Hi Everybody,
I have a page which contains pageviewer Webpart, which redirects to the other page the problem is in IE 8 this works good but comes to IE9 and IE 10 the page is not displaying on the page but link is working good. Can any one please give me suggestions on
this?
Thanks and Regards,
kadaruSastry

Hi kadarusastry,
This issue is about the browser compatibility.
Please add your SharePoint site into compatibility view in IE 9 or IE 10.
Or, use IE 8 mode in browser mode for IE 9 or IE 10.
About how to add site into compatibility view, you can refer to the link:
http://support.microsoft.com/kb/2536204
Note: the settings for IE 9 and IE 10 are same.
Best Regards,
Wendy
Wendy Li
TechNet Community Support

ADF Faces: !-- ERROR: could not create stylesheet for oracle-desktop.xss

Hi,
I'm using ADF Faces EA6. Sometimes when I create the EAR, it doesn't include the file "oracle-desktop-ea6-ie-6-windows.css" which muest be present in the "adf/styles/cache" directory. If I check the source code from the browser, it starts like this:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html dir="ltr" lang="es-ES">
<head><title>Sistema de Seguridad</title><meta name="generator" content="Oracle ADF Faces"><script type="text/javascript" src="/fmv/adf/jsLibs/Commonea6.js"></script><script type="text/javascript">_defaultTZ()</script></head>
Please note the comment: 
Does somebody know the reason?
TIA,
Brian

If everything is set up properly the css will get generated if it doesn't exist. You do not have to be running in the IDE for the css to be correctly generated. Running the app first is generating the css before you deploy, so you've taken away the symptom but not solved the problem. If you try running on another browser, for example, you'll probably run into the same problem.
Does your ear get unzipped when you deploy? Do you have a writable file system for the css to get written to? There is a known issue with WebLogic where it doesn't expand the EAR.
Please check to see if there are errors in the logs.

Expert in xsl - stylesheets for unicode (UTF8)

Hi,
I am looking for an expert in xsl-stylesheets for unicode (UTF-8 format) in order to check the syntax of a stylesheet for the browser-based PI-Sheet in SAP ERP PP-PI.
Can you advise someone ?
Thanks & BR,
Miriam

Hi Kannan,
thanks for your answer!
Unfortunately this problem is a bit more tricky.
We are looking for so. who really can check the syntax of ~ 1.000 lines of XSL coding. The problem is that it cannot be converted to UTF8 because of syntax errors.
=> Do you have an idea who could help here?
Thanks a lot, best regards,
Miriam

Browser compatability and internet connection

When I do a browser compatibility check in DW CS3 it gives me
the error with the link to the Adobe site at the bottom right hand
side, but when I click on the link it tells me I am not connected
to the internet. I am in fact connected to the internet via
wireless connection. I checked this by choosing "updates" and that
ran fine. So why does this not work?

Do you have a location in System Preferences/Network for your PC card? If not, try setting one up and see if you can connect. You will need to create a new location, and under Network Port Configuration add a new one for your card. Drag it to the top of that window, making it first and make the others are unchecked (unless they are needed as part of the setup). You may not have to create a new one if the system's recognition of the card has added one; I'm guessing on this though. I had to do this both on my PB 1.67 and my Wallstreet G4 in order to get a wireless to work. You are using a different access method, but maybe it will work.
Tom

Browser Compatability Help please?

Hi. Im somewhat new to Dreamwevaer, I actually still use GoLive, but slowly trying to move over to DW.
Im doing Browser Compatability tests for a website, and not sure how to fix these errors DW is giving me.
Id appreciate any help or thoughts?
thank you in advance!
-Unsupported value: 'inline-block' Affects: Netscape 8.0
-Unsupported value: 'inline-block' Affects: Internet Explorer 6.0, 7.0; Internet Explorer for Macintosh 5.2; Opera 8.0, 9.0; Safari 2.0, 3.0
-Error parsing styles Affects: Firefox 3.0
-Unsupported property: zoom Affects: Firefox 3.0; Internet Explorer for Macintosh 5.2; Netscape 8.0; Opera 8.0, 9.0; Safari 2.0, 3.0
-Unsupported property: content Affects: Internet Explorer 6.0, 7.0, 8.0; Internet Explorer for Macintosh 5.2

You do have some HTML errors. If you run it through this validator, it will show you where they are and you can repair them...
http://validator.w3.org/
There is an error in the css of your <head> section, you have a line of css outside your <style> tags...
#example-one li,#example-one li a { display: inline-block; float: none; *display:inline;/* ie6 and 7 inlin e-box hack */ zoom: 1.0; }
If you don't need it, delete it, if you do, just move it into one of the <style> tag sets. (you may want to clean the css up and move it to an external sheet so everything is in the same place)
The rest of it looks fine according to the CSS validator here: http://jigsaw.w3.org/css-validator/ the errors it throws, aside from the out of place css line are to be expected and don't affect anything negatively (they're just browser specific code).
I wouldn't be surprised if that line is causing the error you're seeing.

Browser compatability check

I'm trying to use the new browser compatability check feature
in CS3. It seems useless. It tells me there is an error, but
doesn't tell me WHAT the error is or how to fix it. It just points
me to their website, but there is no reference code of any sort to
reference the error. Are there any tricks to this feature to make
it work better?

See these articles for some suggestions:
*https://support.mozilla.org/kb/Firefox+has+just+updated+tab+shows+each+time+you+start+Firefox
*https://support.mozilla.org/kb/How+to+set+the+home+page - Firefox supports multiple home pages separated by '|' symbols
*http://kb.mozillazine.org/Preferences_not_saved
Which security software (firewall, anti-virus) do you have?

JSF Cross Browser Compatibility

In reading about JSF I find no promise for cross browser compatibility. Am I to assume that this has been missed because
i. JSF is a specification and not an implementation and I should be looking for the implementation to make that promise.
ii. it's basically to hard to promise this.
iii. I didn't look hard enough.
I am guessing it's a (i) with the likely hood of (ii) to follow. But I would be interested on any feed back that anyone cares to add. For example, a implementation that is trying to promise this.

In my opinion, the JSF specification (or better, any specification) can only refer to other specifications, but never to a concrete software product. Consider a sentence like:
        JSF 1.0 is compatible with IEWhat could that mean? Some possibilities:
(1)     As it happened, until now, we did not stumble over a
        faces application that broke when run on our Faces
        reference implementation (version 1_1_01) in a
        WSAD 5.0 container in combination with IE 5.5
        with patch 12345 on Windows NT4 SP6 patch 98765.
        (To breake means to produce a result not legitimized
        by the spec, or to produce no result when one is
        expected, at least not in a reasonable time.
        Breakdowns caused by power failure or other
        reasons outside the scope of the spec to be ignored)Well, not worth any further comment.
(2)     Implementations of JSF 1.0 Spec will not brake
        on any faces application when run in a
        WSAD 5.0 container in combination with IE 5.5
        with patch 12345 on Windows NT4 SP6 patch 98765
        (To breake means ...)That is ok... if you have just this combination of components and will never change. Keep in mind that (2) does not promise
anything if you use IE5.5 patch 12345a (and the saying is, there have been several patches to IE ;-)
(3)     Implementations of JSF 1.0 Spec will not brake
        on any faces application when run in any container
        in combination with IE 5.5
        with patch 12345 on Windows NT4 SP6 patch 98765.
        (To breake means ...)Same as (2)
(4)     Implementations of JSF 1.0 Spec will not brake
        on any faces application when run in any container
        in combination with IE 6.0 on any platform with
        any patches.
        (To breake means ...)Maybe what is intended, just impossible to promise. First, such a bold statement about some software can not be proven.
Second, even if you have gained good confidence by thorow testing, who knows which future changes Microsoft will apply to IE 6.0 (via patches, which offen not only correct bugs, but also introduce new and maybe incompatible features)
(5)     Implementations of JSF 1.0 Spec will not brake
        on any faces application when run in any JSP 1.2
        or higher container in combination any broser
        which supports:
           - HTML 4.0.1
           - JavaScript 1.3
           - CSS 1.0
        where IE 6.0 is a browser which supports these
        three standards on any platform with any patches.
        (To breake means ...)It's getting better. But why, for heavens sake, should a JSF specification make a statement about the compliance of IE with HTML 4.0.1, JavaScript 1.3 and CSS 1.0? I think it would be the job of Microsoft to declare the compatibilty of their products with standards (if any applies, whatsoever).
Therefore, lets get rid of these and we have:
(6)     Implementations of JSF 1.0 Spec will not brake
        on any faces application when run in any JSP 1.2
        or higher container in combination any broser
        which supports:
           - HTML 4.0.1
           - JavaScript 1.3
           - CSS 1.0
        (To breake means ...)Nearly finished, just a little bit wordy. It is (nearly) obvious what 'to breake' means. And that it is common wisdom that software breakes, not some specification (Or, as Bertrand Meyer put it, Bubbles don crash. Specifications may be contradictory or fail to describe an algorithm, but never crash). Common wisdom removed gives:
(7)     Implementations of JSF 1.0 need a JSP 1.2 container
        and a browser capable of HTML 4.0.1, JavaScript 1.3
        and CSS 1.0That's it. Specs exist for two reasons. First, to be discussed and thought about. Second, to be implemented. (To the supporters of agile methods: of course you can reverse the sequence ;-). Therefore, specs should be as short and concise as possible, omitting any useless blabla. If the specs are sufficently precise and of moderate complexity, we can even try to prove the compatibility of the specifications. 'COMPATIBLE WITH IE' is advertisement, not tech talk.
Conclusion: Mixing up specifications and implementaions is generally a bad thing. Exception: All sentences where a specification and a implementation are mentioned together should have the form:
         Implementation X does [not] conform to specification Y
---------------------------------------------------------------------------------------------------------I have a follow up question, just inspired by yours. It does not especially concern JSF, but web pages in general.
Some time ago, I stumbled over quite a few web sites with big red eye catchers:
OPTIMIZED FOR INTERNET EXPLORER!!!
And really, they did not look good on Netscape Navigator. Now, my question is, what do you think when you hit such a page? My first thoughts (it's long ago) have been:
    - Oh, nice designers. They really care for the majority of people,
      my neighbor uses an IE.
    - They just skiped the work for other browsers and sell this as an
      optimization. And I didn't get it. Very clever.
    - Poor Guys. Probably they had no other browser at hand.
    - Obviously they had publish this tremendously important information
      under pressure, no time to also optimize for others browsers.Wolfgang Oellinger

Stylesheet for IE 8.0 - Browser Compatability

Similar Messages

Maybe you are looking for