I'd suggest removing Ci altogether and shipping a shim for the empty root
object (with a deprecation warning) for release only. Thus, developers may be
alarmed without the users noticing at first. Then sometime in the future the
shim can be removed altogether.
___
Am Donnerstag, 13. September 2012 08:28:23 UTC+2 schrieb Jonas Sicking:
> * Some content providers strike deals with hardware manufacturers
>
> which allow devices made by the manufacturer to access content for
>
> free. One way that this is implemented is by looking for tokens in UA
>
> strings
As posted in the other thread, I'd rather setup an updateable list instead of
baking this list right into the release thus being able to react faster on
fixes to existing sites and newly found broken sites. See the IE7/8/9 compat
mode list analogy.
However, your policy can apply to an extra (n
May you point me to the documents describing this solution? I cannot find
anything else than bugs with patches which is quite tedious to dissect …
Thanks.
--fb
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listi
Mac OS X Mavericks has been released with improvements to NC. Safari uses NC to
display Web/PushNotifications and seems to work quite well.
I'd like you to revisit the decision to drop NC in favor of XUL Notifications,
and have a second look at the new API and capabilities. NC support could be
5 matches
Mail list logo
