Yellow Lithium - New Tab pages

[Eddy DosSantos]

Hi Team!

We have two extensions that were both rejected for the same reason: Yellow Lithium. The stated reason was that their "primary purpose is to install or launch another app, theme, webpage, or extension."

However, this is not the case. The sole purpose of these extensions is to modify the New Tab page, and they do only that. Each extension uses its own dedicated domain for its New Tab page. These domains are an integral part of the extensions, were built specifically for them, and serve no other purpose.

Has there been any change to the architectural requirements for New Tab pages?

Many Thanks--

									Eddy DosSantos  Network Quality Manager M +972-58-5091911  www.perion.com
Perion Network Ltd. (NASDAQ: PERI)
This message may contain confidential and privileged information. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. Suppose the reader of this message is not the intended recipient. In that case, you are on notice that any use, copy, disclosure, or distribution of this message is strictly prohibited. If you have received this message in error, please notify the sender by replying via email or telephone and delete or destroy any copy of this message. Please note that the sender of this message and their employer collect and process the personal data contained in this message and any of its correspondences as outlined in the applicable privacy policy available on its website.

[Oliver Dunk]

Hi Eddy,

Could you please share the impacted extension IDs?

Thanks,

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Eddy DosSantos]

Hi Oliver, 

Hope all is good with you! 

Here are the extensions IDs:

• acjjhchnekkooeidcjnjpciangnmokgp
• oooanbnlekicbabkbepehpeoindndegn

Many Thanks--

[Oliver Dunk]

Hi Eddy,

Taking a look at the first extension, it appears to immediately close the new tab when opened and open an external URL instead.

I don't think this is something allowed under our API use policy:

Extensions must use existing Chrome APIs for their designated use case.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Eddy DosSantos]

Thank you Oliver! That was indeed the issue. We fixed it, and it has now been approved.

Best--