Created attachment 8680881 [details] logcat_pin-menu-open.txt Description: If the user selects the Pin option in the browser overflow menu while a website is still loading, the Pin Menu page will take several seconds to appear. Depending on size of the website, load times can be over 5 seconds. This consistently occurs on the following websites: www.cnn.com www.kotaku.com www.polygon.com Note: The load time is longer on Flame, often reaching 10+ seconds to load the Pin Menu Repro Steps: 1) Update an Aries to 20151029124810 2) In the Browser app, navigate to www.cnn.com 3) Right as the site begins to load, tap the ellipsis (...) and select Pin Actual: The Pin UI takes 5+ seconds to appear. Expected: The Pin UI takes <1 second to appear. Environmental Variables: Device: Aries 2.5 Build ID: 20151029124810 Gaia: 91cac94948094cfdcd00cba5c6483e27e80cb3b0 Gecko: acb3f4ac5424181d3d4d73283668162137918cf1 Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd Version: 45.0a1 (2.5) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:45.0) Gecko/45.0 Firefox/45.0 Repro frequency: 5/5 See attached: Video (URL), Logcat
This issue DOES occur on the latest Flame 2.5 master build. The Pin UI takes about 10 seconds to appear, significantly longer than on the Aries device. Environmental Variables: Device: Flame 2.5 (512MB) BuildID: 20151029045227 Gaia: 91cac94948094cfdcd00cba5c6483e27e80cb3b0 Gecko: acb3f4ac5424181d3d4d73283668162137918cf1 Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a Version: 45.0a1 (2.5) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:45.0) Gecko/45.0 Firefox/45.0 ************************************** Pin the Web is not implemented on the 2.2 branch.
QA Whiteboard: [QAnalyst-Triage?]
Priority: -- → P1
Whiteboard: [2.5-Daily-Testing][Spark] → [2.5-Daily-Testing][Spark][systemsfe]
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.