Skip to main content
Super User

Return to Answer

Commonmark migration
Source Link
Community Bot
Community Bot
  • 1

Also got this problem, and so did a bit of digging.

According to this answer from a Chrome Dev, there is nothing you can do about it. They say:

This is related to a new feature that aims to prevent third party software from injecting into Chrome's processes and interfering with its code.

 

To keep things simple we warn about all injected software, without making value judgments.

Thankfully, they also say:

Note that soon we will actually start blocking software from injecting, at which point this warning will cease to show.

So I guess all that can be done is wait from them to move from warning to blocking. The answer was posted in July 2018, so I imagine soon could be anywhere from the next 2 months to next year.

Also got this problem, and so did a bit of digging.

According to this answer from a Chrome Dev, there is nothing you can do about it. They say:

This is related to a new feature that aims to prevent third party software from injecting into Chrome's processes and interfering with its code.

 

To keep things simple we warn about all injected software, without making value judgments.

Thankfully, they also say:

Note that soon we will actually start blocking software from injecting, at which point this warning will cease to show.

So I guess all that can be done is wait from them to move from warning to blocking. The answer was posted in July 2018, so I imagine soon could be anywhere from the next 2 months to next year.

Also got this problem, and so did a bit of digging.

According to this answer from a Chrome Dev, there is nothing you can do about it. They say:

This is related to a new feature that aims to prevent third party software from injecting into Chrome's processes and interfering with its code.

To keep things simple we warn about all injected software, without making value judgments.

Thankfully, they also say:

Note that soon we will actually start blocking software from injecting, at which point this warning will cease to show.

So I guess all that can be done is wait from them to move from warning to blocking. The answer was posted in July 2018, so I imagine soon could be anywhere from the next 2 months to next year.

Source Link
CalvT
CalvT
  • 781
  • 4
  • 9
  • 28

Also got this problem, and so did a bit of digging.

According to this answer from a Chrome Dev, there is nothing you can do about it. They say:

This is related to a new feature that aims to prevent third party software from injecting into Chrome's processes and interfering with its code.

To keep things simple we warn about all injected software, without making value judgments.

Thankfully, they also say:

Note that soon we will actually start blocking software from injecting, at which point this warning will cease to show.

So I guess all that can be done is wait from them to move from warning to blocking. The answer was posted in July 2018, so I imagine soon could be anywhere from the next 2 months to next year.