Board Game Arena

I always play on BGA via a Windows browser. If I need help with any item, I hover my mouse over it to activate the pop-up. I am currently traveling and am taking my turns on an iPhone. I am unable to activate any pop-ups. Is there a particular technique I have to use to get the explanation bubble to appear?

I have tried holding my finger down, swiping, double taps, etc.

Tks

Anyone? I’m assuming there is a way, but if there is, I can’t find it. Am just playing without any player aids on my phone, and it is frustrating. Any time I tap, it assumes I want to carry out that action. If I hold, browser options unrelated to BGA come up. If I swipe, scrolling is activated. Does no one else try to play on iPhone?

Currently trying to play Great Western Trail, but help activating any pop ups is appreciated.

Try a long touch (but not sure it is working for every case).

Lunalol wrote: ↑25 August 2023, 10:48 Try a long touch (but not sure it is working for every case).

Yes, my partner uses iOS devices and often complains they don't work. It seems to be implemented on a per game basis (I'm guessing not all devs realise they have to do something particular to support iOS). His solution when it doesn't work is to wait til he's back in front of a computer to play those particular games.

I'm guessing not all devs realize they have to do something particular to support iOS

I'm guessing if iOS devs realize they have something particular to do to be supported by www standards.

Lunalol wrote: ↑25 August 2023, 17:04 I'm guessing if iOS devs realize they have something particular to do to be supported by www standards.

I'm not sure what you mean? I'm just talking about the dev environment for BGA. I don't personally develop games on BGA, so I'm only guessing, but I do write software for a living, so I have a vague idea. In general for this kind of thing there's a framework that allows common actions to be done more easily. But what works as "long press" on an android mobile device, or "hover" on a computer may have some kind of different command required to support the same in iOS. That's one of the hassles of writing web-based software. Every interface you apply it to works just a little differently. It's not an easy task sometimes. On top of that, if a dev doesn't have an iOS device to test with, that's even more reason why they may not realise it's not working the way they intended.

Yes, it would be nice if it all worked consistently. But devs are volunteers so sometimes you get what you get. If something isn't working properly, raise a bug, but as I say, I don't know if the reason it's implemented sporadically is because some devs don't realise how to support iOS for long pressing, or because it just doesn't work in some cases, so it may not always be possible.