Closed
Bug 960039
Opened 10 years ago
Closed 10 years ago
Remove unused `charging` attribute from status bar
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Firefox OS Graveyard
Gaia::System
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: me, Assigned: me)
Details
(Whiteboard: [mentor=timdream][lang=js])
Attachments
(1 file)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 20140110030650 Steps to reproduce: Look at the markup for status bar. Actual results: Noticed non-standard and apparently not used `charging` attribute. Expected results: There should be no `charging` attribute.
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8360388 -
Flags: review?(21)
Attachment #8360388 -
Flags: review?(21) → review?(timdream)
Comment 2•10 years ago
|
||
Comment on attachment 8360388 [details] [review] Patch Hi, the patch looks good, however you need to rebase your branch before I could merge it. Please do the following to update your pull request: git checkout master git remote add upstream https://github.com/mozilla-b2g/gaia.git # assuming you haven't done so. git pull upstream master git checkout remove-charging-attribute git rebase master <resolving conflict, following screen direction> git push -f origin remove-charging-attribute
Attachment #8360388 -
Flags: review?(timdream) → feedback+
Updated•10 years ago
|
Assignee: nobody → me
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Updated•10 years ago
|
Whiteboard: [mentor=timdream][lang=js]
Assignee | ||
Comment 3•10 years ago
|
||
Thanks for review Tim! I pushed the rebased version.
Comment 4•10 years ago
|
||
Comment on attachment 8360388 [details] [review] Patch Looks good! I will merge the commit after Travis CI come back green.
Attachment #8360388 -
Flags: review+
Comment 5•10 years ago
|
||
master: https://github.com/mozilla-b2g/gaia/commit/fecb15413917f16938a4963157584568d7d19017
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•