PageRenderTime 44ms CodeModel.GetById 21ms RepoModel.GetById 0ms app.codeStats 0ms

/error-log.markdown

https://bitbucket.org/mollydotcom/opera-dragonfly-manual
Markdown | 49 lines | 29 code | 20 blank | 0 comment | 0 complexity | 8b4c7be063d9ccf57cb3b3874d1423e6 MD5 | raw file
  1. <style>
  2. ins {
  3. font-size: 11px;
  4. text-decoration: none;
  5. }
  6. .comment { background-color: yellow; }
  7. .bug { background-color: pink; }
  8. </style>
  9. ## Error Log
  10. The Error Log is the place to track down syntax and parser errors that may cause an application or web page to behave unexpectedly.
  11. Click on the Errors icon in the application toolbar to access the Error Log. The number of errors for the current debugging context is conveniently displayed in the icon itself.
  12. ###Search
  13. To search through all errors on a page, use the Search control on the Error Log toolbar.
  14. ###Tabs
  15. By default, the All tab will be selected, showing every type of error for the current page. Errors can be filtered by choosing a more specific tab such as the JavaScript tab.
  16. To add or remove tabs from the Error Log, select the appropriate checkbox from the Error Log tab of the Opera Dragonfly Preferences.
  17. Error messages can be opened one by one by clicking on them, or globally by clicking the Expand All icon in the Error Log toolbar.
  18. ###Error Types
  19. There are three error types displayed in the Error Log:
  20. * error: An example would be a syntax error or an uncaught exception
  21. * information: Provides info, such as for an unknown property or value
  22. * warning: An example is when console.warning() is used
  23. For CSS and JavaScript errors, clicking on the URL of the file in the expanded view will open the style sheet or script as a new tab in the Resource inspector.
  24. You can direct messages to the Error Log programmatically by using the `console.log()`, `console.info()`, `console.warn()`, `console.error()`, and `console.assert()` methods. For more information, see the Console chapter.
  25. <ins>screenshot here--but depends on <span class="bug">DFL-1711</span> and <span class="bug">DFL-1710</span></ins>
  26. ###CSS Filters
  27. Custom CSS filters can be defined in the Error Log settings tab to remove certain types of errors from the All and CSS tabs of the Error Log. Comma separated filters will be matched and ignored. For example, a filter such as `_padding` will force the Error log to ignore the IE6 underscore hack for padding properties.
  28. ###Clearing the Error Log
  29. The Error Log is cleared by clicking the Trashcan icon in the toolbar.