Pranoy - DPS909

   The bug I decided to fix for this release was a very quick and easy one.  It was to update the show more button.  It can be found here . It is not really a bug but it was a minor change that they wanted. Using devtools in the VSCode, it was very easy to figure out which file was the one that needed the change. It was in the  src/components/SecondaryPanes/CommandBar.css . The Line was changed to: mask : url ( / mc/command-chevron .svg ) no-repeat ; Since this was a fairly simple bug to fix, I went ahead and decided to learn more about how the project structure is. This would help me tremendously since I plan on working on the same project for the next release.

    For our release 0.2, we were tasked to find an open source project to contribute to. Initially my plan was to work on the Brave Browser that can be found here . But after looking at the bugs I wasn't able to find a good one to work on, and the ones I found seemed like they were fixed as I was not able to recreate those bugs on my system(I also tried them on a different OS and it still didn't work. Since this wasn't working out I decided to search other projects to work on and I stumbled across the Firefox Debugger.html . Debugger.html is simply a debugger built using React and Redux. It is similar to the developer tools that firefox provides, but the difference being it can be used it any browser. The project can be found at https://github.com/devtools-html/debugger.html   . While subscribed to this project I found out that the community was very helpful and there was a lot of communication among the main contributing developers. Their documentation can be found here

In this lab, our task was to fix a bug in the Brave Browser.  The bug was when a URL containing white-spaces in specific places were passed through the URL Bar the result would be much different than what the other browsers would produce. The first step in fixing the bug was to re-create the bug.  This was very simple as we just passed through a URL which contained spaced and behold the bug appeared. I also tried inputting the same URL's in other browsers such as Chrome and Firefox and this issue did not occur. So the tests that worked and the ones that didn't work in Brave are as follows. "dog" --> worked " dog " --> worked "dog cat" --> worked " dog cat " --> worked "https://www.google.ca/search?q=dog" --> worked " https://www.google.ca/search?q=dog " --> worked "https://www.google.ca/search?q=dog cat" -> Didn't work, it searches the link instead " https://www.googl

For this lab we were to contribute to the bridge-troll app and fix the issue-6.  This issue was the map didn't have a day/night feature.  This means while its dark outside the map would stay the same as it is during the day time which is very bright. Initially while working on the app it was very hard to get it working on a Windows environment. Due to this I had to use a Linux machine to fix the issue. As I was looking at solutions on how to get started on fixing the bug, I saw that in the issue description itself there was pretty much a solution given. This solution was to use suncalc which is an application that calculates the suns position and determines whether its dark or not.  This helped in figuring out the issue of what time the map should switch to the darker colored mode. The implementation of this code was fairly simple the below screenshots show the code added that checks the time. After checking the time the changing of the map was very simple.  I just a dif

For this lab we looked at the ECMAscript test suite. Setting it up and making it run was fairly simple and I didn't encounter any issues.  I just followed the steps provided in https://github.com/bterlson/test262-harness#test262-harness While running the tests not all of them pass. I thought this might have been a Windows issue. Therefore I tried it on my Linux machine and majority of it worked except 6. Then we looked at the test cases for Array.prototype.reverse().  For the task of this lab I simply just rewrote some new test cases to check the array.reverse.  This was fairly simple as looking at the other test cases it gave a general idea on how to write test cases for this. The test case I wrote can be found here. https://gist.github.com/pranoy10/10fd4bbf04a7490567d527017c8d52df

    For Lab 3, our task was to tackle an issue/bug with vscode.  While tackling bugs one of the first things we had to accomplish was to recreate the bug on our machines.  Initially this seemed like a very easy task, follow the steps mentioned in the issue to create the bug and BAM! you got something to work with right? NO.  This was never the case with us.  We tackled the issues listed on the wiki page and wasn't able to recreate most of them.    We tried the colour picker issue #42720, this seemed like it was a fixed issue.  I wasn't able to recreate it on my Linux system and we also tried to create it on a Windows system with no success.  Then we tried the Opening .bat files issue #43302, this was also a fail as we couldn't get the issue to come up.  Then finally giving up on the list provided we ventured out into the 4000+ issues listed on the vscode GitHub.  We filtered for the labels good first issue and bug and found one that we decided to tackle.  We decided to