search

jonathanwalkerscripts / OppChasers

A repository for the QA Specialized Course team, the Opp Chasers.
3 stars 1 forks source link

Showcase Bug #1 (Craigslist upper limit search bar error)😢 #148

Open therealjustinmiller79 opened 3 years ago

therealjustinmiller79 commented 3 years ago

Environment

Device: HP ProBook 440 G7 Version: 10.0.19042 Build 19402 Browser: Google Chrome Version 88.0.4324.192 (Official Build) (64-bit) User type: User

Description

Attempting a search on my local 'Craigslist' site (https://mendocino.craigslist.org/) using a large amount of characters results in an inability to use the right click function and makes the website unresponsive.

Expected behavior

It is expected that if an upper limit exists that could modify the functionality of the website or user experience it should be amended or posted.

Actual Behavior

Errors result when the upper-limit is exceeded. There is no post or limit set leaving the user unable to navigate effectively.

Steps to Reproduce Issue

  1. Navigate to https://mendocino.craigslist.org/
  2. Right click in search bar and select Bug Magnet >Text size> With spaces >64k
  3. No search result is displayed; right click on search bar again and the page 'freezes' not allowing the user to access any links or further content.
  4. After roughly 15 seconds a message is displayed saying that "This page isn't responding", giving the user 2 options; to Exit Page or Wait.
  5. Clicking the Wait button produces a cycle repeating step 4. Clicking the Exit Page button takes the user to a page saying that "This page is having a problem".

Screenshots

1. Example of the right click drop-down menu.

image

2. Example of displayed message in step 4.

image

3. Example of displayed message in step 5.

image

4. Video showing inability to access content or links.

https://user-images.githubusercontent.com/79952938/119934037-05b9c080-bf3a-11eb-868c-c78af4170bb7.mp4

brianifoster commented 3 years ago

This is an interesting bug. On the 2nd step, should I press Return? I'm assuming I do, and so I did, but I didn't get your result.

Here's a screen recording of what I got:

https://user-images.githubusercontent.com/32716832/120410278-86e0d100-c307-11eb-80a3-5d7839c02259.mov

brianifoster commented 3 years ago

my screen didn't freeze like yours did, but that doesn't mean don't use the bug. it just means that my results were a little different than yours. if you can reproduce that bug over and over, then i say, use it