scottydog0

Yes! I can now edit fields in Firefox! Thanks!

While that is one way to get around the problem in the short term, it is not a solution.

Hello? Can I get a response to this?

Sure, I’d like to see the new version.

Thanks,
Scott

I’m not sure about “watermarks”. I’d need to see an example. I think keeping things tightly integrated is probably best. A separate interface could get confusing. What problem have you had w/ spaces so far? Have you tried using a space character placeholder?

Thanks,
Scott

I looked at your code. Maybe something like this:

$tokens = array( 'mask' => 'mask:', 'alternate_mask' => 'aMask:', 're_do' => 'reDo:', 're_undo' => 'reUndo:');

if (!empty( $tag['attr']) {
	foreach($tokens as $var => $token){
		if (strpos($token, $tag['attr'])) {
			${$var} = preg_replace("/.*?$token([^\s]+)\s.*/",'$1',$tag['attr']);
		} else {
			${$var} = '';
		};
	};
} else if (!empty($tag['options'])) {
	foreach ($tag['options'] as $value) {
		foreach($tokens as $var => $token){
			if (strpos($token, $value)) {
				${$var} = preg_replace("/.*?$token([^\s]+)\s.*/",'$1',$value);
			} else if(!isset(${$var})) {
				${$var} = '';
			};
		};
	};
};

I haven’t tested it yet, so my regex may be off, but this should properly parse out the options in either situation.

Sure, here’s what I’m using:

[phone* Phone mask:999-999-9999]

-Scott