Closed Bug 990518 Opened 11 years ago Closed 10 years ago

[Messaging][Visual Refresh] Keyboard suggestions should update messaging composer layout.

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: borjasalguero, Unassigned)

References

Details

(Whiteboard: [p=2] [priority])

Attachments

(2 files)

With the new Visual refresh we need to update the composer with the following: - Composer style should update with the requirements detailed in the link: https://dl.dropboxusercontent.com/u/346211/FxOS/Messagin_Composer_Keyboard_Suggestion.png - Composer should take the whole available space This should be controlled via an observer to the setting related with 'keyboard suggestions' or other equivalent way.
Depends on: 949457
Summary: [Messaging][Visual Refresh] → [Messaging][Visual Refresh] Keyboard suggestions should update messaging composer layout.
I Attached image in the bug, because I deleted from Dropbox ;)
Assignee: nobody → joan.leon
Target Milestone: --- → 2.0 S2 (23may)
blocking-b2g: --- → backlog
feature-b2g: --- → 2.0
Really, I don't think we'll be able to do something different with/without word suggestions (or maybe we'll need to look at the keyboard settings, and it feels bad :( ) _but_ we should still be able to control the composer max-height using the "vh" unit (say: .4vh) that would be good enough and would adapt to all situations. Plus a special case for the "composer" view.
If we have access to the settings to see, if the keyboard suggestion is active, just add a class
The problem is that even if the setting is active, the suggestion part of the keyboard is not always enabled, depending on where the focus is.
But "vh" refers to the height of the device, which does not change with or without "Word Suggestion".
vh is the height of the _viewport_, which changes because the SMS app is resized accordingly, depending on the keyboard size.
I see that in master is already fixed this bug o_O Julien, if you can check this, and you close this patch for address the issue of vh in another bug.
Flags: needinfo?(felash)
Look at comment 0, the requirements are still not there. BTW this bug was created as a follow-up to bug 949457.
Flags: needinfo?(felash)
Hi Julien, It seems keyboard suggestion is already appearing as specified. Do you mind to use this bug for tracking that and open a new bug to cover the pending composer layout work if needed?.
Flags: needinfo?(felash)
Noemi, this bug is not to make the keyboard suggestion appear or not. See comment 0 more precisely :) This bug is to: * implement attachment 8419274 [details] (and I don't think it's really possible actually, or I miss something) * have the composer take the available space as specified (which should be really possible). Borja filed this bug when he removed the JS-based calculations for the max-height in bug 949457. The goal of this bug was to put the max-height back using CSS only. I'm removing Joan as the assignee as I get he has a lot of work, so that someone can pick this up next sprint ;)
Assignee: joan.leon → nobody
Flags: needinfo?(felash)
Keywords: regression
Target Milestone: 2.0 S2 (23may) → 2.0 S3 (6june)
Filed bug 1015867 for the "composer take the available space" part.
Discussed with the team, implementing attachment 8419274 [details] is possible but takes some work for a small improvement, so we keep it out of the current sprint.
Keywords: regression
Target Milestone: 2.0 S3 (6june) → 2.0 S4 (20june)
Whiteboard: [p=2]
blocking-b2g: backlog → 2.0?
feature-b2g: 2.0 → ---
triage: nice to have for 2.0
blocking-b2g: 2.0? → backlog
Whiteboard: [p=2] → [p=2] [priority]
Flagging Wilfred and Victoria to ensure they know about and agree with triage decision to mark this nice to have for 2.0, in which case it would no longer be blocking the Comms refresh.
Flags: needinfo?(wmathanaraj)
Flags: needinfo?(vpg)
It looks buggy but if it requires too much work, don't block the VR.
Flags: needinfo?(vpg)
Flags: needinfo?(wmathanaraj)
Target Milestone: 2.0 S4 (20june) → ---
What is the latest status on this? Please let me know if this will make 2.0 or if we should backlog it for a later release, so we can close out the visual refresh for 2.0. Thanks!
Nope, this won't happen in 2.0.
Hey Zhenshuo, I'd like to know if you still want this for the SMS app. Thanks !
Flags: needinfo?(zfang)
I don't think Zhenshuo worked on this, and she has left Mozilla as of Friday. Flagging Carrie to see if this is still desired for SMS.
Flags: needinfo?(zfang) → needinfo?(cawang)
This was a Visual Design request, not a UX request, that's why I flagged Zhenshuo on this. Who's doing the Visual Design for SMS now?
Flags: needinfo?(mtsai)
Ni? our UX designer Omega and Visual designer Carol for feedback. Thank you.
Flags: needinfo?(ofeng)
Flags: needinfo?(mtsai)
Flags: needinfo?(chuang)
Julien, Fang is your partner on Visual for SMS : ) Since previous comments indicated that it won't be available in 2.0 , the space should be 5px and we will adding adding an attach button in the ui. ni? Fang to upload latest design and spec for verification. Thank you.
Flags: needinfo?(ofeng)
Flags: needinfo?(fshih)
Flags: needinfo?(chuang)
Flags: needinfo?(cawang)
Attached image Spec_SMS_Compose.png
Attached is the latest spec for SMS compose view. The space should both be 5px (0.5 rem) either with word suggestion or not, which is what I've seen in the current build already. Let me know if there is anything I didn't cover. Thanks!
Flags: needinfo?(fshih)
Hey Fang, Actually, I wanted to know what you want it to be in v2.1. Is the 5px space good for you, or do we want to update the space depending on the keyboard suggestion, as originally planned?
Flags: needinfo?(fshih)
Hi Julien, Thanks for confirming. 5px space is good, We don't want to update the space anymore. Let it stay the same. Thanks!
Flags: needinfo?(fshih)
Then it's a WONTFIX. THanks Fang !
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: