Closed Bug 1124366 Opened 11 years ago Closed 9 years ago

The input box high growing should keep the same place visible of a conversation by pushing up

Categories

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

defect

Tracking

(tracking-b2g:backlog, b2g-v1.4 unaffected, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)

RESOLVED WONTFIX
tracking-b2g backlog
Tracking Status
b2g-v1.4 --- unaffected
b2g-v2.0 --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected
b2g-master --- affected

People

(Reporter: NicolasWeb, Unassigned)

Details

(Keywords: regression, Whiteboard: [sms-most-wanted])

Attachments

(3 files)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 Build ID: 20150112203352 Steps to reproduce: 1. open a message conversation 2. start writing a multi line message Actual results: at every new line you compose, more of the bottom of the conversation is overlayed (hidden behind compose input box). Expected results: compose input box should keep visible the same bottom-of-conversation when growing/decrease. it should adapt like it do when you first click on it and push up the conversation part (not overlay it).
Thanks for this bug, you're definitely right, it's how it's supposed to work, and I'm quite sure this is a regression. Asking 2.2 blocking status even if the regression is likely old.
Status: UNCONFIRMED → NEW
blocking-b2g: --- → 2.2?
Ever confirmed: true
Keywords: regression
Whiteboard: [sms-most-wanted]
I agree : it's a regression since it wasn't the case in FFOS 2.0 as show this screen captures.
not sure if good first bug applies to FFOS, but trying...
Whiteboard: [sms-most-wanted] → [sms-most-wanted] [good first bug]
QA: can you please test this in a 2.1 build? Asking for a regression window too, this might help finding an easy fix. Nicolas, "good first bug" applies to FFOS but I don't know yet if this would be easy enough for a new contributor, so I'm removing this flag for now.
status-b2g-v2.1: --- → ?
Whiteboard: [sms-most-wanted] [good first bug] → [sms-most-wanted]
QA Contact: ychung
This issue also reproduces on Flame 2.1. Result: The input field overlays the previous messages as the user composes a multi-line message. Environmental Variables: Device: Flame 2.1 BuildID: 20150121143637 Gaia: 2055fc40a8bd2af1908979cb45da6b7d1c4ced0b Gecko: 38ac70ca969b Version: 34.0 (2.1) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 -------------------------------------------------- I will work on the regression window next.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qawanted
This issue DOES reproduce on Flame 2.0, V18D-1 Base Image (2.0), and V188-1 Base Image. Result: The input field overlays the previous messages as the user composes a multi-line message. Environmental Variables: Device: Flame 2.0 (319mb, KK, full flash) BuildID: 20150121092732 Gaia: 736933b25ded904f0cb935a0d48f1f3cf91d33ad Gecko: 296e19e6edcb Version: 32.0 (2.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Also the attachment in Comment 3 looks like v1.4 rather than v2.0 judging by the UI. This issue DOES NOT reproduce on the latest Flame 1.4. Result: The input field does not overlay the previous messages as the user composes a multi-line message. The previous messages scroll up as the input field expands. Environmental Variables: Device: Flame 1.4 (319mb, JB, shallow flash). BuildID: 20150120212631 Gaia: 04265f42139a7a5c611c45e4869582642927e835 Gecko: e8306da2cbc1 Version: 30.0 (1.4) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Therefore, it is a regression from v1.4 to v.2.0. Unable to provide regression window.
Attached image 2.0_Messages.png
The attachment is what I see from Flame 2.0.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
> I agree : it's a regression since it wasn't the case in FFOS 2.0 as show > this screen captures. > Also the attachment in Comment 3 looks like v1.4 rather than v2.0 judging by > the UI. This issue DOES NOT reproduce on the latest Flame 1.4. Sorry I made a mistake : attachement 8553013 is FFOS 1.3 I'm running FFOS 2.0 that is affected to report this bug.
Attachment #8553013 - Attachment description: UI without input high issue in FFOS 2.0 → UI without input high issue in FFOS 1.3
triage: we lived with it for many releases. it's not breaking functionality, so decision is not to block. We would like it to fixed and request uplift though.
blocking-b2g: 2.2? → backlog
I may be wrong, but 1.3 and 2.0 only were released in devices to users. It seems *they* didn't lived with it for many releases, but only with the last one. I think that for them, it's a new regression. Still happy that this will be fixed :-)
Flags: needinfo?(whuang)
Understood. I have no doubt that we want it to be fixed. It's not necessary to mark blocker in order to fix. Since this isn't really breaking functionality, I think we shouldn't block on it.
Flags: needinfo?(whuang)
blocking-b2g: backlog → ---
Priority: -- → P1
Mass closing of Gaia::SMS bugs. End of an era :(
Status: NEW → RESOLVED
Closed: 9 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.

Attachment

General

Created:
Updated:
Size: