ebay.de - internal function problem

[JoeyG]

Hello again from Berlin,

Using a brand-new profile with the latest versions of both Pale Moon and Basilisk, and after logging in, this internal function of ebay.de doesn't work.



It works properly with the latest Firefox.

I'll be happy to provide any more information that might be required to help analyse the problem, but I'll need some guidance regarding how to get it.

Thank you.

P.S. I'm not sure if there are other issues.

[Moonchild]

This is a known issue.
eBay has already been informed of this (in detail, including what to do to fix) but they don't seem to want to fix it.

[JoeyG]

Oh, please excuse me. I wasn't aware it's already been brought up.

Thanks for the information.

[rodndtube]

Using eBay is also a problem with Basilisk. If eBay doesn't address the issue then we are SOL using Pale Moon and Basilisk? This must be frustrating. Can this issue be resolved by changing the user agent?

[Lunokhod]

It's some javascript thing:
viewtopic.php?f=3&t=24450&p=212925&hili ... rn#p212925
It's possible to test if the button is enabled without making a return, providing you didn't proceed further, but it doesn't sound like a user agent would fix it unless an alternate code path was offered as a result, more like something related to how the browser javascript engine interprets presumably faulty code. Although I don't really know personally, that's only my impression from reading Moonchild's answer.

[Moonchild]

An event handler will have the event reference as a parameter.
ebay's scripting simply needs to use that passed-in event in the handler and not some ambiguous globally defined "event".
But, they are simply refusing to make the necessary change to their scripting which means it will only work in Chrome and workalikes.

i.e.: they are currently using something like:

Code: Select all

function radiobuttonhandler() {
event.preventDefault();
do_something;
}

While they should be using:

Code: Select all

function radiobuttonhandler(ev) {
ev.preventDefault();
do_something;
}

with "event" not being defined, the function will abort on the first line and will never get to do_something (in this case activating the next button)

[moonbat]

Is this global event thing some sort of draft Javascript feature, or just Chrome whitewashing sloppy coding habits?

[vannilla]

Is this global event thing some sort of draft Javascript feature, or just Chrome whitewashing sloppy coding habits?

According to MDN is a "deprecated" feature. And it seems to have been introduced by Chrome, if the compatibility table is correct.

[Moonchild]

And it seems to have been introduced by Chrome

No it was an MSIE4 thing.

[moonbat]

So Chrome enables shitty coding habits introduced by its spiritual ancestor. Lovely