Steps to reproduce: 1. Sign in to AMO-stage page https://addons.allizom.org/en-US/firefox/ 2. Hover over the "user name" link and select "Account Settings" from the drop down list 3. Go to “Profile” section, click the “Choose Photo...” button and select a picture Expected results: There are no display or layout issues. Actual results: The “Choose Photo...” button and “use original” links are displayed on the right side of the profile picture. Notes/Issues: The “Choose Photo...” button is correctly displayed after the account changes are saved, but the “Delete current photo ” link is not. Verified on FF 34(Win 7). Issue is reproducing on AMO-stage, AMO-dev and AMO-prod . Screencast for this issue http://screencast.com/t/mtuGSJCSMkz
Whiteboard: [good first bug]
Please onboard to the AMO codebase before taking this bug. https://wiki.mozilla.org/Add-ons/Contribute/AMO/Code
I'd like work on this, I have completed the onboard process.
Assigned, feel free to ask questions if you need help!
Assignee: nobody → aniket.kudale
I m facing problem with setting up dev environment! I am new to docker, can any one please provide me docs which are not complicated to setup olympia dev environment on docker!
What are you having trouble with, Aniket? The olympia server install documentation  has instructions on how to get the dev environment running once you have docker setup. If you need to install docker then we recommend docker toolbox  if you are on OS X or Windows and regular docker  should work fine on Linux.  http://olympia.readthedocs.org/en/latest/topics/install-olympia/docker.html  https://www.docker.com/products/docker-toolbox  https://docs.docker.com/engine/installation/#installation
Product: addons.mozilla.org → addons.mozilla.org Graveyard
I have submitted a PR. Please have a look at it :)
The PR has been merged and I filed https://github.com/mozilla/addons-server/issues/3835 for a similar misalignment of the "use original" link on the photo picker.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.