If this is your first contribution, please see our onboarding guide: https://wiki.mozilla.org/WebExtensions/Contribution_Onramp

Hello!

Can I give it a try to solve this bug?

I am new to Mozilla and trying to contribute for Outreachy 2019.

Hey Pankhuri, welcome! This bug's all yours. :)

Just a quick heads up: the WebExtensions team doesn't have a project for Outreachy Summer 2019. If you could email me at cneiman@mozilla.com and let me know which project(s) you are interested in, I can try to direct you to those project mentors.

hey Caitlin, I wanted to ask Isn't new certificate viewer for Firefox is the project for outreachy 2019. And This is one of the bug firefox-frontend given on outreachy site.

(In reply to lekhikadugtal from comment #9)

hey Caitlin, I wanted to ask Isn't new certificate viewer for Firefox is the project for outreachy 2019. And This is one of the bug firefox-frontend given on outreachy site.

Hey Lekhikadugtal! Yes, you are right -- I learned after I made comment #8 that the mentor of the new certificate viewer for Firefox project is encouraging applicants to contribute to any Firefox-frontend bug as part of the application process. :) So you are in the right place!

Hello Caitlin,
Can I be work on this bug? I am an outreachy applicant.

(In reply to afshan.shokath from comment #11)

Hello Caitlin,
Can I be work on this bug? I am an outreachy applicant.

Let's just confirm that Pankhuri and lekhikadugtal aren't planning on working on it. :) Pankhuri & lekhidagtal, can you confirm?

I'm working on different bug. Thanks for asking Caitlin :).

Thank you, lekhikadugtal! I talked to Pankhuri offline and it looks like they are working on another project.

Afshan, this bug is all yours! \o/ The bug mentor is on PTO until March 11 so please needinfo me if you need any help and I'll help connect you with another mentor. :)

(In reply to Caitlin Neiman [:caitmuenster] from comment #14)

Thank you, lekhikadugtal! I talked to Pankhuri offline and it looks like they are working on another project.

Afshan, this bug is all yours! \o/ The bug mentor is on PTO until March 11 so please needinfo me if you need any help and I'll help connect you with another mentor. :)

Thank you so much. I will start working on it. Can you please change the status of this bug as assigned to me?

Hello Caitlin,
so apparently removing the add-on with 'remove' button from Extensions view doesn't update AM page automatically. Should I file this as a new bug?

Hey Andrew,
I am the one who is assigned to this bug and who had mailed you. I will communicate from here now onwards.
Like I said in the mail, I have been able to reproduce the bug and now I am looking at the source code.

So, this problem persists even when an add-on is installed from Add-ons->Get Add-ons not just when it is installed from website

The component it is supposed to render is the result of html's 'progress' tag when the attribute-value is status='installing' of the <html:progress> tag in the xul file.

When the class='progress' where progress being the css class is removed then it renders correctly.

How do I share images here?

Hey Afshan, I am sorry for being so late getting back to you. We reviewed this issue and realized it's a wontfix. The code affected is the XUL version of about:addons, and we're currently in the process of rewriting it into HTML.

I know closing this bug affects your Outreachy application. :( I'd encourage you to pick up another front-end good-first-bug. Here's a list of them: https://codetribute.mozilla.org/projects/ff?tag%3Dgood-first-bug

Good luck with your application!

Hey,
I spent days working on it. The deadline is just 5 days away and I don't know what do now. This is seriously not OK for me since all-good bugs are taken already and I am new to contributing.

(In reply to afshan.shokath from comment #21)

I spent days working on it. The deadline is just 5 days away and I don't know what do now. This is seriously not OK for me since all-good bugs are taken already and I am new to contributing.

If you're close to having a working patch, we can still accept it. I just want to make it clear though, that the current xul implementation of about:addons (which is the code that a patch for this bug would affect) is slated for removal in Firefox 69. If that's okay with you, you can still get the experience of getting your patch reviewed, landed, etc. If you're not close to having a patch ready for this bug, I would recommend finding a new bug.

To add to what aswan said, we've talked to the mentor for the project you're applying for and we can get you a good first bug.

Hi Afshan, I just opened up bug 1537535, would you like to take that one? If so, please add a comment to the bug.

Thanks!

Yes. I have did thank you.

(In reply to Caitlin Neiman [:caitmuenster] from comment #23)

To add to what aswan said, we've talked to the mentor for the project you're applying for and we can get you a good first bug.
Thanks a lot.