TT Start Countdown Timer: Press for Beeps - not working

[simidau]

I'm assuming it's related to a browser update, but I can no longer click on the Press For Beeps button to make it go fullscreen and produce the beeps. Happened about 3 weeks ago.

[esitarski]

What hardware, OS and browser are you using? I tried it with Chrome and Firefox on Linux and Windows and it works fine. Can you be more specific about "can no longer click on the Press for Beeps button"? Is the button not shown, or you can't click on it, or you click on it and it doesn't work?

…

On Mon, Mar 27, 2023 at 1:01 AM simidau ***@***.***> wrote: I'm assuming it's related to a browser update, but I can no longer click on the Press For Beeps button to make it go fullscreen and produce the beeps. Happened about 3 weeks ago. — Reply to this email directly, view it on GitHub <#109>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABGXKON3NUJNUYEJ4APMRLW6ENJRANCNFSM6AAAAAAWIVOMPY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Edward Sitarski

[simidau]

Windows 10, tried with Chrome and Edge. I can see the button but it doesn't respond to clicks. Interestingly it worked again when I tried yesterday at our event, but I tried it a number of times prior to the event and no dice. Crossmgr is the latest version, I tried it prior to the event with 3.1.14 (approx version number) and then updated to 3.1.17 and got the same result. Then it worked at the event.

[stuartlynne]

I was just trying to get the countdown page to work and am seeing (as in not seeing) the same thing. Chrome and Edge on Windows 11, Chrome and Firefox on Linux. Chrome on Windows 10.

Screen shot from Firefox. Identical to

This is the start list.

The event results page does work:

[stuartlynne]

Here is the countdown table exposed in Chrome developer tools,

[esitarski]

I changed the page so that "Press for Beeps" gets its callback in the html, not in onload. This works more reliably if you press it as soon as the page loads as onload can get busy synchronizing the browser's clock. Available in latest release. The problem was that the button callback was set in onload, which also does a bunch of other processing like setting the clock synchronization. If you press the button quickly after the page loads, it doesn't work because onload hasn't set the callback yet. If you wait a few seconds, the callback gets set, and the button works fine. Initializing the callback in the html before onload gets called appears to fix the issue.

…

On Fri, Apr 12, 2024 at 8:49 PM Stuart Lynne ***@***.***> wrote: Here is the countdown table exposed in Chrome developer tools, image.png (view on web) <https://github.com/esitarski/CrossMgr/assets/297561/a653362f-ecd8-4bf7-9c11-254ccbefa134> — Reply to this email directly, view it on GitHub <#109 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABGXKJ3T6KL6TGBUP2IOCDY5B6JRAVCNFSM6AAAAAAWIVOMP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJSG42TCMZUGY> . You are receiving this because you commented.Message ID: ***@***.***>

-- Edward Sitarski

[stuartlynne]

Some progress with yesterdays CrossMgr release. Now see something on the page, get the "Press for Beeps".

Note the console error message about AudioContext was not allowed to start.

Nothing much after that, the page goes full screen.

Here is after the button is pressed. I dragged in the crossmgr screen and xls to show context.
2024-04-12-BC Provincial TT 2019-Time Trial.xlsx

I attached the test xlsx I am using.

[esitarski]

Just released an update - should be in github in an hour or so. The solution was to move all the audio initialization code into the "Press for Beeps" callback function, including creating the AudioContext itself. Chrome added a warning about creating an AudioContext outside of a "user gesture". Lots of people complained about this as the spec says that playing a sound is prohibited, not creating the AudioContext itself. Not my fault, but you can't fight Google. I didn't see this problem in Linux, so I suspect that other browsers/platforms behave differently.

…

On Fri, Apr 19, 2024 at 2:22 PM Stuart Lynne ***@***.***> wrote: Some progress with yesterdays CrossMgr release. Now see something on the page, get the "Press for Beeps". Note the console error message about AudioContext was not allowed to start. image.png (view on web) <https://github.com/esitarski/CrossMgr/assets/297561/f453ef4a-d73d-4f8b-8e9c-f1bd27637b0c> Nothing much after that, the page goes full screen. Here is after the button is pressed. I dragged in the crossmgr screen and xls to show context. 2024-04-12-BC Provincial TT 2019-Time Trial.xlsx <https://github.com/esitarski/CrossMgr/files/15044325/2024-04-12-BC.Provincial.TT.2019-Time.Trial.xlsx> image.png (view on web) <https://github.com/esitarski/CrossMgr/assets/297561/c9c4c403-97ca-46d9-8e60-1ba1ed16efa8> I attached the test xlsx I am using. — Reply to this email directly, view it on GitHub <#109 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABGXKO7RTDPD2ELMGCV6CTY6FOF5AVCNFSM6AAAAAAWIVOMP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRXGA4DAMJVGM> . You are receiving this because you commented.Message ID: ***@***.***>

