[Webkit-unassigned] [Bug 254884] setAppBadge() with no or '0' as argument should show badge

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Apr 4 18:02:10 PDT 2023


https://bugs.webkit.org/show_bug.cgi?id=254884

Brady Eidson <beidson at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |beidson at apple.com

--- Comment #4 from Brady Eidson <beidson at apple.com> ---
(In reply to ik from comment #3)
> 
> - Calling setAppBadge() (the value "flag") should display a badge without a
> number. WebKit incorrectly removes the badge.

WebKit actually doesn't (see below)

> I do agree that iOS not supporting "flag" badges presents a problem here,
> but I'm not sure that removing the badge is the right solution?

I agree that `setAppBadge()` - An attempt to set the badge to flag - should not remove the badge. That's a bug.

> Maybe showing '1' is more appropriate?

I don't think "1" meaning two very distinct things is a great situation to be in.

> I'd rather have WebKit handle this because the alternative is that websites
> need to call setAppBadge() or setAppBadge(1) depending on browser detection
> (which is undesirable).

I don't think that websites that want to set `flag` would be happy with `1` instead.
It seems like maybe you would be, but are you saying it's the right thing to have the platform enforce that for all websites?

I don't think that's obviously right.

That said, WebKit actually isn't the business of doing anything here. WebKit communicates all of the information properly through its delegates and the embedding app makes the call of what to do.

There's *definitely* a bug in Apple's iOS 16.4 release in that attempts to set `flag` instead clear the count. And an Apple component should be updated to fix that.

We'll import into Radar to get the ball rolling there.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230405/ebecd207/attachment.htm>


More information about the webkit-unassigned mailing list