Comments (9)
Currently, when the user clicks "Report a problem" we send a "page-problem" telemetry ping. When the user enters details about how the page is broken, we send a "breakage" telemetry ping. So, technically, the display is correct: The user did report "a problem" even though they didn't provide any breakage details.
@ashgrigas - Assuming we still want to allow users to report page problems even if they don't provide any breakage details, should we change copy and/or UX to make this more clear?
from blok.
can we add the word (optional) after the free form text field descriptor text?
from blok.
@ashgrigas yup, that's easy. Do we think that's enough? Or should we put "optional" in the title of the modal to indicate that the entire modal is optional?
from blok.
I would think we would want them to at least choose a radio button at
minimum?
On Wed, Aug 3, 2016 at 12:46 PM, luke crouch [email protected]
wrote:
@ashgrigas https://github.com/ashgrigas yup, that's easy. Do we think
that's enough? Or should we put "optional" in the title of the modal to
indicate that the entire modal is optional?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#71 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AI_-mNb3pS1gDMD5M-aOq8Qlo5FGiVlSks5qcMXWgaJpZM4JYT6F
.
Aislinn Dewey Grigas
User Experience Design Consultant
www.aislinndewey.com
978.930.3729
http://www.linkedin.com/in/aislinn http://www.twitter.com/ashdewey
http://www.facebook.com/ashdewey
from blok.
If they submit breakage details, yes - we require them to at least choose a radio button.
This issue is:
When a user clicks "Report a problem" and then clicks "Cancel" or closes the modal without submitting any details, they still see "You reported a problem on the page" in the notification bar.
It's technically accurate and true - they did indeed report a problem on the page, which we recorded via telemetry. But they didn't give us any details.
So the question is: [how can|should] we change the UI to make it more clear to the user that they did report a problem, even though they didn't give us breakage details.
from blok.
So I guess I don't think it would be clear to users if they clicked the X
or cancel that they actually reported a problem. I think we should change
the recording so it isnt a telemetry record when the X/cancel is clicked -
only if they actually hit submit. The notificaiton bar then would stay in
its original state...
On Wed, Aug 3, 2016 at 2:11 PM, luke crouch [email protected]
wrote:
If they submit breakage details, yes - we require them to at least choose
a radio button.This issue is:
When a user clicks "Report a problem" and then clicks "Cancel" or closes
the modal without submitting any details, they still see "You reported a
problem on the page" in the notification bar.[image: blok-report-cancel]
https://cloud.githubusercontent.com/assets/71928/17376290/9a7e8d52-597a-11e6-8cd9-6a2b934a3894.gifIt's technically accurate and true - they did indeed report a problem on
the page, which we recorded via telemetry. But they didn't give us any
details.So the question is: [how can|should] we change the UI to make it more
clear to the user that they did report a problem, even though they
didn't give us breakage details.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#71 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AI_-mJ0T9R-bNp8fVzj2nJLx4ENAqQiaks5qcNnFgaJpZM4JYT6F
.
Aislinn Dewey Grigas
User Experience Design Consultant
www.aislinndewey.com
978.930.3729
http://www.linkedin.com/in/aislinn http://www.twitter.com/ashdewey
http://www.facebook.com/ashdewey
from blok.
We don't actually send a telemetry ping when the X/cancel are clicked; we do send a telemetry ping as soon as they click the [works|problem] button. We have 3 total separate telemetry pings.
page broken
When the user clicks "Report a problem" we send:
{
originDomain: currentActiveOrigin,
trackerDomains: blockedRequests[currentActiveTabID],
feedback: "page-broken"
}
page works
When the user clicks "This page works well" we send:
{
originDomain: currentActiveOrigin,
trackerDomains: blockedRequests[currentActiveTabID],
feedback: "page-works"
}
breakage
When the user clicks "Submit" in the feedback modal, we send:
{
originDomain: currentActiveOrigin,
trackerDomains: blockedRequests[currentActiveTabID],
breakage: [images|video|layout|buttons|other],
notes: [notes]
}
The page-works
and page-broken
telemetry pings seem valuable even if the user doesn't submit breakage details. I.e. - we can still learn the most-broken sites and the most-breakage-causing trackers. And we can manually check the most-broken sites ourselves to see what's broken.
So, I suggest we keep all 3 of the pings and update the copy to make it clear to the user that they are reporting feedback/data as soon as they click the first buttons, and that the modal is for optional breakage details.
from blok.
@johngruen - what do you think? Should we keep all 3 of these telemetry pings?
from blok.
This became #88 and there's now a PR in for it. #90
from blok.
Related Issues (20)
- The Report a problem input blocks context menu HOT 1
- Indicate the protection is active even on pages where is nothing to block HOT 10
- window is null ext-utils.js:990 HOT 3
- "Report a problem" button not available when Tracking Protection is disabled
- Breakage Analysis: 2016-11-01 HOT 12
- Change copy/text of "notes" field HOT 1
- "You reported a problem with this page" displayed on pages I've never reported
- Blok icon disappears after moving tab to a new window HOT 1
- Block tracking but not advertising HOT 3
- Add a way to review and edit the whitelisted domains. HOT 5
- Change the text next to the toggle switch, to clarify that it only toggles Tracking Protection for the current domain.
- Uh oh. Tracking Protection could not be enabled. Try again later. HOT 5
- Add-on implementation blocks apps.facebook.com differently than native implementation
- Shim requests for utag.js with a no-op utag.view response script HOT 3
- "Share this" buttons do not load Facebook and Twitter HOT 4
- Unable to sign into paypal on ebay checkout HOT 1
- Too many messages in the browser console HOT 3
- Errors in error console HOT 2
- Option to use EFF/Privacy Badger blocklists instead of Disconnect. HOT 1
- CODE_OF_CONDUCT.md file missing
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from blok.