First, thank you @seanmorley15 for this great software. I tried it in other (Desktop) browsers and it's really cool.
π Bug Description
Many UI elements (buttons) just don't respond in any browser based on Webkit. It affects the creation of events, collections (after the first has been created), the "+" button on days in collections, the "..." button to edit a collection, and probably many more. The result is that you just can't use AdventureLog on these browsers.
π Steps to Reproduce
Steps to reproduce the behavior:
- Open frontend on any Webkit-based browser
- Try to create a Location, a second collection, anything on a day in a collection, etc
- nothing happens
β
Expected Behavior
Buttons working - as they do in Chromium-based browsers
π³ Environment Details
- Platform: Docker
- Install Method: Docker Compose
- AdventureLog Version: v0.12.0 (same on v0.11)
- Reverse Proxy: Nginx, but also tested without proxy, the behavior is the same.
π Additional Context
This has been reported a couple of times before: #966, #968 and #973 are open. One of those mentions the reverse proxy but, as stated above, I tested without and it's the same with a fresh install without a proxy.
On discord it's described on https://discord.com/channels/1260594104497344512/1467074559424466965 , https://discord.com/channels/1260594104497344512/1424620580212314275 ,
https://discord.com/channels/1260594104497344512/1397841372173701241 ,
and on general p.e. on https://discord.com/channels/1260594104497344512/1260594104933548096/1450507137162805381
The same was reported on #799 which was closed by #1007 but it's not resolved, the issue persists.
As it is, it affects not only people preferring Safari (and some other desktop browsers) but more importantly everyone on an iPhone or iPad because all browsers on those must use Webkit. This excludes a very large audience from this awesome software, sadly also my friends whom I'm going on a trip with in May.
Anyway, on #799 there were some pointers on what must be done:
I'm guessing that the bug is related to a Safari behavior where ignores interactive elements without a valid href attribute or dynamically added anchor elements.
A solution could be to create a CSS rule to add cursor: pointer to all custom buttons/dropdowns/components in the app. Something like .btn { cursor: pointer; }. Or try with any of the other workarounds available
Originally posted by @ivanmendoza in #799
I'm unfortunately not a developer, but I would be willing to test extensively.
Thank you!
First, thank you @seanmorley15 for this great software. I tried it in other (Desktop) browsers and it's really cool.
π Bug Description
Many UI elements (buttons) just don't respond in any browser based on Webkit. It affects the creation of events, collections (after the first has been created), the "+" button on days in collections, the "..." button to edit a collection, and probably many more. The result is that you just can't use AdventureLog on these browsers.
π Steps to Reproduce
Steps to reproduce the behavior:
β Expected Behavior
Buttons working - as they do in Chromium-based browsers
π³ Environment Details
π Additional Context
This has been reported a couple of times before: #966, #968 and #973 are open. One of those mentions the reverse proxy but, as stated above, I tested without and it's the same with a fresh install without a proxy.
On discord it's described on https://discord.com/channels/1260594104497344512/1467074559424466965 , https://discord.com/channels/1260594104497344512/1424620580212314275 ,
https://discord.com/channels/1260594104497344512/1397841372173701241 ,
and on general p.e. on https://discord.com/channels/1260594104497344512/1260594104933548096/1450507137162805381
The same was reported on #799 which was closed by #1007 but it's not resolved, the issue persists.
As it is, it affects not only people preferring Safari (and some other desktop browsers) but more importantly everyone on an iPhone or iPad because all browsers on those must use Webkit. This excludes a very large audience from this awesome software, sadly also my friends whom I'm going on a trip with in May.
Anyway, on #799 there were some pointers on what must be done:
Originally posted by @ivanmendoza in #799
I'm unfortunately not a developer, but I would be willing to test extensively.
Thank you!