While this article provides some practical OOP advise for the JS space, there is one comment that is suspect...
An issue with the onerror event is browser support. The biggest culprit has been within the Opera browser, so you should verify that all target browsers support this feature before integrating it into your application.
Any ideas how that could be done?
Discussion on:
View:
Show:
What it means is with the Opera browser you may not use the "onerror event" facility!
Speaking of JavaScript, this page's links to code listings use <nClick to open them in new windows. They also include href="#" in each link. Having the href in there causes the you to jump to the top of the article every time you click on a code listing. Taking the href attribute out will stop the jumping article, yet still allow users (with JavaScript) to access the code pop-up windows. (JavaScript links work without HREFs.)
It's a shame XHTML seems to be depricating the target attribute. That is/was a nice way to open new windows without having to resort to JavaScript.
It's a shame XHTML seems to be depricating the target attribute. That is/was a nice way to open new windows without having to resort to JavaScript.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
