0.8.0

Soft checking for missing APIs

Unfortunately in the Chromium sources there is currently one API method with wrong version metadata (runtime.onConnectNative). Chromex used to throw when you used an API method which is missing in your particular Chrome version. Instead we log an error message and continue running by skipping the call. This allows for more soft approach and does not break chromex-sample.

API update

Regenerated APIs to match Chromium @ 9812e7c8aa38.

Notable commits:

a8d68a1 lib: by default, don't throw on missing-api, log error instead

All new changes: v0.7.3...v0.8.0

0.7.3

API update

Regenerated APIs to match Chromium @ bc0e704fa984.

Notable commits:

NONE

All new changes: v0.7.2...v0.7.3

0.7.2

API update

Regenerated APIs to match Chromium @ 6ec8f2bbb140.

Notable commits:

NONE

All new changes: v0.7.1...v0.7.2

0.7.1

Using promise-chan for callbacks in wrappers

WARNING: this is potentially a breaking change!

I realized there were two more places where promise-chan semantics is more appropriate. Please refer to v0.6.0 release notes for detailed explanation.

Reverting to the old behaviour

If you need to revert to old behaviour. Please look at notable commits. You can configure chromex to use your custom implementations of :chrome-storage-area-callback-channel-factory and :chrome-content-setting-callback-channel-factory. By swapping them for old implementation you can easily get back the old behaviour.

API update

Regenerated APIs to match Chromium @ bcc56e24c4d0.

Notable commits:

da056b5 return promise-chan from default-chrome-content-setting-callback-channel-factory
e87f709 return promise-chan from default-chrome-storage-area-callback-channel-factory

All new changes: v0.7.0...v0.7.1

0.7.0

Moved protocols [potentially breaking change]

Ian S Kerins added contentSettings.ContentSetting wrapper via PR #16. Thanks for the contribution!

I decided to move protocols under separate namespaces. Please see issue #17 for details.

API Update

Regenerated APIs to match Chromium @ b793b53fd9cd.

Notable commits:

d3235ca Add a wrapper for contentSettings.ContentSetting by @isker
60e34a8 move defprotocols under separate namespaces, issue #17

All new changes: v0.6.5...v0.7.0

0.6.5

API update

Regenerated APIs to match Chromium @ d3a040e.

Notable commits:

NONE

All new changes: v0.6.4...v0.6.5

0.6.4

API update

Regenerated APIs to match Chromium @ fb4d3d0.

Notable commits:

NONE

All new changes: v0.6.3...v0.6.4

0.6.3

API update

Regenerated APIs to match Chromium @ c23d1b7.

Notable commits:

NONE

All new changes: v0.6.2...v0.6.3

0.6.2

API update

Regenerated APIs to match Chromium @ 4437633.

Notable commits:

NONE

All new changes: v0.6.1...v0.6.2

0.6.1

API update

Regenerated APIs to match Chromium @ f58e6f9.

Notable commits:

NONE

All new changes: v0.6.0...v0.6.1