feat(panel): Add the "Report a broken page" view #2164
Conversation
|
Screenshots for reference: 
|
src/background/broken-page-report.js
Outdated
| 'support_ticket[subject]', | ||
| `[GBE] Broken page report: ${msg.url}`, | ||
| ); | ||
| formData.append('support_ticket[message]', msg.description); |
There was a problem hiding this comment.
We should pass the product version via the form. Until it is supported by the website lets add it to the message.
Lets consider if we want to add also:
- list of detected activities (no urls)
- extension settings
- block list version (checksums)
There was a problem hiding this comment.
I had to miss it, I'll add the extension version via the subject. It might be easier to spot or filter out.
The message body has a limit of 5k characters. We can shorten it to 4k for a space of 1k for additional metadata. We can add a list of tracker IDs (from stats), extension settings are important from the privacy section only. The block list might be tricky as it requires all checksums of all lists, but I will try to generate them.
| } | ||
| }); | ||
|
|
||
| sendResponse(); |
There was a problem hiding this comment.
should we add some error handling so in case of a problem we let people know they can report the problem via the website?
There was a problem hiding this comment.
Good point. That's technically easy, I will add a message after error handling, like "Error... However, you can always report the broken page via our [website form]"
smalluban
force-pushed
the
feat-report-broken-page
branch
from
6df993b to
5daf8e8
Compare
The PR adds the CTA for paused domains, which opens the "Report a broken page" in the panel.
activeTabpermission does not trigger a browser popup when the extension is updated. However, we can also try out the optional permission if it is better.mac,win,ios,ipados,linux, etc... and version only as a separate field (currently we havewindows_10and other as os name)WARNING: the PR logic is finished and it's connected to the real end-point. Please use
npm start -- --stagingwhen testing to avoid spaming the support channel.