News for hackers. Stuff that matters.

A comment on Chrome will aggressively throttle background tabs. Parent comment

Re:Chrome will aggressively throttle background tabs by onion2k on Tuesday January 24, 2017 @12:05PM (#13473162)
As a developer you need to decide whether or not to support a browser, and if that browser doesn't provide the APIs you need then you should drop support for that feature in that browser. In this case, if Chrome is making a change that you can't or won't change your game for then the solution is to detect Chrome and display a "This game only works in a single tab in Chrome. Try Firefox!" message if a user opens it in a second tab.
[ Parent | on HN ]
Re:Chrome will aggressively throttle background tabs by PetahNZ on Tuesday January 24, 2017 @12:28PM (#13473423)
It's your customers that generally dictate what browser you support.
[ Parent | on HN ]
Re:Chrome will aggressively throttle background tabs by xiaoma on Tuesday January 24, 2017 @12:50PM (#13473642)
Not if you have content or apps they really want.

I prefer Firefox, but since Google broke Google Voice (now Hangouts) plugin for FF users, I've been grudgingly opening a Chrome browser each time I want to make a phone call to US number.

[ Parent | on HN ]
Re:Chrome will aggressively throttle background tabs by onion2k on Tuesday January 24, 2017 @04:37PM (#13475780)
Some people are in the fortunate position where they can choose to ignore large sections of their potential customer base. Someone who writes a game as (presumably) a side project is in exactly that position.
[ Parent | on HN ]
Re:Chrome will aggressively throttle background tabs by rhizome on Tuesday January 24, 2017 @12:38PM (#13473512)
If you don't support a browser, how do you learn whether its users are your customers?
[ Parent | on HN ]