| |
| |
| |
|
Page: 1 2
Comments:
<0> ht311 : you'll be happy to know i've got almost a day's worth of overtime so far this week
<0> and have still managed to be of use to the channel :-)
<1> unbelievable
<0> oops, wrong window
<0> hehe
<0> yeah, they still think they're going live
<0> and the freeze starts tomorrow afternoon.
<0> well, actually it starts the 18th
<1> seem you can rack up more overtime then :D
<0> yeah
<0> btw, on of the dev's is about to have a baby... you know how much paternity leave he gets?
<0> 12 weeks, 95% salary! (and that's in addition to what the mother gets from the govt)
<1> a lot if he want
<1> 40 week with 55%
<0> i'm planning babies so i can have next summer off
<1> or 55 week with 50
<0> hehe, yeah, if the wife works
<0> heh, year off. woo
<1> yeah the wife work, self employed
<1> hahhahahhaa
<0> nice
<1> then you go out to do contract
<0> yup
<1> nite
<0> l8r
<2> can you only use onchange="reload(this.form)" once of a page?
<2> s/of/on
<3> I use an onchange to change a select, and I try to change the value of a input text field. I'm using document.getElementById("nameoftextinput").value ="whatever"; but it's not changing the text in the input box. what am I doing wrong?
<1> "nameoftextinput"
<1> "idoftextinput"
<3> it should be the id, not a string?
<1> id and name is different
<3> i got it. thanks
<4> 'alert("x"); return false;' how can I transform this into a function?
<4> hmm eval('function() { ' + mystr + '}');
<4> maybe that would work...
<4> holy cow, it works
<4> this looks great!!!
<4> a.onclick = create_function(elm[1] + " return false;");
<4> man.. this solves a lot of isues
<1> man you going to the darkside
<4> heh
<1> eval is Evil
<1> The eval function is the most misused feature of JavaScript. Use of eval is a cry for help.
<1> eval has aliases. Do not use the Function constructor. Do not p*** strings to setTimeout or setInterval.
<4> I'm describing a menu in an array
<4> and I need to describe the onclick event for each link
<1> still, you don't need eval to create function
<4> I want it to be like this [ ['Item1', 'alert("x");'], ['Item2', 'alert("y");'] ]
<4> looks pretty good
<1> elm.onclick = createfunction(x) { return function() { alert(x);};
<4> instead of ['Item1', function() { alert("x"); return false; }]
<1> you are just lazy
<4> the thing is that not the argument is the problem
<1> elm.onclick = createfunction(x) { return function() { alert(x);return false};
<4> I may have "RemoveCurrentItem(); DoSomethingElse(); HideMe(); return false;"
<4> and on another item just "return false;"
<1> eval is Evil
<1> The eval function is the most misused feature of JavaScript. Use of eval is a cry for help.
<1> eval has aliases. Do not use the Function constructor. Do not p*** strings to setTimeout or setInterval.
<4> heh
<1> people will stone you if you run into problem with eval
<4> and what solution would you have for this thing
<4> I don't think I will, it's not something that bad what I'm doing... and it's the most simple method I can think of to solve this problem in a "cute" way
<1> well, your 2nd array will be a ok one
<4> hmm should I go for the second one?
<4> it will be considerably easyer to describe the elements with the eval method, and it will look better
<1> any alternative other than eval
<1> people will hang you on a cross for using eval
<4> ya, I guess you're right, it's bad design
<4> can anybody see something wrong in here? <a href="#" onclick="jmp_to('home'); return false; ">Home</a> ?
<4> ie doesn't get to jmp_to
<5> try removing the #
<5> and using summit like "javascript:void(0)"
<5> to test
<4> right
<4> anybody else?
<4> tho, thanks for trying to help ;)
<4> it dies when it calls jmp_to('something')
<5> then i would say its a malformed function
<5> check ur function
<4> it's not
<5> sk8ing> ie doesn't get to jmp_to
<5> u didnt say it dies then
<5> u said it doesnt get to THEN
<4> well, it doesn't get TO IT
<4> it dies while calling
<5> then its the function
<4> no, it's not
<5> it is
<5> coz that is correct syntax
<5> <a href="#" onclick="jmp_to('home'); return false; ">Home</a>
<5> thats COrrect
<5> function jum_to(what) { alert("what") }
<4> function jmp_to(to) { alert('x'); } this is correct too
<4> that's what I have
<5> try change ur ' for a "
<4> come on...
<5> come on what
<4> it's not that
<5> have u tried it
<5> then how do u know
<4> I just know
<5> then u have some other **** code in there that the browser doesnt like
<5> good luck
<4> anyhow, somebody that has a clue? any idea why IE would throw an error in such a simple situation?
<5> i have a clue u prick just cant be bothered to help ***holes :)
<4> thanks, but in this situation I don't need "help" to see where my code is broken
<4> cuz I know it isn't
<5> then why doesnt it work lmfao
<4> if you don't know about the bug, just shut up and let someone else do the talking
<5> or not
<4> it's deffinitely a bug, and it's probably present only in some special situations
<5> if u say so
<4> I want to know what might have set the bug free
<4> the function is fine
<4> works in FF, works in IE outside of all the other functions
<4> something else is wrong
<4> IE messes something up at some point
<5> funny that
<5> it works here fine
<4> of course it does
<5> again i say IT MUST BE SOME OTHER CODE IE DOESNT LIKE
<4> not necesarly
<4> but it may be an option
<5> well if it works with no other functions on and doesnt with another function / peice of code
<5> then it must be
<5> fuill stop
<4> it's a 3k lines script that runs with out throwing any exception in FF, I can't comment each line to see what bothers it
<4> none of the functions seems to be defined
<4> that would be a problem huh?
<5> install the FF debugger
<5> and see whats doing it
<4> on FF works fine!
<4> no parsing error on IE, nothing
<5> just install the debugger
<5> and u will see whats wrong
<4> I found the area where the problem is..
<4> it's a cl***... if I have anything defined inside it the whole code doesn't want to work anymore
<4> found the problem
<4> IE ****s
<4> having this.cl*** in that cl*** seems to make it ignore the whole file
<4> function test() { this.cl*** = 'a'; } function blah() { alert('x'); } <a href="#" onclick="blah(); return false; ">adfas</a>
<4> try it out
<4> now everything works fine
<6> hrm
<6> What are we testing?
<6> and why are you using inline event handlers?
Return to
#javascript
or
Go to some related
logs:
#teens
capilene vs smartwool
#java
gcc tr1 gentoo
umw tornado
three dollar bill cliton
#linux
overknocking
undernet ziplok
#mirc
|
|