| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Comments:
<0> exe: thanks :)
<1> sorry I don't know any js.. but, what would this do: function xy(){fxy = screen.width+":"+screen.height; document.snd.w.value=fxy;}
<2> It tries to set an input's value to your resolution
<2> Of course, things aren't always rooted to document so it won't always work. It might even break other script because of that.
<1> just a resolution?
<1> it's on the 'login' button
<1> onClick="xy()"
<2> Right, it fills that information just before it submits the form.
<1> how would i know -where- it submits the form?
<2> That would be the action attribute of the form element that button's in, most likely
<1> <form method="post" name="snd" action="dorf1.php"> wouldi it be that?
<2> yep
<1> thanks
<3> good evening
<4> you think?
<5> how can I find the type of an input element?
<2> .type
<5> tried input.type but that's undefined, at least in mozilla
<5> for(i in document.getElementsByTagName("input")) { 14 alert(i.type); 15 }
<2> ...
<5> alert yields undefined
<2> i there is an index, not an element.
<5> ugh
<2> And don't use for..in for array-type objects, you'll get non-numerical elements.
<2> Sad, but true
<5> indeed
<5> hmm
<5> still get undefined
<6> Hello, is it possible to call an event inside a page that will be loaded using ajax just after it is loaded?
<5> 13 var a = document.getElementsByTagName("input"); 14 for(i in a) { 15 alert(a[i].type);
<2> Because it's not an element.
<2> for(var i=0; i<a.length; i++)
<5> ok
<5> b0at: now it doesn't even enter the for loop, a.length is 0
<5> But there are input elements on the page
<2> `js onload # this problem?
<7> js onload: www.edea.se/Onload
<5> link timed out
<5> but it is a function called onload
<2> It sounds like it's being run before the page fully loads.
<8> It seems, onselect doesn't work for <select><option></option></select> group, How can I activate a call when user made a selection?
<2> xinming: onchange, not onselect.
<5> <body onload="test()"> shouldnt that only run once the page is loaded?
<8> b0at, thanks.
<2> johnjay: yes
<5> b0at: nevermind, figured it out
<5> overiding events
<5> thanks, it all works as expected now
<8> b0at, then, how do I get the value user selected?
<8> b0at, and onchange doesn't work for option. I must handle it in select.
<2> xinming: sel.options[sel.selectedIndex].value
<2> That's right. Option doesn't fire anything.
<8> thanks
<9> im am rather new to js, so a lot of stuff you had to do in a roundabout way in the past I dont know about, is that the case with this, or is it just the worst logic ever? http://erxz.com/pb/2354
<10> MM_* disqualifies as programming
<10> but it should work
<11> TheSeer, you don't like M&M or?
<10> MM_* is macromedia...
<10> which is ugly and hacky code generated by so called wysiwyg editor
<11> TheSeer, yea, I really wonder.. will the next DW have those as AD_* ?
<10> trying to fix their broken code design is not worth the effort..
<12> anyone know the semantics of onunload?
<11> TheSeer, I remember using those on tight deadlines when i needed a quick drop down menu or rollovers.. (I had no idea of CSS rollover back then)
<10> suv4x4: well.. IE still hasn't .. so don't mind :P
<11> TheSeer, well for rollovers (images) it works ok
<11> but ya..
<11> TheSeer, btw depends on your definition of "still doesn't have it" :)
<11> TheSeer, IE7 have 'em
<10> IE7 is unusable ;)
<11> O_O
<11> it is?
<11> it looks like a mix of Opera and FF, how can it be not usable :D hehe
<10> yeah.. i mean.. ie 6 already is bad...
<11> TheSeer, yea, this is why I said depends how you define "still doesn't have it" :)
<11> but soon... pretty soon
<11> like 4 years soon
<11> or so
<10> well.. i installed the beta version .. and removed it after playing with it for like 3 hours
<10> f*cking annoying
<11> which beta
<10> beta 3?
<12> suv4x4: I doubt it
<10> i believe it was beta3...
<12> suv4x4: some retards are still using IE5
<11> beta 3 is looking ok to me. The interface is retarded, but one can get used to it. Plus I don't care about that part, just the rendering
<10> the rendering is still buggy...
<10> it only has the most basic css fixes applied
<11> frb, they are not retards, they just don't know a reason to switch. Some are still on Netscape 2 Gold
<10> and yes.. the retarded interface makes IE7 unusable
<12> suv4x4: even my dad upgrades his software twice a decade
<11> TheSeer, ah I wouldn't call fixing over 20 major bugs "most basic", especially adding CSS2 selectors, support for fixed, PNG transaprency, pseudo cl***es..
<11> IE6 is crap
<10> suv4x4: well.. CSS2 is standard for years now
<11> don't make it seem as if IE7 is just IE6 with sugar on top
<11> there's been some major work done here
<10> upgrading to that stanard is a basic requirement for a product that considers itself a browser
<11> TheSeer, if you were ***igned to take IE6 to IE7 and after months of hard work someone comes and says "it's been a standard for year, screw off" - would that be fair?
<11> years I mean
<11> acknowledge the work done. Major issues have been fixed
<11> it's not where FF is, but think of it in practical terms
<2> The fact the IE dev blogs made it sound like fixing png transparency was like squeezing blood from a stone indicates they're either over their head in ****ty code and should start over or they deserve to be ridiculed.
<10> suv4x4: well.. i that somehow feels like a car dealer telling me their cars now have wheels shipping by factory
<11> only thing that matters is this: they don't stagnate IE7 for 6 years *A G A I N *
<10> CSS2 is standard
<11> it's a "recommendation"
<11> and there's no requirement to support all or none of it
<13> hello all
<10> i don't care how much work is needed to get IE 6 to support it and then call it IE 7
<11> FF itself doesn't support all of it
<2> That's as good as it gets.
<13> help me with scrolling
<11> that's it
<11> hey
<11> inition of "still doesn't have it" :)
<11> [21:37] <11> TheSeer, IE7 have 'em
<10> suv4x4: so FF has to learn more too.. and they're working on it
<11> oops
<11> sorry for paste
<11> TheSeer, ah, so "FF has to learn more, and they are working on it" but "I don't care how much work it's been done in IE. CSS2 is a standard"
<11> be objective
<13> I created one MSN , and want leave the scrolling of <div> ever down
<11> forget MS policy crap about stagnating web standards adoption
<13> does someone kwon
<11> forget the "bosses" and look at the product
<11> the product is good, I like it
<11> and that's about it
<10> suv4x4: Currently from a standards point of view, safari is the best
<13> does someone know anything about it?
<11> TheSeer, "best" is not something that gives you an edge right now. It's about a balance of plenty of disciplines where you are at least "good".
<10> suv4x4: and if FF wants to keep their claim to be most standard compliant browser available, they got some work to do
<11> TheSeer, I'm afraid "be installed with 90% of the user base" is one of those.
<11> don't play like IE7 doesn't matter at all to web designers
<10> that's a restriction ;)
<10> not a standard
<11> the bottleneck is IE6, if that bottleneck is improved with Ie7, then all the web wins
<10> but i agree with you that IE 7 is a big step in the right direction - rendering wise at least
<10> i have no idea if the UI-Designers at M$ are on LSD or sometheing
<11> I hope we see XHTML in IE8 :P
<10> but the UI is totally broken
<11> thing is there's no practical usage of XHTMl right now
<11> it's just something we geeks want, for clarity of code and easier work on the server side
<11> TheSeer, the UI is odd.. but you should really check beta3.
<11> TheSeer, if you saw beta 1 the interface was not even half done
<11> neither were most of the CSS fixes and improvements
<10> i believe i had beta3
<11> when was this
<11> it's recent
<10> a couple of days a go.. 10 days or so?
Return to
#javascript
or
Go to some related
logs:
#perl
dsbeerf
block webex
#osdev
xubuntu Xorg install evdev
nptlonly LD_ASSUME_KERNEL
pydoc SyntaxError: invalid syntax
isp116 usb
#ubuntu
#linux
|
|