includes/solutions/providers.md - Issue 29369476: Issue 4471 - Added AdRecover to the Acceptable Ads Providers widget

Side by Side Diff

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

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

Side by Side Diff: includes/solutions/providers.md

Issue 29369476: Issue 4471 - Added AdRecover to the Acceptable Ads Providers widget (Closed)

Patch Set: Created Dec. 21, 2016, 5:34 p.m.

Left:
Right:

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

Jump to:

View unified diff | Download patch

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

OLD	NEW
1	1

2 <aside class="card list" markdown="1">	2 <aside class="card list" markdown="1">

3	3

4 ## {{providers-header[Acceptable Ads providers heading] Acceptable Ads Providers }}	4 ## {{providers-header[Acceptable Ads providers heading] Acceptable Ads Providers }}

5	5

6 {{providers-summary[Acceptable Ads providers summary] Interested? These prov iders are already serving Acceptable Ads:}}	6 {{providers-summary[Acceptable Ads providers summary] Interested? These prov iders are already serving Acceptable Ads:}}

7	7

8 - [Criteo](http://www.criteo.com/contact-us/){: target=blank }	8 - [Criteo](http://www.criteo.com/contact-us/){: target=blank }

9 - [Taboola](https://www.taboola.com/contact){: target=blank }	9 - [Taboola](https://www.taboola.com/contact){: target=blank }

10 - [Outbrain](http://www.outbrain.com/contact){: target=blank }	10 - [Outbrain](http://www.outbrain.com/contact){: target=blank }

11 - [RevContent](https://www.revcontent.com/signup){: target=blank }	11 - [RevContent](https://www.revcontent.com/signup){: target=blank }

12 - [Dianomi](http://www.dianomi.com/cms/contact/){: target=blank }	12 - [Dianomi](http://www.dianomi.com/cms/contact/){: target=blank }

13 - [Top Advert](http://www.topadvert.ru/){: target=blank }	13 - [Top Advert](http://www.topadvert.ru/){: target=blank }

14 - [Okoads](https://www.okoclick.fr/contact.html){: target=blank }	14 - [Okoads](https://www.okoclick.fr/contact.html){: target=blank }

15 - [Addoor](http://www.addoor.net/en/contact/){: target=blank }	15 - [Addoor](http://www.addoor.net/en/contact/){: target=blank }

16 - [Halal.ad](http://halal.ad/#contact){: target=blank }	16 - [Halal.ad](http://halal.ad/#contact){: target=blank }

17 - [Carbon](https://carbonads.net/){: target=blank }	17 - [Carbon](https://carbonads.net/){: target=blank }

18 - [Chameleon](http://chameleon.ad/contact-us){: target=blank }	18 - [Chameleon](http://chameleon.ad/contact-us){: target=blank }

	19 - [AdRecover](http://adrecover.com){: target=blank }
	juliandoucette 2017/01/09 18:21:42 NIT: We seem to be using fully resolved URLs above NIT: We seem to be using fully resolved URLs above (EG: http://adrecover.com resolves to https://www.adrecover.com/). I think we should consider dropping "http(s):" because most browsers will automatically detect the correct http/https (favoring https) and this may prevent potential protocol errors (when a third party website expects https but allows http and this results in mixed responses). On one hand, we could change this to a fully resolved URL to be consistent. On the other, it doesn't matter because the URL resolves correctly. As a result, I think we should push this and address the http/https issue separately. juliandoucette 2017/01/09 18:29:47 Created issue: https://issues.adblockplus.org/tick Show quoted text On 2017/01/09 18:21:42, juliandoucette wrote: > NIT: We seem to be using fully resolved URLs above (EG: http://adrecover.com > resolves to https://www.adrecover.com/). I think we should consider dropping > "http(s):" because most browsers will automatically detect the correct > http/https (favoring https) and this may prevent potential protocol errors (when > a third party website expects https but allows http and this results in mixed > responses). > > On one hand, we could change this to a fully resolved URL to be consistent. On > the other, it doesn't matter because the URL resolves correctly. As a result, I > think we should push this and address the http/https issue separately. Created issue: https://issues.adblockplus.org/ticket/4782
19	20

20 </asides>	21 </asides>

OLD	NEW