Amani-Alqaisi
commented
4 months ago Bug Report: Privacy Policy Parsing Issue
Issue #8 Assigned to: Mia Hines
Description: Clicking on certain website links to view their privacy policy summary results in incorrect parsing and display of information.
Reproduction Steps:
- Attempt to load the NY Times website.
- Expected: Unable to parse error. Seen: Can't find the link.
- Continuing from Step 1, add the link.
- Expected: Unable to parse error. Seen: Unable to parse error.
- Attempt to load the Grinnell College website.
- Expected: Can't find the link. Seen: Unable to parse error.
- Refresh the browser.
- Expected: Can't find the link. Seen: Can't find the link.
- Continuing from Step 7, add the link.
- Expected: Privacy policy summary. Seen: Unable to parse error.
- Attempt to load the Barnes & Noble website.
- Expected: Privacy policy summary for Barnes & Nobles. Seen: Privacy policy summary for Grinnell College.
Communication about Bug Status:
- 04/10: Initial report by Mia.
- 04/30: Investigating the issue.
- 04/30: Attempting potential solutions.
- 04/30: No progress yet. Seeking assistance from team member Liam.
- 04/30: Issue unsolved. Proposed solution under consideration.
Team Members Involved:
- Mia: Investigator, Debugger
- Liam: Helper, Debugger
[End of Bug Report]
Reproduction Steps
Each website, I attempted to run the Chrome Extension on is listed first in the bullet point.
Hypotheses about what the bug is
Journal Entries
The intention is to experiment with clicking to see the different console logs and errors on the front-end web. 4/30/24 4:30 PM Barnes & Noble. Load screen. Incorrect privacy policy. 4/30/24 4:31 PM Console logged the library received correctly but still the wrong entry. 4/30/24 4:35 PM Barnes & Noble. Load screen. Unable to parse. 4/30/24 4:35 PM Console log. Error with status 500 from the web server. 4/30/24 4:36 PM Barnes & Noble. Load screen. Unable to parse. Error with status 504 from the web server. 4/30/24 4:40 PM Grinnell College. Load screen. Find link. [Correct] 4/30/24 4:42 PM Grinnell College. Load screen. Logged - I've been submitted. However, the error with sending is 503. 4/30/24 4:50 PM Grinnell College. Logged - I've been submitted. However, the error with sending is 503. 4/30/24 4:53 PM Grinnell College. Load screen. Find Link. Entered. Privacy Policy appears. On console. Logged - I've been submitted. However, the error with sending is 504 about Gateway Timeout. 4/30/24 5:00 PM Investigation will pause tonight for discussion and ramp-up with web server. 4/30/24 8:30 PM Meeting with Liam on witnessing errors on the server side. 4/30/24 9:00 PM We resolved the issues I was seeing due to the unforeseen and last-minute changes from the back end. We discovered this through discussion. We will also work to simplify our fetch calls.
A description of the solution
Ongoing Solution: Change the wait time for fetch calls and remove caching with the web server.
A summary of strategies you used to solve the bug
To come to a solution, I experimented with using the extension on various websites and using log messages. Recording the server errors helped me troubleshoot how to improve the web server connection.
A reflection on what you learned from solving the bug
In development, it's interesting to witness how wait times influence our product. I think it's helpful for me to know as I continue with computing in the future.