Site compatibility reporter not working
Categories
(Web Compatibility :: Tooling & Investigations, defect)
Tracking
(Not tracked)
People
(Reporter: k.akshat, Unassigned)
Details
Attachments
(2 files)
Screenshot_2020-11-14 502 Bad Gateway.png
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:84.0) Gecko/20100101 Firefox/84.0
Steps to reproduce:
I am trying to use the inbuilt "Report a Website Compatibility report", but it is not working. It seems like the reporter is itself broken and does not work at all.
Actual results:
Just try to click on the bulb sign and it throws an error in a new tab.
Expected results:
It should have opened the website reporter and let the bug reporting go ahead.
|
||
Comment 1•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
|
||
Comment 2•5 years ago
|
||
It's working fine at the moment. Are you still seeing the issue?
(In reply to Francesco Lodolo [:flod] from comment #2)
It's working fine at the moment. Are you still seeing the issue?
Yes, I do.
If you want I can share the screenshot of the error. I already did.
Yes it is having the same error and on every single page, does not matter on which webpage I am on, is shows the same error.
|
|
||
Updated•5 years ago
|
|
|
||
Comment 4•5 years ago
|
||
Can you copy and paste the URL that results from clicking the menu?
https://webcompat.com/issues/new
If you mean when I click on the website reporter, and the url it generates in a new tab. There here it is.
Firefox Version is:
Firefox Nightly Version Version 84.0a1 (2020-11-14) (64-bit)
|
||
Comment 8•5 years ago
|
||
What is the website you were trying to report?
And does it break on all sites?
Yes it breaks on all the websites, even on google.com
|
|
||
Comment 10•5 years ago
|
||
So it's probably something related to your environment. This is working for me.
Nightly 84.0a1 (2020-11-15) (64-bit)
macOS 11.0.1 (20B29)
Could you try with restarting with Add-ons Disabled. Just for testing.
or start a new profile.
- Go to about:profiles
- Create a New Profile: call it deleteme
- Go to mozilla.com
- Click on the button "Report Site Issue" (lightbulb button in the °°° menu in the URL bar)
Expected:
A new window open with url being prefilled
Actual:
?
|
|
||
Comment 12•5 years ago
|
||
Ah! I have been able to reproduce, but I had to try 3 times
It could look like a race issue where sometimes the URL is not sent to the webpage.
|
Reporter | |
Comment 13•5 years ago
|
||
Yeah there is some issue on the back end, I am not quite into web-dev but it feels like the server is not responding back.
|
|
||
Comment 14•5 years ago
|
||
Maybe related to this other issue I filed this morning Bug 1677415
The behavior is very similar.
|
|
||
Comment 15•5 years ago
|
||
The backend is in our control :) So we can try to diagnose it if it's the backend.
|
|
||
Comment 16•5 years ago
|
||
Though the issue I have is slightly different than yours, you get a nginx error, if I understood. I get the webcompat.com site but the form not filed.
|
|
Reporter | |
Comment 17•5 years ago
|
||
Yeah there are a bit different bugs.
|
||
Comment 18•5 years ago
|
||
If there is a 502, that's absolutely not the fault of the reporter addon. That's either the backend actually being down, or the request ends up somewhere where it doesn't belong.
k.akshat, do you see the same error when just manually browse to https://webcompat.com/issues/new ? If so, please open the Network monitor, reload the error page, and click on the little gear-icon in the network panels' upper-right corner and hit "Save All As HAR", and please attach the resulting file. That will help us double-checking that your request ends up at the right server, and that things like the Host header is set correctly etc. :)
I'll say some words about the "URL not prefilled" thing over in bug 1677415, but that's a completely different issue.
|
|
Reporter | |
Comment 20•5 years ago
|
||
And yes it does not work even if I manually put the url in browser.
|
|
||
Comment 21•5 years ago
|
||
Hah, that was helpful!
I know this sounds weird, please clear your cookies for webcompat.com - it should be working after that. Let me know if it works (or if it doesn't).
|
|
Reporter | |
Comment 22•5 years ago
|
||
OMG! yes it is working now. Can you please tell what was going wrong and how clearing the cookies helped?
|
|
||
Comment 23•5 years ago
|
||
Your session cookie was larger than we expected. I don't quite know why, but I filed an issue to investigate in our backend repository, see https://github.com/webcompat/webcompat.com/issues/3508.
I'll close this report in favor of the linked GitHub issue. Thank you so much for your help! :)
|
|
Reporter | |
Comment 24•5 years ago
|
||
Thank you so much for your help. I am glad I could contribute in any way to Mozilla. I will look it up and see if it happens again and follow the github issue you have sent.
Description
•