Well, on my Macbook Mojave I just downloaded Chrome because the bandlab.com, which just started playing with, supports this browser but not Safari.
But now that I have Chrome on my mac, I may as well start studying its intricacies. It gives me the chance to study the behavior of my Herman web video game on browsers other than Safari.
One of the problems I came up with is an error on the support of the Web Audio API that stated: "The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page." When I went to a webpage of mine that uses the webaudio oscillator, it worked, but when I back-spaced to a previous page that used same, I got this error. On Safari this didn't happen. As an owner of a website, I consider it a good idea to mess with other major browsers. As Safari uses the Webkit engine, currently Chrome seems to use Blink. How this affects the performance of webpages that use Web Audio I haven't yet studied.
As much as I'd like to think that Safari can walk on water and be the only browser that I ever need to use on my mac, as webmaster it's good to experiment with other browsers. Experimentation like this can help me work with more platform-indepentant code on my website.
No comments:
Post a Comment