Skip to content

Releases: timing71/chrome

v1.6.4

Choose a tag to compare

@jamesremuscat jamesremuscat released this 14 Apr 09:43
  • Fix a CSS issue preventing the "Launch Timing71" box from being visible on some sites.

v1.6.3

Choose a tag to compare

@jamesremuscat jamesremuscat released this 05 Apr 23:34

Fix a bug with iframe source URL detection.

v1.6.2

Choose a tag to compare

@jamesremuscat jamesremuscat released this 05 Dec 16:27

Remove obsolete workaround for GCLB sticky-session cookie handling.

v1.6.1

Choose a tag to compare

@jamesremuscat jamesremuscat released this 14 Jul 10:27

Fix transferring replay ZIP data from background to host processes.

v1.6.0

Choose a tag to compare

@jamesremuscat jamesremuscat released this 30 Jun 08:58
  • Further fixes to replay generation
  • Add the ability to mark past sessions as "safe from deletion" - such marked sessions will not be deleted automatically

v1.5.0

Choose a tag to compare

@jamesremuscat jamesremuscat released this 01 Jun 11:55
  • Fix a bug with replay generation that would cause skipped frames and inconsistent data.
  • Update to @timing71/common package v0.6.0.

v1.4.0

Choose a tag to compare

@jamesremuscat jamesremuscat released this 13 Jun 15:52
  • Fix bug relating to multi-session support
  • Show all relevant version numbers in menu
  • Update dependencies

v1.3.0

Choose a tag to compare

@jamesremuscat jamesremuscat released this 19 Apr 12:58

Add support for specifying WebSocket subprotocols (necessary to support GraphQL subscriptions).

v1.2.0

Choose a tag to compare

@jamesremuscat jamesremuscat released this 03 Nov 11:40
  • Add support for services using an EventSource (including fiawec.tv)
  • Fixed ability to manually delete services
  • Removed some obsolete defaults.

v1.1.0

Choose a tag to compare

@jamesremuscat jamesremuscat released this 05 Jun 10:46
  • Allow services to store arbitrary transient data.
    • This is intended to allow services to persist certain internal state so that it can be recovered if the service is restarted (e.g. the browser page is refreshed).
  • Support multiple sessions from one service instance.
    • This, combined with the related changes to @timing71/common, allows services to declare session changes, and keep separate sessions' data separate. Take, for example, a service that's running all day; previously you'd have one set of data with each track session that day (practices, qualifying, support races...) and no easy way to separate them out. Now, if services can detect a session change, they can store each session separately.
  • Move IndexedDB access to extension-space code. This resolves an issue where some services would not work without third-party cookies enabled in Chrome.
  • Recent sources list is now stored separately to recent sessions; this preserves the list even when recent sessions are expired.
  • Fixed a bug in file naming if the service name or description contained a slash.
  • Added button linking to the T71 Archive to the browser extension menu.