-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Browser action docs use incorrect property name in sample manifest #871
Conversation
Hello! This is an automated review by our custom reviewbot. It updates automatically when code or GitHub comments in this pull request are created or updated. Requested changesIf there are any common problems with the content files you created or modified, they will be listed here.
|
✔️ Deploy Preview for developer-chrome-com ready! 🔨 Explore the source changes: 456c27f 🔍 Inspect the deploy log: https://app.netlify.com/sites/developer-chrome-com/deploys/60c29df436fe0b000805df40 😎 Browse the preview: https://deploy-preview-871--developer-chrome-com.netlify.app |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change LGTM.
Commit message says
...
This PR also contains a minor clarification on page action.
But I don't see the change for page action?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
slgtm.
Also note: typo in the commit title ("Browser ation" -> "Browser action")
Words are hard. Thanks, @rdcronin. |
The first code sample in the browser action API docs indicates that the manifest key for a browser action is "action". This PR fixes that reference to say "browser_action".
This PR also contains a minor clarification on page action.