Skip to content

Conversation

carlosjeurissen
Copy link
Contributor

As discussed in:
#229 (comment)

To align with other extension APIs like scripting.registerContentScripts(), using camelCase when setting iconVariants instead of snake_case would align with existing patterns in webExtension API design.

This PR also adds a note on NotificationOptions.iconVariants as alternative for NotificationOptions.iconUrl.

@carlosjeurissen carlosjeurissen changed the title Correct iconVariants and colorSchemes casing. Add NotificationOptions.iconVariants Correct iconVariants and colorSchemes casing. Add NotificationOptions.iconVariants Oct 9, 2025
@carlosjeurissen carlosjeurissen changed the title Correct iconVariants and colorSchemes casing. Add NotificationOptions.iconVariants Correct iconVariants and colorSchemes casing. Add NotificationOptions.iconVariants Oct 9, 2025
@carlosjeurissen
Copy link
Contributor Author

@solomonkinard @oliverdunk considering the pending Chromium implementation, love to hear your thoughts.

@carlosjeurissen
Copy link
Contributor Author

carlosjeurissen commented Oct 10, 2025

@xeenon after checking your webkit PR on the setIcon null fix (https://github.com/WebKit/WebKit/pull/52135/files), seems you are also handling setIcon({variants: null}), we may want to add this to the proposal as well. (Or introduce a more semantic version, like restoreIcon() or resetIcon() as proposed in #876
@solomonkinard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants