Skip to Content

Firefox 35 successfully tested with NetWeaver

Firefox 35 Rapid Release Cycle was released on January, 12th, for Windows, Mac and Linux.

New features Include:

  • a new rooms-based conversations model, called “Hello”
  • a new search UI improved and enabled for
  • access the Firefox Marketplace from the Tools menu and toolbar button
  • built-in support for H264 (MP4) on Mac OS X Snow Leopard (10.6) and newer through native APIs
  • improved handling of dynamic styling changes to increase responsiveness
  • HTTP Public Key Pinning Extension (for enhanced authentication of encrypted connections)
  • improved high quality image resizing performance.

For more details about the new changes, read the release notes for Firefox 35. The browser is available now to download from

Mozilla Firefox 35 RRC has been successfully tested with NetWeaver versions 740 SP10, 731 SP14, 730 SP13, 711 SP13, 702 SP16 on operating systems Win 7 64-bit, Win 7 32-bit,  Win 8-64 bit (desktop), Win 8-32 bit (desktop),Win 8.1 64-bit, Mac and Linux in the areas of PLS, WD-ABAP, WD-JAVA, NWBC, ACF, BI, UI5, FPM ,CRM Web UI, EP, Adobe, BPM and FLP on ABAP.


As usual, for further details and SAP restrictions see: SAP Product Availability Matrix (PAM): Firefox browser note:

You must be Logged on to comment or reply to a post.
  • Hi Andreas,

    I have a couple of question and would be glad if you can find some time to help me on. I have actually a customer EP 7.31, which was updated to SP14 recently. Accroding to the new stand, they would like to test also on last FF 35 and Chrome 40 versions, which are supported and tested due your statements and the PAM.

    After first quite shallow tests EP looks good on both browsers. I have noticed some small problems apparently, before I open an OSS may I ask you 2 things please:

    1.)Can we assume minor changes within the browser releases are also supported? Since FF and Chrome are updating themself automatically, my FF is e.g. 35.0.1. Or to be more generally: how can I found out if my current NW resp Portal version is matching a browser? In my case: EP 7.31 SP14 + latest patches is working well with FF 35.0.1 and Chrome 40.

    2.)I remember we talk about this in short years ago, but to be sure: custom frameworks and custom application are not guaranteed to run well, right? My customer is using custom parts of AJAX framework (masthead) and mainly FPM applications. Im noticing some errors in rendering resp divergences comparing to IE, I guess we will not get any OSS support on this, right?

    Thank you very much,


    • Hi Lawrence,

      Thanks for you questions!

      1) For Firefox and Chrome, always the latest releases are supported (Firefox Extended Support Release and Rapid Release Cycle). You can find the required SPs in the Product Availability Matrix for the corresponding product version under

      E.g. for NW 7.40, the slides: 7, 11, 13 may be interesting for you:

      2) In general the SAP standard Portal is supported with FF and Chrome. But customer modifications are not supported. This may get quite complex and offers space for well specialized and good consultants. 😉

      Kind Regards, Andreas

      • Hi Andreas,

        thank you very much for your quick reply, this helps a lot.

        >E.g. for NW 7.40, the slides: 7, 11, 13 may be interesting for you:

        yes, I took a look at already initially, but missed input for FPM e.g. But since FPM is in fact based on WDA, I will assume FPM in EP is also supported. The rest should be simple: all SP stands bigger as x, are supported by NW for Chrome and FF, like PAM is mentioning. So there is nothing beside the PAM we need to know

        >This may get quite complex and offers space for well specialized and good consultants. 😉

        I got you, we will work on this 🙂

        Thank you again for your friendly support,

        best regards from Bern