Javascript errors

Just to let ya know; ATS is throwing profuse _javascript errors.

I'm a web developer and frequently will visit ATS while one of my "debuggers" is open, they are detecting your errors, which are on virtually every page.

reply to post by tanka418

If you're a web developer, this may sound like an obvious inquiry. Is your java up to date, and all old versions removed? Or can you actually pin it down to ATS's code?

Klassified
reply to post by tanka418

 

If you're a web developer, this may sound like an obvious inquiry. Is your java up to date, and all old versions removed? Or can you actually pin it down to ATS's code?

I take it you are not a developer (software engineer). JavaScript is native to One's browser, there fore IF one has an up to date browser; like IE/10, the latest Firefox, or Chrome, or any of the Apple browsers; then their "_javascript" engine is automatically up-to-date.


But, just so we are quite clear; it is ATS _javascript:

$("#pbgcolor").spectrum([
showInput: true,
showInitial: true,
preferredFormat: "hex"
]);
$("#data2").spectrum([
showInput: true,
showInitial: true,
preferredFormat: "hex"
]);

The error: the identifier "spectrum" is undefined.

give me a "postback" and I'll give you a URL.

www.abovetopsecret.com...
www.abovetopsecret.com...

And, that boys and girls usually costs around $500.00

reply to post by Klassified


Java is not related to _javascript in anyway, besides sharing the word 'java'

reply to post by tanka418

No. I am not a developer. Thank you for the clarification. I have reported this thread to Skeptic Overlord, and I'm sure he'll be taking a look at it when he gets a chance.

reply to post by Kr0nZ

Kr0nZ, I really like that avatar. lol.

tanka418
Just to let ya know; ATS is throwing profuse _javascript errors.

I'm a web developer and frequently will visit ATS while one of my "debuggers" is open, they are detecting your errors, which are on virtually every page.

im a software engineer and don't see any errors. Must be your system.

reply to post by tanka418

Got the saame, also getTrigger error has been there for a very long time for me.

I did once send some stuff on all the CSS error/warnings. Don't think they were addressed. New stuff now.

ZetaRediculian
im a software engineer and don't see any errors. Must be your system.

Start your dev system. You know...Visual Studio, and use IE/any.

tanka418

ZetaRediculian
im a software engineer and don't see any errors. Must be your system.

Start your dev system. You know...Visual Studio, and use IE/any.

Yeah...visual studio? For java script? It's jquery code specifically.

$("#picker").spectrum([
color: tinycolor,
flat: bool,
showInput: bool,
showInitial: bool,
showAlpha: bool,
disabled: bool,
localStorageKey: string,
showPalette: bool,
showPaletteOnly: bool,
showSelectionPalette: bool,
clickoutFiresChange: bool,
cancelText: string,
chooseText: string,
className: string,
preferredFormat: string,
maxSelectionSize: int,
palette: [[string]],
selectionPalette: [string]
]);

bgrins.github.io...

It's some color picker function. Probably missing a reference to the spectrum.js file. I have all my debug tools at work but I'm not going to bother debugging ATS while I'm working besides it doesn't look like much of anything anyway.

You should be able to reference the file in your debug tool and see if it fixes it. The file reference is here: bgrins.github.io...

reply to post by ZetaRediculian


Like I actually care about the exception or its source.

I saw an issue; thought I might be helpful.

tanka418
reply to post by ZetaRediculian

 

Like I actually care about the exception or its source.

I saw an issue; thought I might be helpful.

The source of the error is from a jquery plugin that's missing its reference. There is nothing with the id "pbgcolor" anywhere either. The code block is probably leftover from the switch to the new UI. its probably annoying if you leave your debugger open in VS. Other than that, it probably doesn't effect the rest of the terrestrial population.

"profuse __javascript errors." it is not.

reply to post by ZetaRediculian


So I guess the error should just be left. Its not visible to most, and has little effect on overall operation, so no need to address it, no need to fix it.

If I worked like that I would be out of a job in a matter of days.

reply to post by tanka418

It should be prioritized accordingly. If I represented that as a "profuse JavaScript error" to my team...Well.

I am certain there are more pressing issues than not annoying you.

a reply to: tanka418