Closed Bug 825166 Opened 9 years ago Closed 9 years ago

[CONTACTS][es] Contact details are not shown correctly

Categories

(Firefox OS Graveyard :: Gaia::Contacts, defect, P3)

x86_64
Windows 7
defect

Tracking

(blocking-basecamp:+)

VERIFIED FIXED
B2G C4 (2jan on)
blocking-basecamp +

People

(Reporter: carlosmartinez, Assigned: vingtetun)

References

Details

(Keywords: regression, smoketest, Whiteboard: interaction, UX-P1)

Attachments

(2 files)

Tested in unagi with:

Gecko - b8d7310
Gaia - 73270c3

STR:
1-Add a new contact filling all the fields
2-Try to edit it

Expected result --> You enter in contact edit mode and you´re able to edit every field 

Actual result --> You get the screen you can find in the attachments
blocking-basecamp: --- → ?
Expected result is incorrect, you should get to contact details, but you cannot see them.
Summary: [CONTACTS] Edit mode is not working fine, a strange screen is shown before you can get to edit mode → [CONTACTS] Contact details are not shown correctly
Triage: BB+, C4, P3 - maybe due to localization in Spanish?
blocking-basecamp: ? → +
Priority: -- → P3
Target Milestone: --- → B2G C4 (2jan on)
QA can you check if this happens only for spanish? Or if it is on all locales?
Keywords: qawanted
Summary: [CONTACTS] Contact details are not shown correctly → [CONTACTS][es] Contact details are not shown correctly
Still waiting for the 12-28 build to come out, but using the 2012-12-27-23-02-02 later build I do not see this in English. Trying Spanish next.
I´ve retested this with English (US) and is working fine.
https://github.com/mozilla-b2g/gaia/commit/3eadb55a7c182803a4e36a1853a1b8305adbb987

I have backout the fix that has created the issue and I have reopened it.
Assignee: nobody → 21
Status: NEW → RESOLVED
Closed: 9 years ago
Depends on: 820145
Resolution: --- → FIXED
As far as I can tell, all languages are working in the 12/28 nightly. I'm unable to reproduce what Carlos posted in the screen shot.
Its technically fixed, cause we had to back out a change. But the bug really is... that the content area breaks when the header label is longer. We need to make a change to the header "edit" action. So this needs to be fixed.
Blocks: 820145
Status: RESOLVED → REOPENED
No longer depends on: 820145
Resolution: FIXED → ---
Whiteboard: interaction, UX-P1
Attached image contact detail
(In reply to Patryk Adamczyk [:patryk] UX from comment #8)
> But the bug really
> is... that the content area breaks when the header label is longer. 

That's the part I'm not seeing in today's build. Maybe there are different steps that I'm missing.
(In reply to Dylan Oliver [:doliver] from comment #9)
> Created attachment 696382 [details]
> contact detail
> 
> (In reply to Patryk Adamczyk [:patryk] UX from comment #8)
> > But the bug really
> > is... that the content area breaks when the header label is longer. 
> 
> That's the part I'm not seeing in today's build. Maybe there are different
> steps that I'm missing.

Since I have reverted the fix that has created this you can not see it anymore.
Removing QA wanted since Carlos tested and commented.
Keywords: qawanted
From a product perspective, bug 820145 is a blocker, this bug will need to be fixed. 

This is already marked blocking so we should keep it.  Plus, Dylan has repeatedly said he cannot reproduce this so we need to figure out the repro steps here.
Duplicate of this bug: 825951
(In reply to Chris Lee [:clee] from comment #12)
> From a product perspective, bug 820145 is a blocker, this bug will need to
> be fixed. 
> 
> This is already marked blocking so we should keep it.  Plus, Dylan has
> repeatedly said he cannot reproduce this so we need to figure out the repro
> steps here.

Chris if Dylan says he can not reproduce this is because I have revert the patch that is the root cause of this bug. Let's not create any confusion anymore and let's close this bug and make sure to fix it / not create it again in the fix that will be done by bug 820145.
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
Chris what do you think about Vivien answer. Do you want to take the risk of changing code in many files ?

Vivien could you estimate LOE and Risk please.
Flags: needinfo?(clee)
Flags: needinfo?(21)
Status: RESOLVED → VERIFIED
Flags: needinfo?(clee)
Flags: needinfo?(21)
You need to log in before you can comment on or make changes to this bug.