chrome/common/extensions/docs/templates/intros/feedbackPrivate.html - Issue 17111003: Implement the feedbackPrivate API.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: chrome/common/extensions/docs/templates/intros/feedbackPrivate.html

Issue 17111003: Implement the feedbackPrivate API. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Created 7 years, 6 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

« no previous file with comments | « chrome/common/extensions/api/feedback_private.idl ('k') | chrome/common/extensions/docs/templates/public/extensions/feedbackPrivate.html » ('j') | chrome/renderer/extensions/feedback_private_custom_bindings.cc » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
(Empty)
	1 <p id="classSummary">

	2 Use the <code>chrome.feedbackPrivate</code> module to

	3 provide Chrome [OS] feedback to the Google Feedback

	4 servers.

	5 </p>

	6

	7 <h2 id="code">Implemention of the Chrome [OS] Feedback UI</h2>

	8

	9 <p>

	10 The Chrome [OS] Feedback UI is invoked when the user clicks

	11 the Report an Issue button in the wrench->tools menu (wrench

	12 menu if on Chrome OS). This triggers the onFeedbackRequested event

	13 with a feedbackInfo object with the URL of the current page

	14 (determined by the active tab) and if available, the email of the

	15 logged in user filled in. On Chrome OS, the system information field

	16 in the feedbackInfo object may also contain relevent data <i>(for

	17 example, as of now it is populated with a TIMESTAMP key containing

	18 the timestamp of when the user invoked feedback</i>).

	19 </p>

	20

	21 <p>

	22 The UI first takes a screenshot, then displays itself. It uses the

	23 provided API's to get system information and provides the user with

	24 fields to fill out feedback.

	25 </p>

	26

	27 <p>

	28 Once the user is done, the UI uses the sendFeedback API to send the

	29 feedback to the feedback servers.

	30 </p>

	31

	32 <p>

	33 The sendFeedback API gathers the feedback data and starts a post to

	34 the feedback servers. If the post is successful, a 'success' status

	35 is returned to the Feedback UI, otherwise a 'delayed' status is

	36 returned and Chrome continues to try to send the feedback every 4 hours

	37 for up to a day.

	38 </p>

	39

	40

	41 <p class="note">

	42 <b>Note:</b>

	43 The feedbackPrivate API can also be used by whitelisted apps to provide

	44 a custom feedback UI and send Chrome Feedback. The productId field in

	45 the feedbackInfo structure can be given to override the product ID to

	46 be sent with the feedback report. This will allow the app to send

	47 feedback to it's own feedback bucket instead of the default Chrome [OS]

	48 one.

	49 </p>

OLD	NEW