Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cm/safari audio hack #440

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

cm/safari audio hack #440

wants to merge 3 commits into from

Conversation

CharlieMcVicker
Copy link
Collaborator

  • better indicate unsupported vs denied/unrequested media recorder status
  • add extra logging to media recorder hook
  • fix/hack: allow audio to playback on ios safari

Get around iOS safari never triggering the "oncanplaythrough" event, which our audio player waits for before showing the play button.

Copy link

netlify bot commented Dec 6, 2024

Deploy Preview for dailp ready!

Name Link
🔨 Latest commit e13977f
🔍 Latest deploy log https://app.netlify.com/sites/dailp/deploys/67532c61edeb30000823b99f
😎 Deploy Preview https://deploy-preview-440--dailp.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@GracefulLemming GracefulLemming left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left two comments, neither of them are blockers here but both are probably worth a short conversation.

website/src/components/audio-player.tsx Show resolved Hide resolved
Comment on lines +11 to +12
// TODO: is there a place to store this instead of doing this check everytime?
// happens at this level because vite will run this server-side and crash sometimes
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My first thoughts are to do this through React state. I figure you considered that already though. Is there anything worse about using state than running this every time?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll look for a way to see if we are on the server-side, and short-circuit if we are? I wonder if that would let us make it a constant.

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.

2 participants