I'm having a problem where the links to my decks and inventory don't do anything when I click on them. If I right click and open in a new tab they work fine.

Details:

Configuration:
Chrome 9.0.597.98
Windows 7

Steps to repro:

Login to the site and click through on the links for a deck.

Observed:

The link is clicked and sometimes I see a wait for deckbox but most often nothing happens.

Work around:

As noted above. If I right click and open a new window it works just fine.
Dave

Can you post a link that does not work or something? 'cause I could not reproduce the error

I reproduce it every day, for all deck links, and what I do is just double-click the deck link.
Also using chrome. WinXP pro sp3.

Spoook wrote:Can you post a link that does not work or something? 'cause I could not reproduce the error

Sure thing.

here is the link i'm clicking:

http://deckbox.org/sets/33452

Vlad, thanks for the work around. The double clicking is working.

Ok, I did some more testing and here is what I discovered.

The source snippit for the link I'm clicking on is here:

<ul>
<li id="deck_33452" class="submenu_entry deck "><a href="/sets/33452" title="RDW - Koth, Dragonlord" class="simple"><img src='/images/icon_spacer.gif' class='sprite s_deck ' title=''/>RDW - Koth, Drago ...</a></li><script>Tcg.folders.setupDeck(33452);</script><li id="deck_33449" class="submenu_entry deck "><a href="/sets/33449" title="Vampire" class="simple"><img src='/images/icon_spacer.gif' class='sprite s_deck ' title=''/>Vampire</a></li>
<script>Tcg.folders.setupDeck(33449);</script>
</ul>

The main issue seams to be that the <a> tag isn't getting activated. I think the <a> isn't getting activated because a parent control is draggable the begin drag operation is getting called first even though I am not actually dragging the object. I say this because of the observed behavior. When I click down it starts the drag operation. Likely this is eating the click event. While the double click event is getting through. I'm not familiar enough with the call stack here to help further.

I hope this helps you find the issue.


I also reproduced this issue in IE 8.0.

FatPackNoob wrote:

Spoook wrote:Can you post a link that does not work or something? 'cause I could not reproduce the error

Sure thing.

here is the link i'm clicking:

http://deckbox.org/sets/33452

Vlad, thanks for the work around. The double clicking is working.

Thanks for the link, unfortunately (for you) for me it works like a charm. I'm using Firefox 3.6

Spoook wrote:

FatPackNoob wrote:

Spoook wrote:Can you post a link that does not work or something? 'cause I could not reproduce the error

Sure thing.

here is the link i'm clicking:

http://deckbox.org/sets/33452

Vlad, thanks for the work around. The double clicking is working.

Thanks for the link, unfortunately (for you) for me it works like a charm. I'm using Firefox 3.6

Do you represent deckbox.org? Is that the official response to the bug report? Obviously there will always be things that work in one browser and not another. I'm just surprised by the response.

Mnah, he's just a user... official responses come from Sebi or Laura.

Trickster wrote:Mnah, he's just a user... official responses come from Sebi or Laura.

Thanks, just learning who is who. :)

FatPackNoob wrote:

Trickster wrote:Mnah, he's just a user... official responses come from Sebi or Laura.

Thanks, just learning who is who. :)

I was just trying to reproduce the bug, so I can help, but since I didn't.. i'm off the case :)

Its probably related to Chrome, it probably handles the javascript events somehow differently than the rest of browsers. Anyway, until we get a response from sebi, there's nothing we can do.

Ok, weird: earlier today one-clicks worked fine for me as well, but now I have to double-click again.

Spoook wrote:

FatPackNoob wrote:

Trickster wrote:Mnah, he's just a user... official responses come from Sebi or Laura.

Thanks, just learning who is who. :)

I was just trying to reproduce the bug, so I can help, but since I didn't.. i'm off the case :)

Thanks for the clarification. I was like, hey man. This is still a bug for me. :)

BTW: I did reproduce the error with IE 8. Not sure if that matters since the only person I know who uses IE is my wife. :)

FatPackNoob, this is some fantastically good bug reporting you've done :)

Will check it out in the weekend.

Very late reply, I know :/ but with today's deploy this issue should also be fixed.

Thank you again FatPackNoob for a very nice bug report and sorry for postponing this so much.