I tend to leave browser tabs open. But if I come back to the steinberg.help page that has been open in a tab for a while, a search for a topic returns errors. The url has a base of www.steinberg.help but I get DNS errors if I try to refresh it. If I try using a new tab everything works fine. Any ideas what’s going on?
What platform and browser are you using? There have been some reports of problems with older Macs running Safari.
2018 Mac Mini, Sonoma, Chrome
Hi @Michael_Miller - welcome to the forum!
How long would you say is “a while”? If it’s more than a few days, then it could be that our documentation hosting platform has rotated their back-end servers recently – which can happen when deploying new code – and the DNS cache in your browser tab is stale.
We will certainly pass this observation onto them and see what they say.
1 Like
Not sure if this is related, but I can report a recent behavior change in Safari (17.6): when I go to my ever-open 5.1 manual tab after “some amount of time” (unhelpful, I realize, [EDIT: but not “more than a few days,” I know] — I’ll start to pay closer attention), it’s blank except for the “loading website” wheel, which never completes. But as soon as I manually reload the page it loads just fine.
ADDENDUM: Also, I’ve noticed just very recently I’ve begun being prompted several times a day to accept Steinberg cookie settings and even got bumped out once and had to log back in. New behaviors to this regular user, for sure. I’m enough of a “world-wide-inter-web” (
) ignoramus not to know if these would be related to some of the other behaviors being reported, but I wanted to err on the side of caution.
Regardless of any problems that may or not be related, I always recommend not using Chrome.
There are other Chromium-based browsers, like Brave, Vivaldi, or MS Edge.
Thanks, but with all due respect, I don’t think that’s a good business strategy:
Browser worldwide marketshare Aug 2024
|Chrome|65.18%|
|Safari|18.55%|
|Edge|5.26%|
|Firefox|2.74%|
|Samsung Internet|2.56%|
|Opera|2.15%|
While I agree, Chrome has it’s issues, mainly making it impossible for web designers to keep up… The symptoms indicate a problem at the server end rather than with the browser. But I’ll give Firefox a try as I’m wary of the others.
Not sure if any of this is relevant. However, everything but the last line of the log was there when I returned to the page after a few hours. Then when I tried to refresh, the message about navigating to the chrome-error appeared.
hth
VM34:7969 2024-09-11T07:28:47.901-05:00 WARNING - net.antidot.fluidtopics.client.application.reader.shared.base.misc.TopicsPositionManager - Trying to restore scroll position, but no restoration point was stored
yQf @ VM34:7969
VM34:7969 2024-09-11T07:28:48.028-05:00 WARNING - net.antidot.fluidtopics.client.application.reader.shared.base.misc.TopicsPositionManager - Trying to restore scroll position, but no restoration point was stored
yQf @ VM34:7969
VM34:7969 2024-09-11T07:28:48.031-05:00 WARNING - net.antidot.fluidtopics.client.application.reader.shared.base.misc.TopicsPositionManager - Trying to restore scroll position, but no restoration point was stored
yQf @ VM34:7969
VM34:7969 2024-09-11T07:29:09.777-05:00 WARNING - net.antidot.fluidtopics.client.application.reader.shared.base.misc.TopicsPositionManager - Trying to restore scroll position, but no restoration point was stored
yQf @ VM34:7969
cJg @ VM34:7483
bJg @ VM34:5835
qJg @ VM34:6953
wJg @ VM34:5082
G6l @ VM36:7855
XCl @ VM36:6851
JCl @ VM36:7395
sDl @ VM36:8008
CBp @ VM34:7981
ABp @ VM34:7981
Yzp @ VM34:7981
iE @ VM34:7966
(anonymous) @ VM34:4321
FI @ VM34:4018
II @ VM34:7365
(anonymous) @ VM34:5702
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Third-party cookie will be blocked in future Chrome versions as part of Privacy Sandbox.
Node cannot be found in the current page.
VM34:7969 2024-09-11T07:31:24.561-05:00 WARNING - net.antidot.fluidtopics.client.application.reader.shared.base.misc.TopicsPositionManager - Trying to restore scroll position, but no restoration point was stored
yQf @ VM34:7969
cJg @ VM34:7483
bJg @ VM34:5835
qJg @ VM34:6953
wJg @ VM34:5082
G6l @ VM36:7855
WCl @ VM36:6866
lAl @ VM36:7467
cAl @ VM36:4260
LBl @ VM36:8008
Gzn @ VM34:7975
$S @ VM34:7775
RS @ VM34:7407
Rwn @ VM34:1799
ovn @ VM34:4054
iAl @ VM36:4964
zAl @ VM36:7938
EAl @ VM36:8008
i0g @ VM34:7971
eCp @ VM34:6694
tCp @ VM34:7981
Qvg @ VM34:6106
fCp @ VM34:7097
kCp @ VM34:7981
WCp @ VM34:7981
BT @ VM34:6080
UT @ VM34:7967
(anonymous) @ VM34:5648
FI @ VM34:4018
II @ VM34:7365
(anonymous) @ VM34:5702
XMLHttpRequest.send
JT @ VM34:7777
OBp @ VM34:7422
VBp @ VM34:7899
hCp @ VM34:7981
Sou @ VM34:6843
sxl @ VM36:7625
hAl @ VM36:7907
aAl @ VM36:7277
qBl @ VM36:8008
Yzp @ VM34:7981
iE @ VM34:7966
(anonymous) @ VM34:4321
FI @ VM34:4018
II @ VM34:7365
(anonymous) @ VM34:5702
setTimeout
mE @ VM34:4013
bE @ VM34:6734
jE @ VM34:7966
Qzp @ VM34:5398
Uzp @ VM34:3912
Yzl @ VM36:5904
kAl @ VM36:5975
M3l @ VM36:7562
tdl @ fluidtopicsclient-65.js:235
Ndl @ fluidtopicsclient-65.js:543
Wzn @ VM36:8008
$S @ VM34:7775
N4l @ VM36:7638
z3l @ VM36:7768
v4l @ VM36:8008
C3l @ VM36:2573
B4l @ VM36:8008
oJ @ VM34:7358
fJ @ VM34:6162
rJ @ VM34:7966
mJ @ VM34:1809
FI @ VM34:4018
II @ VM34:7365
(anonymous) @ VM34:5702
d @ VM34:6305
setTimeout
d @ VM34:6305
setTimeout
d @ VM34:6305
setTimeout
pJ @ VM34:6306
hJ @ VM34:6327
jJ @ VM34:4016
eI @ VM34:7242
jI @ VM34:2325
Lml @ VM34:7974
g9f @ VM34:7970
zlg @ VM34:4534
Glg @ VM34:6917
Tlg @ VM34:6709
qlg @ VM34:1784
slg @ VM34:7970
$S @ VM34:7775
bT @ VM34:6233
bkg @ VM34:7201
dZn @ VM34:7977
gkg @ VM34:7690
rkg @ VM34:7970
FS @ VM34:7967
$S @ VM34:7775
LS @ VM34:6780
lNm @ VM34:1798
xNm @ VM34:7974
GS @ VM34:4533
nNm @ VM34:7880
bPm @ VM34:7571
QOm @ VM34:7974
ETf @ VM34:6258
pVf @ VM34:5900
FI @ VM34:4018
II @ VM34:7365
(anonymous) @ VM34:5702
[Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as ‘passive’ to make the page more responsive. See
[Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as ‘passive’ to make the page more responsive. See
[Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as ‘passive’ to make the page more responsive. See
[Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as ‘passive’ to make the page more responsive. See
[Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as ‘passive’ to make the page more responsive. See
[Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as ‘passive’ to make the page more responsive. See
[Violation] Added non-passive event listener to a scroll-blocking event. Consider marking event handler as ‘passive’ to make the page more responsive. See
www-embed-player.js:1871 [Violation] ‘setTimeout’ handler took 114ms
base.js:1642 [Violation] ‘setTimeout’ handler took 103ms
lgfEe1oiFLs:1 Blocked aria-hidden on a element because the element that just received focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at Accessible Rich Internet Applications (WAI-ARIA) 1.3. <button class="ytp-play-button ytp-button" aria-keyshortcuts="k" data-title-no-tooltip="Pause" aria-label="Pause keyboard shortcut k">…
lgfEe1oiFLs:1 Access to XMLHttpRequest at ‘https://googleads.g.doubleclick.net/pagead/viewthroughconversion/962985656/?backend=innertube&cname=56&cver=20240902&foc_id=IOwP19omIVDSUq2rTGgHKw&label=followon_view&ptype=no_rmkt&random=529072368&cv_attributed=0’ (redirected from ‘https://www.youtube.com/pagead/viewthroughconversion/962985656/?backend=innertube&cname=56&cver=20240902&foc_id=IOwP19omIVDSUq2rTGgHKw&label=followon_view&ptype=no_rmkt&random=529072368’) from origin ‘https://www.youtube.com’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.
base.js:1678
GET https://googleads.g.doubleclick.net/pagead/viewthroughconversion/962985656/?backend=innertube&cname=56&cver=20240902&foc_id=IOwP19omIVDSUq2rTGgHKw&label=followon_view&ptype=no_rmkt&random=529072368&cv_attributed=0 net::ERR_FAILED 302 (Found)
xr @ base.js:1678
g.yr @ base.js:1685
AVa @ base.js:5506
(anonymous) @ base.js:5597
Dr.then @ base.js:8354
dWa @ base.js:5597
eWa @ base.js:5592
gWa @ base.js:5581
uWa @ base.js:5617
wYa @ base.js:5876
uYa @ base.js:5875
(anonymous) @ base.js:5874
(anonymous) @ base.js:1642
setInterval
g.pr @ base.js:1668
vYa @ base.js:5874
g.k.eM @ base.js:11378
(anonymous) @ base.js:1642
bi @ base.js:720
g.k.dispatchEvent @ base.js:7814
g.k.dispatchEvent @ base.js:9250
listener @ base.js:6049
[Violation] ‘setTimeout’ handler took 53ms
en/dorico/topics/setup_mode/setup_mode_percussion_kits_c.html:1 Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Navigated to chrome-error://chromewebdata/
@Michael_Miller,would you please edit that post and at least wrap that lengthy pasted code inside the forum’s hide details feature? (I would think that even better would be to upload it as a zipped text file.) It’s quite the scroll!
1 Like