Target option still missing from latest version

James -

Will this extension ever support the TARGET attribute?

From the looks of it, it doesn't seem like it's even being considered.

Please advise.

Thanks

PS - Yes, I know you can manually code the target attribute in, but you will lose all the manual changes once you update the menu through the WebAssist interface.

  James -  

ummm, my name is Jason, not James.

My brother is named James, but i dont think he will be much help to you ;)

  Will this extension ever support the TARGET attribute?

From the looks of it, it doesn't seem like it's even being considered.

Please advise.

Thanks

PS - Yes, I know you can manually code the target attribute in, but you will lose all the manual changes once you update the menu through the WebAssist interface.  

there are no immediate plans to include this in Menu Writer. if it is to be included, I would not expect to see it till Version 3.

a feature request was put through a while back, I will put through another one now.

you can also post your request to the wishlist forum.

This doesn't apply to the target attribute, but here's a workaround to combat losing any custom css styling after reentering the wizard - if anyone is interested.

I've been designating custom styles (like CSS3 styles or <li> class styles) to a separate stylesheet, placed below the menu.css that MenuWriter generates. You can re-enter the wizard to make edits, and unless you make major menu structure changes, the custom style sheet should still target your menu's tags. If anything goes wonky its usually not hard to pinpoint the problem selector and fix accordingly.

Sort of adapted this method from Dan Cederholm's book, &#8216;Handcrafted CSS&#8217; in which he adds an enrichment css file to the bottom of the style sheet stack to utilize the cascade effect and server up CSS3 styles to modern browsers. The beauty is in the fact that the MW wizard won't touch this file and alter it on you.