[Webkit-unassigned] [Bug 88950] [Blackberry] add a new Api named setAllowNotification
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Jun 13 08:12:39 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=88950
--- Comment #8 from Chris.Guan <chris.guan at torchmobile.com.cn> 2012-06-13 08:12:38 PST ---
(In reply to comment #6)
> (From update of attachment 147257 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=147257&action=review
>
> > Source/WebKit/blackberry/Api/WebPage.cpp:6349
> > + static_cast<NotificationPresenterImpl*>(NotificationPresenterImpl::instance())->onPermission(domain.utf8(), allow);
>
> Since this is a singleton, is it a problem that a new page will "inherit" this?
I am thinking refactor our notification implementation.
>
> > Source/WebKit/blackberry/Api/WebPage.h:269
> > + void setAllowNotification(const WebString& domain, bool allow);
>
> Would it make sense for the whole method to be wrapped in #if ENABLE(NOTIFICATIONS) ?
Both are okay to me, I was searching other ports, I remember that I kept the same with it, Mac or QT probably(not sure) :)
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list