# Test Case STR 1. Launch the browser with blank page 2. input the google doc with 10 tables 3. close the browser # Hardware OS: Ubuntu 14.04 LTS 64-bit CPU: i7-3770 3.4GMhz Memory: 16GB Ram Hard Drive: 1TB SATA HDD Graphics: GK107 [GeForce GT 640]/ GF108 [GeForce GT 440/630] # Browsers Firefox version: 47 Chrome version: 51.0.2704.103 # Result Browser | Run time (median value) Firefox | 51878 ms Chrome | 39405 ms

Hello, I'm asking your help with an experiment with making decisions on bugs. You've been needinfo'ed on this bug. I'd like you to take one action to help this bug make progress toward a decision. The things you can do include: * If you know or have a good guess of which product and component this bug belongs to, change the product and component of the bug * If you know of the right person to ask about this bug, redirect the needinfo to them * If you cannot reproduce the bug, close it

We need a lot more info about this before we can entertain this process. Assuming we would try to do option 3: - do we need to reproduce using the same hardware/OS specs? native or VM? - we need more info about the STR: -- when do we start timing? when do we stop timing? -- are we already logged in? -- is the google doc already created -- is there any other typing into the doc? -- does the size of the table(s) matter? -- is this automated, or based on how fast I can use the cursor and UI? I'm guessing (though I do not know) that this is an attempt to expediently triage [qf:investigate] Core/General bugs, but option 3 is not viable without more information. And option 1 and 2 seem to be a larger problem. Is there anyone dedicated to looking at google docs related issues already? Should there be?

:dees, is there a good way contributors can help with these quantum flow related google docs bugs?

(In reply to Emma Humphries ☕️ (she/her) [:emceeaich] (UTC-8) +needinfo me from comment #3) > :dees, is there a good way contributors can help with these quantum flow > related google docs bugs? Naveed, Anthony and/or Andrew could best advise here. They are overseeing a lot of the triaging and engineering efforts with regards identified and prioritized QF issues.

(In reply to Emma Humphries ☕️ (she/her) [:emceeaich] (UTC-8) +needinfo me from comment #3) > :dees, is there a good way contributors can help with these quantum flow > related google docs bugs? Not really, no. The infrastructure setup and difficulty of reproducing hardware-specific numbers makes that not a good use of people's time. Thank you, though!

I spoke with Emma and we agreed these bugs aren't appropriate for [ele:1b]. These Quantum Flow tracker bugs will be dealt with separately. Thanks!