Slashdot Mirror
Obfuscated HTML Contest?
ptaff asks: "We all know the nightmare of typical HTML developer: you get different results on different browsers/platforms (and we're talking HTML only, no CSS/scripts). To make matters worse, MSIE has this ability to render completely invalid HTML code (missing tags, invalid nesting, you get the point). Mozilla and its many cousins are trying hard to keep up with the inconsistencies of today's 'web-optimized-for-MSIE', but where is the limit?
As an exercise, can you build the most malformed HTML document that can be rendered in MSIE but will choke on others browsers?"
Well, i guess that's the difference between theoritical stuff (HTML standard) and the practical implementation (browsers)...
Maybe also the time required for a feature to become standard HTML plays a role, think people are gonna wait some months to have a feature, when the browser (broken or anticipating the new standard) can make it already ?
Isn't that after all also how the Internet itself works usually ? ie people do something in different ways, usually without any standard, or extending one, then some mix of everything becomes 'the' new standard (RFCs & so on) ?
Tsuyoikoto ha taisetsu da ne, dakedo namida mo hitsuyousa (Strength is an important thing, but tears too are necessary)
Why not make it render something different but valid in as many different browsers as possible?
My sympathy goes out to the judges of this contest.
That's totally obfuscated......
Old Style:
<APPLET code=XYZApp.class codebase=html/ align=baseline width=200 height=200> <PARAM NAME=model VALUE=models/HyaluronicAcid.xyz> No Java 2 SDK, Standard Edition v 1.3 support for APPLET!! </APPLET>New Style:
<EMBED type=application/x-java-applet;version=1.3 width=200 height=200 align=baseline code=XYZApp.class codebase=html/ model=models/HyaluronicAcid.xyz pluginspage=http://java.sun.com/products/plugin/1Step 2: save as a web page.
The result:
Of course, it breaks the rules because it uses style sheets, but who's counting...--- Jason Olshefsky
Karma: Poser (mostly affected by adding this line long after everyone else did)
Here is a classic.
It just looks dumb in Mozilla, but you can use IE to truly experience the horror.
I believe this was originally designed as an object lesson that HTML email and usenet posts are a bad idea.
There is no author identified, but I'd love to know who came up with this one.
I think it's better to find pages that use such code. example - the www.europcar.com .de .fr pages the use a javascript menu that does ONLY work in MSIE on windows. No MacIE, Mozilla(choose your platform), Opera 7 or other alternative browsers. You simply cannot see the menu or cannot use it - therefore you cannot navigate. There are more pages out there, writing this code on purpose is pointless, because it has already been written ;) Find those pages and complain, make a publicly available list of invalid non-working HTML pages. Write the webmasters about your problems. And of course show workarounds so that those "programmers" can see and change their mistakes.
A good reason for coding obfuscated (be it valid or invalid) HTML would be to create a repository of "real world" code for Browser developers out there to check if it works with their product. Then of course a "desired output" image should be attached to the code.
Creating a blacklist of corporate pages using invalid html is my favourite idea, but the mentioned repository would help a lot coders out there...I strongly disagree. HTML standards are standards for a very good reason -- it allows ALL producers of HTML clients AND HTML editors to aim for a common goal.
Following the "standards" as laid down by Internet Explorer will mean those writing HTML documents will continue in bad habits learnt during the so-called browser wars between Microsoft and Netscape. If you take 10 random sites and check the source code of the home page, I'd wager than none of them are using valid HTML 4, although the standard has been public for over four years!