907064 - [Buri][IOT][Telenor] Latency when scrolling into firefox browser

Status: RESOLVED INVALID

(Core :: Graphics: Layers, defect, P3)

Description

[sync-1]

Mozilla build ID:20130806071254
 
 DEFECT DESCRIPTION:
 Most of the time there is latency when scrolling webpage.
 
 Step1: Go to a long webpage including many words
 Step2: Try to scrolling into this webpage
 Result: Each time end-user try to scroll up there is a part of the article which does not appear immediately he has to wait for a while before display it correctly. There is part of the screen who is blank during a while. After a while a error message appears. End-user has to reload the webpage
 
  REPRODUCING PROCEDURES:
 The displaying should be appears with no latency
 
  EXPECTED BEHAVIOUR:
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[sync-1]

Clone from brother

Comment 2

[sync-1]

Attachment: adb log

Comment 3

[Viga]

Attachment: Laggy

Comment 4

[Jason Smith [:jsmith]]

This looks bad performance wise, but this is likely not a 1.01 regression. This is a problem panning and zooming performance not being good on this target site. Given that this isn't a regression from 1.01 and we have no new perf requirements for 1.1, this isn't a blocker for 1.1. However, moving to koi, given that panning/zooming perf improvements is a 1.2 requirement.

Comment 5

[Joe Cheng [:jcheng] (please needinfo)]

in the video, www.lepoint.fr is desktop site which is not suitable for mobile devices
mobile.lepoint.fr is mobile site that should be returned instead of the desktop site
May file a mobile web compatibility bug so it's fixed on server side
https://bugzilla.mozilla.org/form.mobile.compat

Comment 6

[Ben Kelly [:bkelly, not reviewing]]

Based on comment 5 I opened evangelism bug 913590 and I'm marking this as a dupe.  Please reopen if you feel this is inappropriate.

Comment 7

[Ben Kelly [:bkelly, not reviewing]]

Reopened per Karl Dubost's request.

Comment 8

[Karl Dubost💡 :karlcow]

Following up on the discussion started on bug 913590

Thanks ben for reopening.

(In reply to Ben Kelly [:bkelly] from comment #3)
> Done.  Whats the correct way to handle bugs that are filed as performance
> issue, but it appears its due to a desktop site is being returned for a
> mobile device?  Thanks.

So basically, the issue is that there is a performance issue which is exhibited. The fact it is desktop or mobile doesn't matter. It is not even related to the site in question. The site is just an example of such a performance issue. 

The best to do usually in this case is to create a test case which reduces the context of the issue and attach it to the bug. The B2G dev team might choose to work on it or to close as WONTFIX. It is a valid business decision. 

Having and identifying performance issues is useful and should be recorded as such. :)

Comment 9

[Gregory Pappas [:gregp]]

Closing old B2G bugs