Closed Bug 976494 Opened 10 years ago Closed 7 years ago

[Sora][Message][MMS]Can't display the newest message when enter a thread which include some MMS and SMS.

Categories

(Firefox OS Graveyard :: Gaia::SMS, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: sync-1, Unassigned)

Details

(Keywords: regression)

Firefox OS v1.3
 Mozilla build ID: 20140208004002
 
 DEFECT DESCRIPTION:
 ->MS can't display the newest message.
 
  REPRODUCING PROCEDURES:
 ->There is a mms message (more than 10 pages) in a thread,including media files and texts;
 ->Enter"Message",select the thread to enter in this mms message;
 ->MMS can't display the newest message, the slider dosen't stop at the bottom of the content.(ko)
 
  EXPECTED BEHAVIOUR:
 ->The slider of the mms should stop at the bottom of the content.
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:80%
 
  For FT PR, Please list reference mobile's behavior:Beetle lite FF can't reproduce.
Can someone confirm this on the Moz side?
Keywords: qawanted, regression
I'd like to know whether the view is not scrolled to the bottom, but _can_ be scrolled, or whether it can't be scrolled.

If it can't be scrolled at all, then it's a regression, otherwise it's always been like this (I think we have a bug about this, but I can't find it right now).
Flags: needinfo?(sync-1)
(In reply to Julien Wajsberg [:julienw] from comment #2)
> I'd like to know whether the view is not scrolled to the bottom, but _can_
> be scrolled, or whether it can't be scrolled.
> 
> If it can't be scrolled at all, then it's a regression, otherwise it's
> always been like this (I think we have a bug about this, but I can't find it
> right now).

The view is not scrolled to the bottom, but  can  be scrolled.
blocking-b2g: --- → 1.3?
Thanks, then it's known for a long time and is not a regression, unless it's more severe than what we used to have. It's not _that_ easy to fix (although we definitely need to fix it) because MMS are loaded in an asynchronous way, and not always displayed as we don't display always everything.

Maybe the key in this bug is the "more than 10 pages" precision: I also found this bug when the thread is quite loaded.

I'm keeping the bug opened because I can't find the older bug right now.
Flags: needinfo?(sync-1)
Keywords: regression
I think this is being misinterpreted. The reporter's testing already confirmed they can't repro this on Buri 1.1, so testing-wise, this is a confirmed regression. We're probably not understanding the bug correctly here.
Keywords: regression
Ok, I didn't understand the last line of the description, is it where they say it repros in 1.1?

From my side I'm quite sure this happens in 1.1 too but I accept this could be made worse by other work.
Per discussion with  田旻 , because this issue 1) only happens with long(about 10 pages)MMS, 2) user can still view the bottom of the MMS by manually scrolling down), we will keep watching this issue, but for now, remove 1.3?

Let me know if you think we should stay with 1.3?
blocking-b2g: 1.3? → ---
(In reply to Julien Wajsberg [:julienw] from comment #6)
> Ok, I didn't understand the last line of the description, is it where they
> say it repros in 1.1?
> 
> From my side I'm quite sure this happens in 1.1 too but I accept this could
> be made worse by other work.

This statement:

Beetle lite FF can't reproduce.

That means they couldn't reproduce it on the 1.1 Buri device.
I actually think this is a dupe of bug 952526 for the record.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Keywords: qawanted
I think it's different.

In Bug 952526, while in a thread view, we receive a message.
Here, while in the thread list, we enter a thread.

Completely different steps.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Mass closing of Gaia::SMS bugs. End of an era :(
Status: REOPENED → RESOLVED
Closed: 10 years ago7 years ago
Resolution: --- → WONTFIX
Mass closing of Gaia::SMS bugs. End of an era :(
You need to log in before you can comment on or make changes to this bug.