eBay is terrible to use these days (terrible script lag?)...

[the86d]

Firefox:


Chrome too, just points to a different server:




Both on Firefox AND Chrome scripts sit waiting for data, and constantly update data that doesn't seem to be readily accessible from eBay's own site? This is my guess.

The only add-ons I add is a dark reader, but w/out ANY add-ons, or a complete Firefox "refresh" same thing. Same on Chrome, LAG.

If you load about any page that has product listings in it, then this is the case. Work machine, home machine, different browsers, all current browsers, Win 10, and 7.

Can't scroll more than 1.5 pages down w/out eBay's site "trying" to parse data?

Anybody else experiencing this, only on eBay's site?

[dracer]

no , works great for me search for things every day , using win 10 and chrome

[jdfthetech]

ebay is re-parsing the HTML that sellers use to cut out sections it doesn't like. This is causing many sporadic issues. I write all my ebay listings using very basic HTML5 and yet things like flexbox don't parse correctly and cause terrible problems with the listings.

eBay has really screwed the pooch the past few months. You are not alone.

[the86d]

while (bullets > 0 && target == 1){fire == 1;}

Your sig... "Crobots" code, only you used "bullets" in place of "missiles", as I recall?

[ocabj]

Isn't fire==1 in that context semantically incorrect? == is a comparison operator, not an assignment operator. So the content of the while loop is only going to check if the fire variable is 1, as opposed to actually doing an action (setting a variable, running another function, etc).

Wouldn't something like this more appropriate:

while (bullets > 0 && target == 1) { fire(); }

or

while (bullets > 0 && target == 1) { fire = 1; }

But even then, simply setting a variable like in the second choice above will not actually result in an action either, since setting a variable will not have any effect until the while loop is exited, since there is no action (function, sub-routine) in the conditional loop.

[jdfthetech]

Isn't fire==1 in that context semantically incorrect? == is a comparison operator, not an assignment operator. So the content of the while loop is only going to check if the fire variable is 1, as opposed to actually doing an action (setting a variable, running another function, etc).

Wouldn't something like this more appropriate:

while (bullets > 0 && target == 1) { fire(); }

or

while (bullets > 0 && target == 1) { fire = 1; }

But even then, simply setting a variable like in the second choice above will not actually result in an action either, since setting a variable will not have any effect until the while loop is exited, since there is no action (function, sub-routine) in the conditional loop.

depends how you define fire. . . but try not to read too much into it, it's just pseudo code not meant for consumption

. . . and as for the thing about crobots, don't know what crobots is, I was just goofing around when I made the sig


edit: but technically yes, using a conditional to define a value shouldn't happen so you're right in the end

[bbodybill]

Had a "Negative" feedback to a seller... CANCELLED yesterday... Seller took MORE than 3 weeks to ship-advertised, "normally ship in 5 days"...

FORK THEM !!!!