This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

5

Side note, tapping is how you get all the on-hover events to trigger, like the flag/vote buttons for comments
–
Ben BrockaApr 15 '12 at 16:10

Another side note: on the mobile theme, usage is very clear. But the iPad is using the regular site. One more reason to want the mobile look & feel for spoilers on the regular sites too!
–
ArjanApr 15 '12 at 18:33

As one needs to scroll code blocks with 2 fingers (or at least it used to be like that): does using 2 fingers help?
–
ArjanJun 29 '12 at 16:52

More specifically, you can only click to view the spoiler if the "Was this post useful to you?" controls are present, apparently. I'm unclear why that makes a difference at the moment.
–
Tim StoneAug 30 '12 at 20:11

Apparently (seemingly contrary to the documentation) setting the mouseover event on a non-document element causes that element to be activate-able, which allows you to trigger the hover behaviour of the descendant elements. It's worth noting that in your screenshot the event handler isn't actually applied to the spoiler by the way (it's applied to div#question.question), you just have the filter on the right hand side of the Event Listeners panel set to "All nodes"
–
Tim StoneAug 30 '12 at 21:26

@TimStone interesting. Did not know about the filter. But still, why should that affect the hover event?
–
amanaP lanaC A nalP A naM AAug 30 '12 at 21:29

3

It makes the post element something you can "click" on in iOS, which in turns allows you to trigger the hover behaviour of the spoilers. The fact that you can click the spoilers on iOS at all is an accidental side-effect of that handler being added for the post feedback feature, so in the general case showing the spoiler on an iPad is simply unsupported and likely needs to be reworked to make that more touch-screen friendly.
–
Tim StoneAug 30 '12 at 21:31

For a bug report that's gotten a fair bit of attention, this is currently rather useless. Things I would like to know: 1) Has anyone other than AmanaP reproduced this? 2) Has anyone reproduced this reliably? 3) Does this affect all three iPads? 4) Does this affect current (iOS 6) versions of Safari? 5) Does this affect tablets that aren't iPads? 6) If you switch to the mobile theme (using the link in the footer) does that correct the problem?
–
Shog9♦Sep 21 '12 at 4:57

@Shog9 it has been tested on all tablets when logged in tapping on the spoiler does not work. When logged out, it works fine. See discussion on KennyTMs deleted answer.
–
amanaP lanaC A nalP A naM ASep 21 '12 at 13:10

@Shog9 switching to the mobile theme makes no sense! that is completely different. I am talking about using the main site not the mobile one.
–
amanaP lanaC A nalP A naM ASep 21 '12 at 13:11

@Shog9: last I checked, I'm not amanaP. This bug can be reproduced 100% reliably: just log in on an iPad, any iPad. (And anyone who seriously wants people to use the mobile theme on an iPad needs to get their head out of certain parts of their anatomy.)
–
MartiSep 21 '12 at 15:11

AmanaP, @Marti: you seem to be taking this rather too personally. I don't care which theme you use, and I can't test this myself - I just want a clear, comprehensive bug report. I've done as much as I can to flesh this out with the information that was here, so if you can fill in the blanks I've identified above, that will go a long way toward making this something worth discussing.
–
Shog9♦Sep 21 '12 at 16:34

@Shog9 would editing this question to include the questions asked above move it towards being fixed? I am willing to put in the legwork to file a good bug report. Just confirm that the above is what you need and I'll make it happen. :)
–
ahsteeleMar 15 '13 at 18:22

@amanaPlanaCAnalPAnaMA: #1. See the update, it will not show all spoilers until you click. #2. Well it is a hack :), Safari should respond to :hover. Maybe we should blame Apple.
–
kennytmAug 24 '12 at 17:43

Have you tested this again? It seems that they have fixed this bug.
–
nhahtdhAug 27 '12 at 7:05