Clarity

Expand all | Collapse all

14-2 issues with latest Firefox Release? (40.0.3)

  • 1.  14-2 issues with latest Firefox Release? (40.0.3)

    Posted Aug 28, 2015 07:30 AM

    Hi guys,

     

    today our developers cannot access our Development 14-2 environment using Firefox. They just get a white screen when they enter the URL.

    The application opens fine in IE and Chrome.

     

    I noticed that Firefox released a new version (40.0.3) yesterday and I'm wondering if that is causing the problem? Have any others encountered  similar issues?



  • 2.  Re: 14-2 issues with latest Firefox Release? (40.0.3)

    Posted Aug 28, 2015 07:36 AM

    Can you ask them to clear the caches and then see if the issue still persiste.

     

    Ask them to clear any history on the firefox.

     

    Also, ask them to access %temp% from the run command, clear any caches.

     

    This should help

     

    NJ



  • 3.  Re: 14-2 issues with latest Firefox Release? (40.0.3)

    Posted Aug 28, 2015 08:19 AM

    I'm using Firefox and so far all is ok, I'm agree with NJ seem be environmental issue.



  • 4.  Re: 14-2 issues with latest Firefox Release? (40.0.3)

    Posted Aug 28, 2015 08:23 AM

    Thanks guys,

     

    I don't have Firefox myself so cannot test. I have forwarded your suggestions to one of the Developers to try.

    I'll let you know how this goes.



  • 5.  Re: 14-2 issues with latest Firefox Release? (40.0.3)

    Posted Aug 28, 2015 09:05 AM

     

     

    Have a nice weekend !

     

    NJ



  • 6.  Re: 14-2 issues with latest Firefox Release? (40.0.3)

    Posted Aug 28, 2015 02:00 PM

    I don't have such problem.

     

    Are your developers accessing CA PPM locally or through a slow problematic network connection?



  • 7.  Re: 14-2 issues with latest Firefox Release? (40.0.3)

    Posted Aug 28, 2015 05:51 PM

    Hi,

     

     

    I have experience the same issue, but with Internet Explorer 11 on Windows 8.1.

     

    Tried flushing cache, deleting temporary files, cookies, resetting ie, etc.

     

    Several users experience the same behaviour.  And for all of us, this strange workaround workds:

    1. When you have the white screen:

    2. open up the "Developer Tools" by pressing F12

    3. Do a simple refresh F5

    4. Close the "Developer Tools" by pressing F12

     

    Firefox eqvivalent would be to open the "Debugger" - <ctrl><shift><s>

     

    It would be interresting to hear your how you solve this.

     

    Good luck.

     

     

    Knut



  • 8.  Re: 14-2 issues with latest Firefox Release? (40.0.3)

    Posted Aug 31, 2015 10:55 AM

    Hi Knut,

     

    thank you for your suggestion. I asked one of the developers to try your workaround but the issue remains.

     

    They have also tried the usual deleting cache, cookies, history etc.

    It is very strange - they can access our other environments (Sandbox/Stage/Production) without any problems in Firefox. The only difference is that the Dev environment is on version 14-2.



  • 9.  Re: 14-2 issues with latest Firefox Release? (40.0.3)

    Posted Aug 31, 2015 12:46 PM

    Hi,

     

    I have been looking some more at our issue.  We have done som modifications to the UI-theme.  When I change the UI-theme back to the CA default, it seems we don't have the issue with the white page.  I think we have to look more closely at our modifications. :-)

     

    Not sure if this is relevant for you, but it's worth a try! :-)

     

    Knut



  • 10.  Re: 14-2 issues with latest Firefox Release? (40.0.3)

    Broadcom Employee
    Posted Aug 31, 2015 02:11 PM

    Hi Colin,

     

    I second Knut's suggestion : we have seen similar issues before.

    Could you try using one of our CA default Themes and see if it works? If yes, please check with your developers to adapt the custom Theme to Firefox.

     

    Regards

    Nika



  • 11.  Re: 14-2 issues with latest Firefox Release? (40.0.3)

    Posted Sep 01, 2015 08:33 PM

    Hi,

     

    You can try to open a "New Private Window" on Firefox to see if it works.

     

    They can't access the login page, right?

     

    The Clarity url is http or https?

     

    You can ask them to open the Network tab on Developer Tools on Firefox and Chrome, and compare if in both browsers the same HTTP requests are being made. This information can help you to locating the root of the problem.

     

    They can also check on the Developer Tools if a javascript or network error is happening.

     

    Regards,

    Roberto Barra



  • 12.  Re: 14-2 issues with latest Firefox Release? (40.0.3)

    Posted Sep 07, 2015 09:04 AM

    We tried reverting to a default there from Clarity but the issue remains.

     

    It's correct, users cannot access the login page. The URL is https:

     

    It's strange because for a time last week it seemed to work ok, but all of a sudden today it's gone back to a blank screen.



  • 13.  Re: 14-2 issues with latest Firefox Release? (40.0.3)

     
    Posted Sep 04, 2015 03:10 PM

    Hi Colin - Were you able to find a resolution using any of the suggestions provided? If so please mark Correct Answer as appropriate. Thanks! Chris



  • 14.  Re: 14-2 issues with latest Firefox Release? (40.0.3)
    Best Answer

    Posted Sep 23, 2015 07:18 AM

    Hi guys,

     

    a quick update on this.

     

    I established that our 14.2 Stage environment was having no issues with display in Firefox.

    So then I used the 'Inspect Element' feature on Firefox, comparing the problematic Dev version with the working Stage version.


    I noted a couple of parenthesis errors in the HTML files located: D:\niku\clarity\webroot\ui\uitk\gwt\com.ca.clarity.container

    in my problematic version


    So I corrected these, restarted all services and cleared my Firefox browsing history.

    After this, the display is appearing fine.


    It seems that Firefox is a lot more unforgiving than other browsers when it comes to handling errors/warnings.


    Thanks a lot for your help and advice with this one.