Skip to content

Expand on limitations of existing speech recognition events in Alternatives and refactor Timestamps to use Seconds - #205

Open
alan33d wants to merge 2 commits into
mainfrom
alan33d-patch-2
Open

Expand on limitations of existing speech recognition events in Alternatives and refactor Timestamps to use Seconds #205
alan33d wants to merge 2 commits into
mainfrom
alan33d-patch-2

Conversation

@alan33d

@alan33d alan33d commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

Added detailed explanations regarding the limitations of existing API surfaces for tracking latency in speech recognition in the Alternatives Considered section, including issues with speechstart and speechend events and the implications of modifying event.timeStamp.

Added detailed explanations regarding the limitations of existing API surfaces for tracking latency in speech recognition in the Alternatives Considered section, including issues with `speechstart` and `speechend` events and the implications of modifying `event.timeStamp`.
@alan33d
alan33d requested review from evanbliu and reillyeon August 20, 2026 22:41
@alan33d alan33d self-assigned this Aug 20, 2026
Updated the speech recognition result timestamps to use seconds instead of milliseconds, improving consistency with other Web APIs. Added detailed explanations for the choice of time representation, proposed behavior, and security considerations. Based off of comments from #205
@alan33d alan33d changed the title Expand on limitations of existing speech recognition events in Alternatives Expand on limitations of existing speech recognition events in Alternatives and refactor Timestamps to use Seconds Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants