1. ????? ??? 20?30??? ??.

2.??? 20? ?? ???.

3.????? ?? 8? ??? ???.

4.??? TV? ??? ????.

5.??? ???? ????.

6.??? ??? ????.

7.’?? ??’? ???.

8.??, ???? ???.

9.????? ??? ?? ?? ???? ??? ??.

10.??? ?? ?? ??? ? 2?3?? ?? ? ????.

??:http://cafe.daum.net/lifebean

It seems like you have used an invalid character for apostrophes in your code (or the WordPress commenting system mangled it). Either way, this code below works fine:

DOMAssistant.DOMReady(addEvents);
function addEvents() {
if($(”formContact”)) {
alert(’q');
}
$(”formContact”).addEvent(”submit”, validateContact);
}
function validateContact(){
alert(”Validate”);
}

No, sorry. This is due to the default behavior and implementation of events in web browsers. Please see my comment above for an alternate solution.

Thanks for sharing! It’s always good to have different versions for possible alternate scenarios.

@ Robert,
First of all, thanks for sharing DOMAssistant.
I changed getElementsByAttribute a little bit because I needed partial matching of the attribute values. Here’s the code, in case you find it interesting/useful:

getElementsByAttribute : function (attr, attrVal, tag, partialMatch){
var elms = ((!tag || tag == “*”) && this.all)? this.all : this.getElementsByTagName(tag || “*”);
partialMatch = (partialMatch ? “.*” : “”);
var returnElms = [];
if(typeof attrVal != “undefined”){
var attrVal = new RegExp((partialMatch || “(^|\\s)”) + attrVal + (partialMatch || “(\\s|$)”));
}
…
// the rest of the method is not changed.
}

Needless to say, this could give you way too many matches, but I thought it wouldn’t hurt to share.

Wow, interesting scenario…
This is just off the top of my head, but i think it will work:

var desiredElms = document.getElementsByClassName(”test”);
var elm;
var elmParent;
for(var i=0; i<desiredElms.length; i++){
elm = desiredElms[i];
elmParent = elm.parentNode;
var wrapper = $(elm).create(”div”, {
className : “testwrapper”
}, false, elm.cloneNode(true));
elmParent.insertBefore(wrapper, elm);
elmParent.removeChild(elm);
};

The idea is:

It finds the elements
Clones them
Creates the wrapper
Appends the clone to the new wrapper
Inserts the new wrapper into the DOM before the original element
Deletes the original element

I’ve been looking for something specific. Namly a script that would allow me to wrap HTML tags around a number of HTML tags that are of a specific class. For instance, I might have this:

[img class=”test” /]
[img class=”test” /]

[div class=”testwrapper”]And would like to, via javascript, end up with this:

[div class=”testwrapper”][img class=”test” /][/div]
[div class=”testwrapper”][img class=”test” /][/div]

I see several libraries that allow one to insert HTML inside a tag (ala innerHTML) but finding ones that allow you to wrap HTML outside a tag seem harder to find. It was recommended to be to check out both jQuery and DomAssistant. I did find how to do it with jQuery, but it does involve using jQuery, which is a tad large for this one thing. Can DomAssistant to do this? Looking through the examples, I saw lots of examples of inner-HTML-esque options, but nothing that actually wrapped HTML.

I’m glad to hear that!

That works beautifully, I’m using to add classes to form element containers when required fields aren’t filled out - it works like a charm.

Thanks for your help.
Colin

Interesting. I’ve only tried it briefly, but this should do the trick:


getParentByTagName : function(tag){
var elm = this;
var pattern = new RegExp(tag, "i");
while(elm.parentNode && !pattern.test(elm.nodeName) && !/body/i.test(elm.nodeName)){
elm = elm.parentNode;
}
return elm;
}


Something I use fairly often is the jQuery parents function to find a specific container above a given element. I’ve tried to roll my own, but i’m no expert when it comes to JS. Here’s what i’ve come up with so far, which I’ve added to the DOMAssistant.js file:

getParentByTagName : function(tag) {
var elm = this;
while (elm) {
if (elm.tagName.toLowerCase() == tag.toLowerCase()) {
return elm;
}
elm = elm.parentNode;
}
}

I’m sure one of you folks will be able to point out where my glaring errors are rather quickly!

Thank you!

I’m not too big of fan of using CSS selectors in script to access elements; to me, it feels awkward. But one can never tell what the future holds…

please i’d really appreciated it

and your AJAX previewer is totally awesome!!!!

Sorry, not as of now. If you’re interested in delving deeper, you might want to take a look at Mark Wubben’s Event Cache.