Covers instances of 'GoogleChrome'

[jonathansampson]

Automated test plan

npm run unittest -- --grep="extensionsUtil bravifyText"

Description

• Submitted a ticket for my issue if one did not already exist.
• Used Github auto-closing keywords in the commit message.
• Added/updated tests for this change (for new code or code which already has tests).
• Ran git rebase -i to squash commits (if needed).

Fixes #8181

Also removes old stub version of bravifyText from js/about/extensions.js.

[bsclifton]

@jonathansampson can you update this (and the original issue) to have testing steps? Thanks 😄

[cezaraugusto]

++

[jonathansampson]

@bsclifton In this particular case, you would need to have an older session-store-1 file that had Pocket's name/description cached. Upon updating Brave, the cached name/description from session-store-1 would be loaded, and the incorrect value would be shown.

I don't think this will be something we need to watch moving forward.

We could, and probably should, write a few unit tests for bravifyText though.

[bsclifton]

@jonathansampson ah ok... unit tests work 😄 Would you be able to make some? (I can help if needed, let me know). Then we can mark this as no QA needed, since it would be covered by automated tests

[jonathansampson]

@bsclifton I still have issues running tests on Windows, but I think Unit Tests will work easier than the Chrome Driver ones. I'll write up a couple tests, and see if they work as expected.