Empty element-properties differs in browsers

[mootools]

Empty element-properties differs in browsers

[cpojer]

Why is this a problem exactly?

[simonklb]

For example <form action></form> sends you to http://domain.com/null while <form action=""></form> sends you to the same page.

[jdalton]

nice find!

[subtleGradient]

Yup. Definitely an issue. Should be a pretty easy fix I would assume

[arian]

@subtleGradient how?

form.setAttribute('action', ''); // → <form action></form>

// or maybe?

var attr = document.createAttribute('action');
attr.nodeValue = '';
form.setAttributeNode(attr); // → <form action></form>

So how did you want to fix this?

[Inviz]

While we're there, does Slick.match(new Element('input[disabled]'), 'input[disabled]') still return false? Boolean (empty) attributes did not call setAttribute, and Slick doesnt read the property

[arian]

@Inviz seems to work fine: http://jsfiddle.net/YBcUs/1/

[Inviz]

@arian Even if your example does not create element with mootools, i checked it myself now, and it works with the edge mootools. I guess, i just need to update. Thanks anyways!

[ibolmo]

Updated the fiddle and looks like the attribute does have an empty string: http://jsfiddle.net/ubLw5/2/ for all browsers I've tested (FFx, IE, Safari, Chrome, ...)

So.. worksforme. You're probably seeing the attribute as <div attribute> because of the developer tools vs Firebug it'll show the empty string.

Re-open the issue, if you can provide a better test case.