mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 09:16:03 +03:00
[GH-ISSUE #1465] Response section stays hidden on FireFox #472
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#472
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rschristian on GitHub (Feb 4, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1465
Describe the bug
The entire "Response" section stays hidden right now on Firefox.
Opening up dev tools, it seems to be because the only element within the Response section ('#response') has a "hidden" class. Removing the class displays the Response section once again, though this does involve opening up the dev tools and manually editing the content. Not sure why that class is there to begin with.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I'd expect to see the Response section so I can see what the HTTP method returns
Screenshots



There's three images here. The first is when navigating to the page, the second is opening dev tools and highlighting the "hidden" element that seems to be the issue, the third is upon manually editing the element's class list so that "hidden" is no longer applied.
Desktop (please complete the following information):
Additional context
Opening this up in Chrome on another device works as expected.
@liyasthomas commented on GitHub (Feb 4, 2021):
Noted. I'm inspecting this use case. Thanks for reporting the issue.
Can you reproduce this issue after doing a force refresh?
@rschristian commented on GitHub (Feb 5, 2021):
Yes, I can still reproduce after a force refresh.
Was just able to test standard Firefox on Windows, and that's unaffected. That might narrow it down to the Arch build or the developer edition.
@liyasthomas commented on GitHub (Feb 5, 2021):
Thanks for the detailed information. Hoping to fix this ASAP.
@rschristian commented on GitHub (Feb 5, 2021):
After manually clearing cookies, storage, etc. it seems to have been corrected. Seems resolved, as I can't reproduce.
Edit: Not sure what did it, apologies for not trying that earlier.
@liyasthomas commented on GitHub (Feb 5, 2021):
About 3 weeks ago, we did a overhaul on UI - with more modern components and migrated to TailwindCSS.
I'm guessing - before this update you might've collapsed Response section. And came after UI overhaul. Anyways, feel free to open issue if this happens again.
@rschristian commented on GitHub (Feb 5, 2021):
That sounds likely to have been the issue. Thanks for the quick response! Love the tool.