Geoff Welsh wrote:
Often times, when a link on a page doesn't work, I notice (by looking in the status bar) it's not HTML <href...> it's "javascript:void()" So, some designer is using Javascript for no good reason, I understand that...
Sometimes they are using JavaScript for a very good reason. Just because the href has a value of "javascript: void ()" does not mean that the link is dysfunctional; it may well be that there is also an "onclick" attribute and it is that which performs the actual transfer to another page. For example : <a href="javascript: void ()" onclick="window.location=NextPage ()">link text</a> The href could not be hard-coded because the value of "NextPage ()" is known only at run-time. Such code works perfectly in Seamonkey (as in any other standards- compliant browser with JavaScript enabled); I develop and test /all/ of my work in Seamonkey, which I could not possibly do if Seamonkey could not handle such links. In the case you cite, there is no explicit "onclick" or similar : <a href="javascript: void()" class="prodIng1">View Ingredients</a> but it is still possible that the designer/programmer had intended to add one via DOM-walking -- in general, if a page is going to /require/ JavaScript, then it is better to use minimal HTML markup and add the required functionality using a DOM-walking technique to add additional attributes to the element in the DOM : such additional attributes will never be visible via "View source". The page you cite is also dysfunctional in IE9, which reports errors; Seamonkey's error console reports several tens of errors in the CSS, and the W3C HTML validator reports 38 HTML errors. It is hardly surprising, therefore, that it does not work as Colgate would wish in Seamonkey. Philip Taylor _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
