Closed Bug 1801440 Opened 3 years ago Closed 3 years ago

Online USA Today crossword puzzle doesn't work.

Categories

(Core :: DOM: Core & HTML, defect)

Firefox 107
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: huwashburn, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0

Steps to reproduce:

I log in to https://puzzles.usatoday.com/ to play USA Today crossword puzzle online. I select Start Playing button to open the cross word grid. The crossword grid should appear and you should start typing answers. I have been doing this for months on Firefox.

Actual results:

I log in to https://puzzles.usatoday.com/ to play USA Today crossword puzzle online. I select Start Playing button to open the cross word grid. I get an error message:

"Application error: a client-side exception has occurred (see the browser console for more information)."

Expected results:

I log in to https://puzzles.usatoday.com/ to play USA Today crossword puzzle online. I select Start Playing button to open the cross word grid. The crossword grid appears and then I start typing answers.

This puzzle works fine if I use Microsoft Edge.

The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core

This is working for me in Nightly 109. The crossword is HTML based, so this isn't media related. Reporter, can you try safe mode? Also disabling tracking protection for the site might help.

Component: Audio/Video: Playback → DOM: Core & HTML

I found a fix for this. I could get it to work in the safe mode so I investigated my add ons. It was an ad blocking add on that was causing the problem and I turned it off for that website. Still don't know why it was working for months before it stopped working.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.