-- Edward Sitarski

[stuartlynne]

Tested with current version today.

For Chrome in Windows, Linux and IOS click on Beep gets a nice set of beeps.

After that nothing.

[stuartlynne]

I dug up an old version of CrossMgr, 3.0.33 from 2019.

I'm getting the countdown clock, and get proper beeps in Chrome for Windows, Linux, IOS and Safari in IOS.

[esitarski]

I have tested it many times and can't make it fail. Can you do me a big favor? When it stops, in Chrome, click on the three vertical dots on the right, then select *Developer Tools*. Then click on the *Console* tab. There should be an error message in there. Send me the screen capture. Thanks!

…

On Sun, May 19, 2024 at 3:08 PM Stuart Lynne ***@***.***> wrote: I dug up an old version of CrossMgr, 3.0.33 from 2019. I'm getting the countdown clock, and get proper beeps in Chrome for Windows, Linux, IOS and Safari in IOS. image.png (view on web) <https://github.com/esitarski/CrossMgr/assets/297561/1844b875-3911-485b-a0fe-ce7a39644e6e> — Reply to this email directly, view it on GitHub <#109 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABGXKJWCRIJPGTAGBUU5UTZDD2EFAVCNFSM6AAAAAAWIVOMP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZGMZTCOJXGI> . You are receiving this because you commented.Message ID: ***@***.***>

-- Edward Sitarski

[esitarski]

This is strange as the only changes I made were to do the audio initialization after the Beep button was pressed as this was required by the most recent version of Chrome. It is possible that you are running into some issue with the data. Anyway, the error shown in the *Console* page should settle the matter. On Mon, May 20, 2024 at 8:32 AM Edward Sitarski ***@***.***> wrote:

…

I have tested it many times and can't make it fail. Can you do me a big favor? When it stops, in Chrome, click on the three vertical dots on the right, then select *Developer Tools*. Then click on the *Console* tab. There should be an error message in there. Send me the screen capture. Thanks! On Sun, May 19, 2024 at 3:08 PM Stuart Lynne ***@***.***> wrote: > I dug up an old version of CrossMgr, 3.0.33 from 2019. > > I'm getting the countdown clock, and get proper beeps in Chrome for > Windows, Linux, IOS and Safari in IOS. > > image.png (view on web) > <https://github.com/esitarski/CrossMgr/assets/297561/1844b875-3911-485b-a0fe-ce7a39644e6e> > > — > Reply to this email directly, view it on GitHub > <#109 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AABGXKJWCRIJPGTAGBUU5UTZDD2EFAVCNFSM6AAAAAAWIVOMP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZGMZTCOJXGI> > . > You are receiving this because you commented.Message ID: > ***@***.***> > -- Edward Sitarski

-- Edward Sitarski

[stuartlynne]

No errors other than some associated with (probably) some ad blockers. Have you tried with an iPhone? I get the same results with both Safari and Chrome on my iPhone. I tried an (older) Android phone I have, but can't convince Chrome to go to an IP address even with HTTP://192.168.40.40:8765 as the URL. Linux in the first screen: [image: image.png] Countdown screen (with Log XMLHttpRequests turned on: [image: image.png] On Mon, May 20, 2024 at 5:33 AM Edward Sitarski ***@***.***> wrote:

…

I have tested it many times and can't make it fail. Can you do me a big favor? When it stops, in Chrome, click on the three vertical dots on the right, then select *Developer Tools*. Then click on the *Console* tab. There should be an error message in there. Send me the screen capture. Thanks! On Sun, May 19, 2024 at 3:08 PM Stuart Lynne ***@***.***> wrote: > I dug up an old version of CrossMgr, 3.0.33 from 2019. > > I'm getting the countdown clock, and get proper beeps in Chrome for > Windows, Linux, IOS and Safari in IOS. > > image.png (view on web) > < https://github.com/esitarski/CrossMgr/assets/297561/1844b875-3911-485b-a0fe-ce7a39644e6e> > > — > Reply to this email directly, view it on GitHub > < #109 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AABGXKJWCRIJPGTAGBUU5UTZDD2EFAVCNFSM6AAAAAAWIVOMP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZGMZTCOJXGI> > . > You are receiving this because you commented.Message ID: > ***@***.***> > -- Edward Sitarski — Reply to this email directly, view it on GitHub <#109 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACIUWKBZUHTAU2FYM76QYLZDHUR5AVCNFSM6AAAAAAWIVOMP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGM3TCMJXGM> . You are receiving this because you commented.Message ID: ***@***.***>

--

__________O___________ _______-\<,____________ _____(_)/_(_)___________

_________________________ ***@***.***>____604-518-1749(m)__604-461-7532(h)