web control fixed
you need to hit f12 (you will see elements page on right )
then as you would like to refresh page but right click the refresh icon and empty cache and hard reload option
sorted
chrome issue with the reloading page bug fix
Moderators: Site Moderators, FAHC Science Team
-
Frogging101
- Posts: 85
- Joined: Wed Mar 25, 2020 2:39 am
- Location: Canada
Re: chrome issue with the reloading page bug fix
If this does help, I think the same effect can be achieved by pressing Ctrl + F5
Re: chrome issue with the reloading page bug fix
it wont i tested the ctrl f5 does not work for me
Re: chrome issue with the reloading page bug fix
I'm being plagued with this problem and the F12, etc fix works for me.
However, do we know what triggers this behaviour?
It happens when I leave my laptop and Windows' power saving features kicked in. So I disabled these but the problem persists. Is there anything else I need to disable to stop it recurring?
However, do we know what triggers this behaviour?
It happens when I leave my laptop and Windows' power saving features kicked in. So I disabled these but the problem persists. Is there anything else I need to disable to stop it recurring?
-
GeekFantasy
- Posts: 7
- Joined: Tue Apr 07, 2020 2:56 pm
- Hardware configuration: EVGA Nvidia GeForce RTX 2060 Super
Intel Core i7 4790K @ 4.0GHz
Re: chrome issue with the reloading page bug fix
I can confirm that hitting Ctrl + F5 in Chrome on Windows 10 indeed did NOT fix the issue of the Web Control reload loop. However, strangely, the alternative method of opening the Dev Tools and using the "Empty Cache and Hard Reload" option DID fix the problem. I just upgraded my FaH client version on my machine which I believe is what broke my Web Control. Hopefully it stays fixed. We shall see.
Thanks for the tip! @regchan
Thanks for the tip! @regchan
Folding for free as MarkUnboxed since December 2016.
Re: chrome issue with the reloading page bug fix
its a bug in chrome itself as far as i can narrow it down
its trying to reload iframe that linked to
http://127.0.0.1:7396/
i would try running local and see
i cant see any issue as im looking at the f12 info screen and doing the reloading empty cache and reload option
its trying to reload iframe that linked to
http://127.0.0.1:7396/
i would try running local and see
i cant see any issue as im looking at the f12 info screen and doing the reloading empty cache and reload option
Re: chrome issue with the reloading page bug fix
http://127.0.0.1:7396/
loading up locally instead of using the client.folding@home.org page seems to be the site loadding the iframe several times
the Iframe on the site seems to be a bug in the site code
in body
iframe id frame
seems to be the wtx-context some random numbers could be causing this but it gets filled in but i just refreshed and that part of codes not there
just html class no-js
this code works
<html class="no-js">
<!--<![endif]--><head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Folding@home Web Control</title>
<meta name="description" content="">
<meta name="viewport" content="width=device-width">
<link rel="stylesheet" href="css/normalize.css">
<link rel="stylesheet" type="text/css" href="https://fonts.googleapis.com/css?family=Oswald:700,400">
<link rel="stylesheet" href="https://code.jquery.com/ui/1.10.3/theme ... ery-ui.css">
<link rel="stylesheet" href="css/main.css">
</head>
<body style="">
this bit of code is buggy
<html class="no-js" wtx-content ="some numbers and letters">
<!--<![endif]--><head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Folding@home Web Control</title>
<meta name="description" content="">
<meta name="viewport" content="width=device-width">
<link rel="stylesheet" href="css/normalize.css">
<link rel="stylesheet" type="text/css" href="https://fonts.googleapis.com/css?family=Oswald:700,400">
<link rel="stylesheet" href="https://code.jquery.com/ui/1.10.3/theme ... ery-ui.css">
<link rel="stylesheet" href="css/main.css">
</head>
<body style="">
<div id="cp" class="panel corner-all">
loading up locally instead of using the client.folding@home.org page seems to be the site loadding the iframe several times
the Iframe on the site seems to be a bug in the site code
in body
iframe id frame
seems to be the wtx-context some random numbers could be causing this but it gets filled in but i just refreshed and that part of codes not there
just html class no-js
this code works
<html class="no-js">
<!--<![endif]--><head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Folding@home Web Control</title>
<meta name="description" content="">
<meta name="viewport" content="width=device-width">
<link rel="stylesheet" href="css/normalize.css">
<link rel="stylesheet" type="text/css" href="https://fonts.googleapis.com/css?family=Oswald:700,400">
<link rel="stylesheet" href="https://code.jquery.com/ui/1.10.3/theme ... ery-ui.css">
<link rel="stylesheet" href="css/main.css">
</head>
<body style="">
this bit of code is buggy
<html class="no-js" wtx-content ="some numbers and letters">
<!--<![endif]--><head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Folding@home Web Control</title>
<meta name="description" content="">
<meta name="viewport" content="width=device-width">
<link rel="stylesheet" href="css/normalize.css">
<link rel="stylesheet" type="text/css" href="https://fonts.googleapis.com/css?family=Oswald:700,400">
<link rel="stylesheet" href="https://code.jquery.com/ui/1.10.3/theme ... ery-ui.css">
<link rel="stylesheet" href="css/main.css">
</head>
<body style="">
<div id="cp" class="panel corner-all">
Re: chrome issue with the reloading page bug fix
Ok I'll play "spot the difference".
All I can see is the wtx-content attribute on the root element, is that right? I don't seem to have that, but then again it currently works for me. /shrug
All I can see is the wtx-content attribute on the root element, is that right? I don't seem to have that, but then again it currently works for me. /shrug
CPU: Ryzen 9 3900X (1x21 CPUs) ~ GPU: nVidia GeForce GTX 1660 Super (Asus)