Closed Bug 1434809 Opened 6 years ago Closed 5 years ago

Google Spreadsheet "ProjectSheet planning" add-on's timescale change is 2-3x slower in Firefox than Chrome

Categories

(Core :: JavaScript Engine, defect, P3)

58 Branch
Unspecified
Windows
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr52 --- wontfix
firefox58 --- affected
firefox59 --- affected
firefox60 --- affected
firefox68 --- verified

People

(Reporter: cpeterson, Unassigned)

References

Details

I created this Google Spreadsheet using a free Google Spreadsheet add-on called "ProjectSheet planning". The add-on adds buttons and scripts to the spreadsheet. I don't know if you will need to install the add-on to reproduce this spreadsheet behavior or whether the add-on "sticks" to the spreadsheet. To install the add-on, open Add-ons menu > Get Add-ons > Search add-ons for "Gannt" and select "ProjectSheet planning"

STR:
1. Open this Google Spreadsheet:

https://docs.google.com/spreadsheets/d/1qtaDkyHHKz2JLY7zA_b7BB_LrFCK2Wi3-Zr3VZRs1bE/edit#gid=1533228141

2. Wait for the "ProjectSheet" sidebar to open on the right side of the page.
3. In the sidebar's "Set Gantt chart timescale" section, change timescale setting to "3 years per timescale" or back to "7 days per timescale".
4. Wait for the dates in rows 1 and 2 to change.

RESULT:

Simply loading the spreadsheet triggers a "A web page is slowing down your browser" warning. Changing the timescale takes 10-15 seconds and also triggers a "A web page is slowing down your browser" warning.

Changing the timescale in only takes about 5 seconds in Chrome and Edge.

Here is a link to a Gecko profile from Firefox Nightly 60:

https://perfht.ml/2GBInRI
_Lots_ of time is spent dealing with cross-compartment wrappers.
Component: General → JavaScript Engine
Whiteboard: [qf]
Priority: -- → P3

WFM in 68 Nightly. Switching the timescale takes about 5-7 seconds in both Firefox 68 Nightly and Chrome 73.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.