bugs.html - Issue 5685291679481856: Issue 676 Adapted /bugs page at adblockplus.org to drive users to the forum rather than the issue t…

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
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
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
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
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Unified Diff: bugs.html

Issue 5685291679481856: Issue 676 Adapted /bugs page at adblockplus.org to drive users to the forum rather than the issue t… (Closed)

Patch Set: Seperated sentences for translations. Created June 17, 2014, 3:59 p.m.

Use n/p to move between diff chunks; N/P to move between comments.

Jump to:

View side-by-side diff with in-line comments

Download patch

Index: bugs.html

diff --git a/bugs.html b/bugs.html

index 9b1a5836799b4948561a657368a20f5a3b1003fc..b4bc38a3c8ef105ec1deb637b70f3e83c09bbaf6 100644

--- a/bugs.html

+++ b/bugs.html

@@ -7,11 +7,6 @@

Please consider the following points before filing your bug report.

</p>

-<h2 id="support">Getting support</h2>

-<p>

- If you are not sure, whether you are actually facing a Bug/Defect, first <a href="/forum/index.php">get support in the forum.</a>

-</p>

<h2 id="nonbugs">Some issues aren't Adblock Plus bugs</h2>

<ul>

@@ -38,20 +33,14 @@

</li>

</ul>

-<h2 id="known">Some issues are already known</h2>

+<h2 id="reporting">How to report bugs</h2>

<p>

- Please have a look at the known issues (<a href="en/known-issues"><fix>Firefox</fix></a>,

- <a href="en/known-issues-chrome"><fix>Chrome</fix></a>) before reporting.

- You should also <strong>look through existing bug reports first</strong> in the <a href="/forum/viewforum.php?f=11">bug forum</a> and our <a href="https://issues.adblockplus.org/report/10">issue tracker</a>.

+ You can get support and <a href="/forum/index.php">report your issue in the forum.</a>

</p>

-<h2 id="reporting">How to report bugs</h2>

<p>

- Adblock Plus bugs can be reported <a href="https://issues.adblockplus.org/newticket">in the

- issue tracker</a>.<fix> </fix>Please create a new issue, unless you are <strong>absolutely</strong> sure that you are facing the same

- issue, when commenting on an existing one.<fix> </fix>Your bug report should contain all necessary information to reproduce it:

+ Your bug report should contain all necessary information to reproduce it:

</p>

<ul>

@@ -75,6 +64,5 @@

<p>

You came back and your bug report is no longer there?<fix> </fix>Maybe the moderators

- changed the title to make it more meaningful, look around in the <a href="https://issues.adblockplus.org/report/10">issue tracker</a> and the <a href="/forum/viewforum.php?f=11">bug forum</a>.<fix> </fix>Or it wasn't a

- valid bug report and has been moved to the <a href="/forum/index.php">general discussion forum.</a>

+ changed the title to make it more meaningful. <fix> </fix> Look around <a href="/forum/index.php">in the forum.</a>

</p>

« no previous file with comments | « no previous file | no next file » | no next file with comments »