I’m working with a publishing system that uses custom tags. These are interpreted on the server. The problem is, that they cause big problems with Opera, when viewed locally (custom tags are not interpreted).
Opera is handling these tags differently from other browser. It looks like it is closing the tag at the end of the document (even if the tag contains closing slash). I’m just wondering, if such behavior is considered bug or feature.
Also, if you have any idea how to hack such code so that I can debug HTML+CSS for Opera locally (without interpreted custom tags), please let me know. Thank you.
Try the folowing code to see it in action (live example):
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Strict//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd'> <html xmlns='http://www.w3.org/1999/xhtml'> <head> <meta http-equiv='Content-Type' content='text/html; charset=utf-8' /> <title>Non-standard tag behavior in Opera</title> <style type='text/css' media='all'> div { background: yellow; padding: 1em; } nonstandardtag { border: 1px solid red; } </style> </head> <body> <div> <nonstandardtag>content of non-standard tag</nonstandardtag> main tag content </div> <div> <nonstandardtag /> main tag content </div> </body> </html>
This seems to be fixed in Opera 10. So I guess it was not a feature.