Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

Pomodoro Clock Example Project #1057

Closed
gunderodd opened this issue Mar 8, 2020 · 3 comments
Closed

Pomodoro Clock Example Project #1057

gunderodd opened this issue Mar 8, 2020 · 3 comments

Comments

@gunderodd
Copy link

gunderodd commented Mar 8, 2020

Issue Description

The example for the Pomodoro Clock project does not make an audible beep when I use Chrome, and fails either 1 or 2 tests (Tests 1 and/or 2 of the #Audio section) in Chrome. I can hear the beep and the tests pass on Edge and Firefox.

Browser Information

  • Browser Name, Version: Chrome 80 (But not on Edge or Firefox)
  • Operating System: Windows 10
  • Mobile, Desktop, or Tablet: Desktop (Though I replicated the problem on Chrome on my Android device)

Your Code / Link to Your Pen

The Pomodoro Example project from FCC

https://codepen.io/freeCodeCamp/full/XpKrrW

@parkers116
Copy link

I have the same issue. But I think it is not the bug of this project.
This issue cause due to the upgraded security of Chrome 80.
All HTTP request in audio tag would be automatically converted to HTTPS
If the server of request URL doesn't have HTTPS, it cannot reach.

@gunderodd
Copy link
Author

gunderodd commented Mar 14, 2020

@parkers116 that is very interesting. I don't know much about it, myself, so I did some research, and found this:

Chrome 80 also sees some changes in the way that the browser handles HTTPS requests. The problem is many pages using HTTPS still load some of the content they contain using insecure HTTP. This is called mixed content and it’s a particular problem for images, audio, and video, Google has said. It’s all very well loading a page securely, but if it loads an insecure image that compromises your browser, you may as well not have bothered with HTTPS at all.

The company moved towards blocking all mixed content by default in Chrome 79, but it’s doing it in stages. In Chrome 80, mixed audio and video resources will be upgraded automatically to HTTPS. If they can’t load using that protocol, the browser will block them. Mixed images will still load, but they will prompt a “Not Secure” icon in the omnibox (that’s the address bar, to you and me).

@moT01
Copy link
Member

moT01 commented Sep 18, 2020

For more visibility, please open issues on the main repo for these. Thanks and happy coding 🎉

@moT01 moT01 closed this as completed Sep 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants