Unfortunately, it sounds like your tablet simply doesn't like some of our dynamic components. You might want to leave the details in our Website Feedback forum.The issue still occurs, it does not appear to be possible to access the survey/competition from a windows 10 tablet.
Steps:
On this page http://paizo.com/pathfinderRPG/bestiary5
Tap on the link for 'Round 1: Top 16 Monsters'
The whole pages refreshes back to the same page.
I don't think that this is an isolated issue.
I have now tried it from three different windows 10 pcs (from different manufacturers). In all cases the link fails when using touch. It works correctly if clicked with a mouse (although this is not possible on tablets - this is no mouse).
This issue is definitely with your code, and not with my machine.
This is yet another example of Paizo's continued distain for windows users, who account for 97% of your users.
Cross-posted in web-site feedback, because apparently it is not possible for you to forward this on to the correct staff.
In all cases the link fails when using touch. It works correctly if clicked with a mouse (although this is not possible on tablets - this is no mouse).
This issue is definitely with your code, and not with my machine.
This is yet another example of Paizo's continued distain for windows users, who account for 97% of your users.
This sounds like a Tablet/touchscreen problem, not an OS problem, since it works fine using a mouse.
This is yet another example of Paizo's continued distain for windows users, who account for 97% of your users.Windows is fine. This sounds like a Tablet/touchscreen problem, not an OS problem.
As I said, this is not a tablet issue. It also occurs on a windows 10 Dell XPS 12 laptop, where quite a few of the links on the Paizo site fail with touch but work with a mouse.
The page receives the event, the HTML click event fires, but the underlying code returns the original page rather that the correct page. I suspect that the underlying code relies on properties of a legacy MOUSE event, and the touch event is being allowed to tunnel down to the page in general and not being absorbed by the element catching the event.
I am an developer in HTML, C# and C++ code, I can state with certainty that the problem is NOT with my machines.
| 2 people marked this as a favorite. |
Antony, I understand you're upset that the functionality isn't working. However, our Community Team cannot correct the issue, which is why I suggested detailing the error in this forum in more detail so that our Tech Team can assist. I can assure you that nobody in our office has a "disdain" for a certain subset of our customers, and our goal is to cater to as many browsers and devices as is possible within our work flow. I've notified the manager of our Tech Team about this thread, so that he can assist you further.
| 1 person marked this as a favorite. |
As I said, this is not a tablet issue. It also occurs on a windows 10 Dell XPS 12 laptop, where quite a few of the links on the Paizo site fail with touch but work with a mouse.This is yet another example of Paizo's continued distain for windows users, who account for 97% of your users.Windows is fine. This sounds like a Tablet/touchscreen problem, not an OS problem.
Hence the /touchscreen part of the comment.
If it works fine with a mouse, then the problem is not on Paizo's end, it's far more likely on whatever recognition software or hardware is associated with your touchscreen(s).
As I said, this is not a tablet issue. It also occurs on a windows 10 Dell XPS 12 laptop, where quite a few of the links on the Paizo site fail with touch but work with a mouse.This is yet another example of Paizo's continued distain for windows users, who account for 97% of your users.Windows is fine. This sounds like a Tablet/touchscreen problem, not an OS problem.Hence the /touchscreen part of the comment.
If it works fine with a mouse, then the problem is not on Paizo's end, it's far more likely on whatever recognition software or hardware is associated with your touchscreen(s).
Please see my edited response above, the issue is DEFINATELY with the code on the Paizo site.
Also, tracing the code that fires on the event, the backend code attempts to return the correct page, then another event fires and it then returns the original page, implying that the original handler is not trapping the touch and allowing it to fall through to the main page.
As I said, this is not a tablet issue. It also occurs on a windows 10 Dell XPS 12 laptop, where quite a few of the links on the Paizo site fail with touch but work with a mouse.This is yet another example of Paizo's continued distain for windows users, who account for 97% of your users.Windows is fine. This sounds like a Tablet/touchscreen problem, not an OS problem.Hence the /touchscreen part of the comment.
If it works fine with a mouse, then the problem is not on Paizo's end, it's far more likely on whatever recognition software or hardware is associated with your touchscreen(s).
Please see my edited response above, the issue is DEFINATELY with the code on the Paizo site.
Also, tracing the code that fires on the event, the backend code attempts to return the correct page, then another event fires and it then returns the original page, implying that the original handler is not trapping the touch and allowing it to fall through to the main page.
Further investigation:
The Onclick handler on the 'Top 16...' link is designed to rebuild part of the page, and not to refresh the page as a whole.
The handler is replying on 'return false' to stop the propagation of the event (stopping the 'a' tag from loading a new, linked page).
Unfortunately, 'return false' only stops the default event (in this case the default would be a click event) it does not stop the popagation of other events, such as a touch.
This causes the 'a' link to navigate the whole page to the url it has been given, which in this instance causes the page to refresh.
See:
http://stackoverflow.com/questions/128923/whats-the-effect-of-adding-return -false-to-an-onclick-event
for examples and workarounds.
Regards,
Antony
As I said, this is not a tablet issue. It also occurs on a windows 10 Dell XPS 12 laptop, where quite a few of the links on the Paizo site fail with touch but work with a mouse.This is yet another example of Paizo's continued distain for windows users, who account for 97% of your users.Windows is fine. This sounds like a Tablet/touchscreen problem, not an OS problem.Hence the /touchscreen part of the comment.
If it works fine with a mouse, then the problem is not on Paizo's end, it's far more likely on whatever recognition software or hardware is associated with your touchscreen(s).
Please see my edited response above, the issue is DEFINATELY with the code on the Paizo site.
Also, tracing the code that fires on the event, the backend code attempts to return the correct page, then another event fires and it then returns the original page, implying that the original handler is not trapping the touch and allowing it to fall through to the main page.
Further investigation:
The Onclick handler on the 'Top 16...' link is designed to rebuild part of the page, and not to refresh the page as a whole.
The handler is replying on 'return false' to stop the propagation of the event (stopping the 'a' tag from loading a new, linked page).
Unfortunately, 'return false' only stops the default event (in this case the default would be a click event) it does not stop the popagation of other events, such as a touch.
This causes the 'a' link to navigate the whole page to the url it has been given, which in this instance causes the page to refresh.
See:
http://stackoverflow.com/questions/128923/whats-the-effect-of-adding-return -false-to-an-onclick-event
for examples and workarounds.
Regards,
Antony
Antony, I've been able to replicate your concern on my Surface tablet using touch interface, however if you have a tablet with a touchpad mouse controller (the Surface keyboard cover has one, as do most of the detachable keyboards for tablets) or a Bluetooth mouse using that interface sends a more mainstream "click" event and the interface works correctly.
We will certainly look at integrating more touch friendly components as we do further development on the site, but as with any development team we have to make choices as to where we devote our limited resources. We appreciate you bringing the issue to our attention.
Antony, I've been able to replicate your concern on my Surface tablet using touch interface, however...As I said, this is not a tablet issue. It also occurs on a windows 10 Dell XPS 12 laptop, where quite a few of the links on the Paizo site fail with touch but work with a mouse.This is yet another example of Paizo's continued distain for windows users, who account for 97% of your users.Windows is fine. This sounds like a Tablet/touchscreen problem, not an OS problem.Hence the /touchscreen part of the comment.
If it works fine with a mouse, then the problem is not on Paizo's end, it's far more likely on whatever recognition software or hardware is associated with your touchscreen(s).
Please see my edited response above, the issue is DEFINATELY with the code on the Paizo site.
Also, tracing the code that fires on the event, the backend code attempts to return the correct page, then another event fires and it then returns the original page, implying that the original handler is not trapping the touch and allowing it to fall through to the main page.
Further investigation:
The Onclick handler on the 'Top 16...' link is designed to rebuild part of the page, and not to refresh the page as a whole.
The handler is replying on 'return false' to stop the propagation of the event (stopping the 'a' tag from loading a new, linked page).
Unfortunately, 'return false' only stops the default event (in this case the default would be a click event) it does not stop the popagation of other events, such as a touch.
This causes the 'a' link to navigate the whole page to the url it has been given, which in this instance causes the page to refresh.
See:
http://stackoverflow.com/questions/128923/whats-the-effect-of-adding-return -false-to-an-onclick-event
for examples and workarounds.
Regards,
Antony
But not anyone using any of the following:
* Asus 8" tablets
* Bush 8" tablets
* Dell Venue 8
* ANY windows phone (which cannot use a Bluetooth mouse).
In addition, this is not a request just for 'touch friendly' - at present, on a windows 10 touch device, it is not possible to access parts of your site AT ALL - this effects any page which uses partial rebuilds, including all of the tabs on the product category pages:
http://paizo.com/pathfinder/modules/pathfinderRPG
http://paizo.com/pathfinder/campaignSetting/pathfinderRPG
http://paizo.com/pathfinder/companion/pathfinderRPG
etc
There, plainly, is the distain for windows users I mentioned. Maybe you should come out of your apple bubble now and again and see what is happening in the rest of the world.
Disgusted,
Antony
| 1 person marked this as a favorite. |
You know, that kind of attitude is not a very good way to get someone to help you.
Chief Technical Officer
|
| 1 person marked this as a favorite. |
There, plainly, is the distain for windows users I mentioned. Maybe you should come out of your apple bubble now and again and see what is happening in the rest of the world.
Perhaps you missed the part where Cort was talking about his Surface tablet...? That's not just for testing.
There, plainly, is the distain for windows users I mentioned. Maybe you should come out of your apple bubble now and again and see what is happening in the rest of the world.Perhaps you missed the part where Cort was talking about his Surface tablet...? That's not just for testing.
Sorry,
A surface (£290, $450US) tablet is NOT typical of the majority of Windows tablets - I know dozens of people with windows tablets, none of which are a surface, most of which are 8" or 9" tablets, without keyboards.
Conversely, I do not know anyone with an apple device - in the UK/Europe apple devices are not common, are extortionately over-priced (the cheapest ipad mini is £195 ($300US) at amazon) compared to comparable small windows tablets (8" bush tablet, argos, £65 ($100US)).
So unfortunately, testing in a single brand of windows machine, the most expensive, is not encouraging. There are a LOT of people outside of the US using windows phones and tablets without keyboards.
I spend time identifying the issue and pointing to a possible solution, and I expected a better customer-facing response than "Sorry, you need a more expensive tablet."
| 1 person marked this as a favorite. |
Antony, I believe Vic was speaking to the comment that indicated we are solely Apple focused or have a bias against Windows users (we don't). Again, we understand where you're coming from, have noted the issue, and when our Tech Team begins to look at features to support more touch functionality, it will be considered. In the interest of not fostering argument on either side, I'm going to be locking this for now.