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

Errors caused by not keeping up with new versions of Chrome? #74

Open
PeterV989 opened this issue Jul 20, 2024 · 0 comments
Open

Errors caused by not keeping up with new versions of Chrome? #74

PeterV989 opened this issue Jul 20, 2024 · 0 comments

Comments

@PeterV989
Copy link

I'm new here so forgive me. This may not be the appropriate place to make these issue observations but I'm hoping to avoid dealing with the gatekeeper volunteer and get right to the people who can address these issues I have persistently seen.

When I try to navigate to the next page in my Daily Reading Plan, the Next button does nothing. I can see that it detects the click on the button but fails to move to the next link. I discovered that if I refresh the page (I used Ctrl+R) it refreshes to the next screen. I did happen to notice a very brief message in the lower corner of my display (above the system tray on my Windows 11 tablet) but it comes and goes so quickly I couldn't read it.

Today I opened the developer tools and found around fifteen console messages. They all seem centered around the CORS headers. Some warnings related to deprecated issues and will become outright errors soon.

My environment is Windows 11 V23H2 OS Build 22631.3880 running Chrome Version 126.0.6478.182 (actually that version is about to be installed once I relaunch Chrome).

Last year I had a bad time with my Daily Reading Plan and I could not move past a blank day (a day of rest or catch-up built into the plan). That was also centered around CORS issues, but I could not get past the volunteer gatekeeper. I worked around it by updating my shortcut to hard-code the day I wanted to read.

This is an issue I would like to tinker with and see if I can figure it out. I'm not sure about the feasibility of my doing that, but I wanted to post this first in case others might have a fast answer to this.

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

No branches or pull requests

1 participant