CRIMX

Results 13 issues of CRIMX

这个 bug 不知道怎么才能复现哈哈。刚重启之后使用没问题,但在一段时间后 bug 开始出现,对方撤销信息成功拦截,但没有拦截提醒。

I was trying write something like ```typescript const [callback, flag] = useEventCallback< React.MouseEvent | boolean, boolean >($events => $events.pipe(mapTo(false)), false) callback(true) ``` And there was type error. ``` Argument of...

Currently Subject state$ and input$ are always created. How about checking the `length` of the callback argument and only create the Subjects that are used by the callback. One caveat...

See [NotificationOptions](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/notifications/NotificationOptions).

I'm having trouble making sinon-chrome stubs work with `sinon.match`. I use webpack, karma, mocha and sinon-chai. The spec below may reproduce the error. It looks like sinon-chrome's stub doesn't recognize...

感谢制作这么优秀的应用,请问是否考虑上架 [F-Droid](https://f-droid.org/zh_Hans/)?([提交应用](https://gitlab.com/fdroid/fdroiddata/blob/master/CONTRIBUTING.md))类似[这个](https://f-droid.org/zh_Hans/packages/com.zfdang.touchhelper/)。

enhancement

ESM is for modern usage and should not include babel runtime. The babel regenerator runtime requires `unsafe-eval` CSP which is a safety concern. Removing the babel polyfill can fix this...

Nice work! :tada: While reading the source there is one place I don't quite understand. Why set all the event handlers to noop?

Some of the apis in the schema are partly supported. How about using [browser-compat-data](https://github.com/mdn/browser-compat-data/tree/master/webextensions/api) to make them optional?

enhancement