Closed Bug 863335 Opened 11 years ago Closed 11 years ago

Download Update via data screen update

Categories

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

All
Other
defect

Tracking

(blocking-b2g:tef+, b2g18 fixed, b2g18-v1.0.1 fixed)

VERIFIED FIXED
blocking-b2g tef+
Tracking Status
b2g18 --- fixed
b2g18-v1.0.1 --- fixed

People

(Reporter: epang, Assigned: arnau)

References

Details

(Keywords: polish, Whiteboard: visual design, UX-P1, yedo)

Attachments

(3 files, 1 obsolete file)

Attached image Download via data mock ups (obsolete) —
Pavel,

I've created a mock up for layout and font updates for this screen.  Also note that I've removed the download icon.  Can you work on this? Let me know if you have any questions, thanks!
Attached file Font Specs
QA Contact: jsmith
tracking-b2g18: --- → ?
Assignee: pivanov → arnau
Eric, why are we using a padding of 25px for the divider instead of 15px? we're using 15px everywhere else on the device. Is this a special case? 

Thanks!
(In reply to Sergi from comment #2)
> Eric, why are we using a padding of 25px for the divider instead of 15px?
> we're using 15px everywhere else on the device. Is this a special case? 
> 
> Thanks!

Hi Sergi,  I've been using the Specs from the wiki:
https://wiki.mozilla.org/File:OWD_00_Confirm_Sample.jpg

The confirmation screens on the wiki have 25px margins for the div lines and a left margin of 30px for the text.  

Let me know if this is incorrect.  If so, can you point me to a final spec I can follow.

Thanks!
Flags: needinfo?(sergiov)
I'm afraid that's incorrect. I've updated it in the wiki:https://wiki.mozilla.org/Gaia/Design/BuildingBlocks#Confirm

Do you want me to replace the sample you provided in this bug?

Thanks!
Flags: needinfo?(sergiov)
Hi Sergi, 
Looks like my browser was caching and I was looking at the outdated specs, sorry!

Now i see the specs:

15px padding for div liens
30px padding for text

Is this something we can update in the building blocks to make all screens of this type consistent?  Let me know if it's possible...i hope it is!

Thanks!
Yes. I think it won't be a problem. 

I'm adding Arnau to the conversation and will also talk with him offline to get this done asap.

Thank you very much Eric
Flags: needinfo?(arnau)
(In reply to Sergi from comment #6)
> Yes. I think it won't be a problem. 
> 
> I'm adding Arnau to the conversation and will also talk with him offline to
> get this done asap.
> 
> Thank you very much Eric

No Problem, for now I'm updating any mock ups I've created within the last couple of weeks that have not yet been worked on with the new building blocks (15px padding).  Will attach one here shortly too :).  Thanks for bringing this to my attention Sergi!
Updated padding of div lines to 15px (to match revised building blocks)
Attachment #739151 - Attachment is obsolete: true
Attached file patch
Attachment #741294 - Flags: review?(igonzaleznicolas)
Flags: needinfo?(arnau)
Info for reviewers:
css in bb/value_selector.css was overwriting values in Confirm Building block.
I have added data-type="value-selector" to avoid it, and also removed unneeded styles in style/modal_dialog/prompt.css and style/update_manager/update_manager.css.
Comment on attachment 741294 [details]
patch

Everything looks fine to me :D
Attachment #741294 - Flags: review?(igonzaleznicolas) → review+
Comment on attachment 741294 [details]
patch

CSS only change, r=me.
Attachment #741294 - Flags: review?(alive) → review+
Comment on attachment 741294 [details]
patch

NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.

[Approval Request Comment]
Bug caused by (feature/regressing bug #): 
User impact if declined: incorrect layout visualization
Testing completed: yes
Risk to taking this patch (and alternatives if risky): low, only CSS changed
String or UUID changes made by this patch:
Attachment #741294 - Flags: approval-gaia-v1?
Attachment #741294 - Flags: approval-gaia-v1?
Nominating tef? as his duplidated is tef+
blocking-b2g: --- → tef?
blocking-b2g: tef? → tef+
tracking-b2g18: --- → ?
Can we please close the bug and also put in the commit of when it was committed?

Committed : 
Apr 26, 2013
https://github.com/rnowm/gaia/commit/e69553c36894979e0be587fe2b172a8b6795d803

This was put in a while ago to master.

Verified on : 
Build ID : 2013-04-30-03-10-46
"mozilla-central" revision="dd0c611a0a27"
"gecko.git" revision="0050771e43cf27a7728710c0bbf44035528dc341"
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #16)
> Can we please close the bug and also put in the commit of when it was
> committed?
> 
> Committed : 
> Apr 26, 2013
> https://github.com/rnowm/gaia/commit/e69553c36894979e0be587fe2b172a8b6795d803
> 
> This was put in a while ago to master.
> 
> Verified on : 
> Build ID : 2013-04-30-03-10-46
> "mozilla-central" revision="dd0c611a0a27"
> "gecko.git" revision="0050771e43cf27a7728710c0bbf44035528dc341"

Thanks for verifying Naoki!
Arnau, can you request for an approval-gaia-v1 ?
Flags: needinfo?(arnau)
Oops sorry already requested in comment 14 (https://bugzilla.mozilla.org/show_bug.cgi?id=863335#c14)
Flags: needinfo?(arnau)
I already removed gaia-approval-v1 request last week as this is a tef+ bug.
Tef+ bugs don't need gaia-approval-v1+
Didn't know that thanks Maria.
I was not able to uplift this bug to v1-train and v1.0.1.  If this bug has dependencies which are not marked in this bug, please comment on this bug.  If this bug depends on patches that aren't approved for v1-train and v1.0.1, we need to re-evaluate the approval.  Otherwise, if this is just a merge conflict, you might be able to resolve it with:

  git checkout v1-train
  git cherry-pick -x  e69553c36894979e0be587fe2b172a8b6795d803
  <RESOLVE MERGE CONFLICTS>
  git commit
  git checkout v1.0.1
  git cherry-pick -x $(git log -n1 v1-train --pretty=%H)
(In reply to John Ford [:jhford] -- If you expect a reply from me, use needsinfo? instead of CC from comment #22)
> I was not able to uplift this bug to v1-train and v1.0.1.  If this bug has
> dependencies which are not marked in this bug, please comment on this bug. 
> If this bug depends on patches that aren't approved for v1-train and v1.0.1,
> we need to re-evaluate the approval.  Otherwise, if this is just a merge
> conflict, you might be able to resolve it with:
> 
>   git checkout v1-train
>   git cherry-pick -x  e69553c36894979e0be587fe2b172a8b6795d803
>   <RESOLVE MERGE CONFLICTS>
>   git commit
>   git checkout v1.0.1
>   git cherry-pick -x $(git log -n1 v1-train --pretty=%H)

Arnau, can you please look into this? Thanks!
Flags: needinfo?(arnau)
Cherrypicking done! Thanks
Flags: needinfo?(arnau)
v1.01 3e232bce289c9e156d92553e752616cba284bc8f
v1-train b0aca0dd1e2955e11190ede725e1fb9ee596438b
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: