Hi John,
Further to Tim's comments I think the JavaScript menu is a weak point. A
better solution would be to have the 'Members Name' and 'Type of Furniture'
options built in to the content in separate select boxes and then use
JavaScript to show one of them and hide the other.
The advantage to
Tony Crockford wrote:
the framed pages have *no* doctype - what would make them strict?
and why, when they are part of a frameset would you try and validate
them against a strict DTD?
Why do the framed pages not have a doctype Tony? I can't see anywhere in the article you reference where
Richard Lake wrote: Help needed
See http://www.pricklypair.co.nz/rocket1/products.php?dept=cakes
All works well as long as the first product's height pushes it past the
sidebar. Where this doesn't occur the second product doesn't start until
after the sidebar. I've experienced this problem
and some are not then you don't have a choice - each external link needs a separate hook.
As said before though, triple check before you decide that a new window is the best option. Ian Pouncey wrote: As a general rule, if you are opening a new window or loading anything other than another HTML
Ian Pouncey wrote: This is the same idea as the PPK code, as there is still a hook required - the wrapper element.Thierry Koblentz wrote: No, it is not required. Using a DIV as a hook is not for making the script work but to make sure
we do not parse *every single link* in the document (i.e
One last email at the risk of boring the rest of the list! I think it's
just down to you and I now Thierry.
Thierry Koblentz wrote:
Ian,
I'm not saying my approach is better or cleaner I'm just saying that it does
not work the way you describe it.
AFAIK, PPK is "tagging" the external
