Clarity

Expand all | Collapse all

Clarity 13.3 Timesheet issue with Google Chrome browser

Jump to Best Answer
  • 1.  Clarity 13.3 Timesheet issue with Google Chrome browser

    Posted 07-28-2015 12:23 PM

    Hello,

     

    We are experiencing an issue where the Clarity timesheets are not displaying correctly with the Google Chrome browser. There are days that are not open for entering time on certain time periods, but not all of them. These days display correctly on Firefox and IE and are open for entry. Chrome is also not displaying the timesheet correctly once the period has been submitted. The days header and the columns below are not aligned, with the columns shifted over to the right. We are using the newest version of Chrome right now, 44.0.2403.107 m. Could there be something that has broken with the new version? Has anyone seen this before?

     

    Here 7/20 and 7/21 should be open:

    Timesheet Clarity Chrome 1.png



  • 2.  Re: Clarity 13.3 Timesheet issue with Google Chrome browser

    Broadcom Employee
    Posted 07-28-2015 06:50 PM

    What is the zoom percentage of the page?

    Reset it to 100%

    Are you using one of the standard UI Themes?

    If not, reset to a standard theme and clear the browser caches.



  • 3.  Re: Clarity 13.3 Timesheet issue with Google Chrome browser
    Best Answer

    Posted 07-29-2015 01:16 PM

    It looks like it was mostly cached data that needed to be refreshed. Most issues cleared up by themselves. Thanks everyone!



  • 4.  Re: Clarity 13.3 Timesheet issue with Google Chrome browser

    Posted 07-29-2015 06:56 AM

    Hi,

     

    I'm using chrome 44.0.240.107m, with 13.3 and I do not have the problem.

    Is this consistent for all users? or just one?

     

    Do you have any plugins that the organisation uses?

    check under settings ---> extensions

    disable everything



  • 5.  Re: Clarity 13.3 Timesheet issue with Google Chrome browser

    Posted 07-29-2015 07:49 AM

    I will also confirm that I have also checked and did not find any issues with it.