Chrome extension check view (invalid) Processing Method

I have nothing to worry about recently. I have briefly read the chrome extension development and developed a small translation plug-in (translatebao) as a trainer. The development details are not detailed, if you are new to chrome extension development, you can refer to the source code and welcome to provide valuable comments and make progress together.

Nothing to mention. After a demo version is developed, it will be loaded into chrome for experience, and everything will feel good ...(-. -), But if you encounter something that is uncomfortable, see:

 

Yes, the problem is that there is an "invalid" behind "Check view: background.html". Although no specific impact is found, such a negative word seems a bit uncomfortable here, so we started searching.

 

Finally, I learned about the problem:

In fact, here (invalid) prompts are ambiguous. "invalid" gives people the first impression of being "invalid", but in the English version, the prompt here is (inactive ), it should be clear that "invalid" here is actually "inactive.

In the background in manifest. JSON, there is a property called persistent, which describes an attribute that extends the persistent state. When this attribute is false, chrome will disable the application when it detects that the application is not active.

Solution: Change the persistent attribute under the background in manifest. JSON to true, which is not displayed (invalid.

Chrome extension check view (invalid) Processing Method