×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

cancel ×
This is a preview of your comment

No Comment Title Entered

Anonymous Coward 1 minute ago

No Comment Entered

1000 comments

Phoenix (-1, Offtopic)

mojowantshappy (605815) | more than 10 years ago | (#5867844)

Well, Phoenix doesn't crash. Mozilla: 1, IE: -1!!!!

Re:Phoenix (5, Interesting)

thesadjester (87558) | more than 10 years ago | (#5867866)

Well, just to note, the Mac OS X version of IE did NOT crash. However, anyone using IE on mac when Camino, Mozilla, and Safari are well put together should have their head examined. Don't forget Opera too.

The bug seems to be Windows only....so the Mac coders at MS may be better coders...who knows.

Re:Phoenix (1, Interesting)

Anonymous Coward | more than 10 years ago | (#5867937)

so the Mac coders at MS may be better coders...who knows.

No, this is actually well known. IE for Mac got way ahead of IE for Windows, so the group coding the Mac version was dissolved a few years back to slow down development.

Bang! (-1, Offtopic)

Anonymous Coward | more than 10 years ago | (#5867847)

Aye Carumba, that sucked!

Damnit! (-1, Offtopic)

Anonymous Coward | more than 10 years ago | (#5867849)

Not only did THIS version of IE crash, but the others I had open did too!

Its times like this that I wish I had enabled my history. Maybe I'll stop loosing these great porno sites by doing that.

Re:Damnit! (2, Interesting)

antoy (665494) | more than 10 years ago | (#5867884)

Not only did THIS version of IE crash, but the others I had open did too!

It crashed only a single IE window on my pc. I run IE 6.0 on XP with all the updates, but maybe it has something to do with the 'Open folder windows in separate processes' option I have enabled.
It's not a serious vulnerability, but it sure is a very embarassing one :)

Inquirer says one line (4, Informative)

A nonymous Coward (7548) | more than 10 years ago | (#5867850)

Here is their story [theinquirer.net]

Re:Inquirer says one line (3, Informative)

MrP- (45616) | more than 10 years ago | (#5867919)

They're wrong, at least with my ver of IE, you have to have the FORM tag also or it just displays a text input box

Re:Inquirer says one line (1)

jtilak (596402) | more than 10 years ago | (#5867964)

um its html so technically the whole 234234213 tags could be on one line.

Microsoft...bleh. (-1, Flamebait)

aarondyck (415387) | more than 10 years ago | (#5867851)

Does this really surprise anyone? I mean, geez, you'd think that with a rep like MS that people would be expecting it! After all, I'm running WinME at home (No choice, it's on an IBM NetVista...my other systems run linux) and the thing crashes on almost an hourly basis.

How difficult would it be for Microsoft to simply hire a few people to do a GOOD job of testing their software? If MS used the open source concept, think of how quickly they would have their bugs found and/or fixed? Surely they should at least allow their beta testers to use the source, if for no other reason than to find simple bugs like this one and report them!

Re:Microsoft...bleh. (1)

Gortbusters.org (637314) | more than 10 years ago | (#5867903)

WinME? I feel for ya... I would endure a thousand browser crashes on 2000 or XP to avoid any pull-the-plug job on ME.

Re:Microsoft...bleh. (0)

Anonymous Coward | more than 10 years ago | (#5867942)

You must be new.. Welcome to Slashdot.. I hope you enjoy your stay. The restroom is in the back but please don't piss on the computer under the sink.

ME??? (0)

Anonymous Coward | more than 10 years ago | (#5867962)

Microsoft ME stands for Miserable Edition. What did you expect?

Wonder if that works deeper in a page (4, Funny)

ShieldW0lf (601553) | more than 10 years ago | (#5867852)

Could wreak havoc in html-enabled forums

Re:Wonder if that works deeper in a page (0)

Anonymous Coward | more than 10 years ago | (#5867893)

Probably some havok, but most forums only allow a few select tags.

Re:Wonder if that works deeper in a page (5, Informative)

zook (34771) | more than 10 years ago | (#5867921)

I doubt it. From my quick toying around, it seems that if the offending <input> tag appears inside of a <body> tag there's no such effect.

It's hard to divine the exact fatal combination, of course. :)

OS X IE Is Unaffected (5, Interesting)

WiseWeasel (92224) | more than 10 years ago | (#5867853)

It seems that IE 5.x on MacOS X is not affected by this. Not that it's such a big deal, I imagine any affected Windows versions of IE can be relaunched and people will just avoid going to places with such code. I fail to see the significance. Oh well, glad to see their Mac port is more stable in this regard.

So is IE 5.1.6 on OS 9.XX (3, Funny)

Rxke (644923) | more than 10 years ago | (#5867923)

Heh. Thank you so much for porting a better IE to the Mac, Billy...

Re:OS X IE Is Unaffected (1)

slamb (119285) | more than 10 years ago | (#5867966)

Not that it's such a big deal, I imagine any affected Windows versions of IE can be relaunched and people will just avoid going to places with such code. I fail to see the significance.

If this is just a denial of service attack, you're probably right. But it's often the case that when you can crash software, you can insert arbitrary code. (Buffer overflows, format string vulnerabilities...the most common causes of segfaults.) So what makes this really worrisome is not the inconvenience of restarting the browser but the fear that any website you go to can completely compromise your machine.

No IE to Crash (0, Offtopic)

Mooncaller (669824) | more than 10 years ago | (#5867855)

I think this is the only time in my life that I wished I had a MS box. BTW mostly MS free my entire life. The only exception was the shit that came on one of my systems I had built. It did not last long!

Poetic Justice (2, Funny)

Rudeboy777 (214749) | more than 10 years ago | (#5867856)

Hey if I insert htis here maybe it will crash out all Slashdot readers using IE. That'll learn 'em ;)

<html>
<form>
<input type crash>
</form>
</html>

And Opera is.... immune (0)

Anonymous Coward | more than 10 years ago | (#5867857)

Looks like this is one bug that Opera isn't affected by (it's got its own bugs to worry about)

mozilla crashes too (5, Informative)

Anonymous Coward | more than 10 years ago | (#5867858)

I use galeon most of the time and it crashes often too... Just put this in a document

<body onblur="javascript:self.focus()">

browse it, and galeon will crash (as of 1.3.3.20030419). Do the same in mozilla, close the browser window, and it will segfault (version 1.3).

Re:mozilla crashes too (0, Redundant)

magnum3065 (410727) | more than 10 years ago | (#5867957)

Hmm, no problem on Phoenix build 20030407. Tried it turning on and off the ability for JavaScript to raise and lower windows.

MSIE Crash'd (0)

JWSmythe (446288) | more than 10 years ago | (#5867859)

Hehe.. 4th post..

Confirmed, crashed MSIE 6.0 (6.0.2800.1106) on Win98 VMWare Window..

Of course, it doesn't touch Mozilla 1.2.1 on Linux.. Hmmm, time to upgrade to Mozilla 1.4a. How did I get so far behind on this machine?

Re:MSIE Crash'd (0, Redundant)

Penguin Follower (576525) | more than 10 years ago | (#5867873)

Mozilla 1.3 here... no crash either ;)

Re:MSIE Crash'd (0)

Anonymous Coward | more than 10 years ago | (#5867943)

Are you sure? I thought it would. You know, since they share so much code.

IE on OS X ok (1)

Zo0ok (209803) | more than 10 years ago | (#5867861)

IE 5.2.2 on Mac OS X (10.2) appears to be immune - no crashes here...

IE for Mac is a completely different IE from IE for Windows, right?

Re:IE on OS X ok (0)

Anonymous Coward | more than 10 years ago | (#5867911)

Yep. IE for the Mac is just another app. IE for Windows basically IS Windows.

Funny, considering the Windows versions of IE 5 and 6 are supposedly ports from the then-superior Mac version.

Re:IE on OS X ok (2, Informative)

Tokerat (150341) | more than 10 years ago | (#5867952)


Yes, I'd even go as far as to say they re-wrote the rendering engine from the ground up. PS MacOS 9 is safe too.

Bizarre (2, Interesting)

AnimeFreak (223792) | more than 10 years ago | (#5867862)

It doesn't affect Internet Explorer 5.1 for Mac OS X, and it is the latest version.

Not bizarre at all (1, Informative)

Anonymous Coward | more than 10 years ago | (#5867908)

It doesn't affect Internet Explorer 5.1 for Mac OS X, and it is the latest version.
That's not bizarre. Internet Explorer for Mac is built from an entirely different codebase than its IE counterpart, which means it lacks this bug (and likely others). They literally wrote IE for Mac from the ground up, they have(had?) an entire team devoted to the project. In some regards, IE 5.1 for Mac is better than IE 6.0 for Windows.

This has to be somthing put into ie on purpose... (2, Funny)

TheeAlien (518930) | more than 10 years ago | (#5867863)

This has to be somthing put into ie on purpose... merhaps the ie core team gets bored?

Lets look at the code shall we:

An html tag, a form tag, then this:

A closing form tag, and closing html tag.

!?

You _MUST_ be kidding me...

Re:This has to be somthing put into ie on purpose. (0)

Anonymous Coward | more than 10 years ago | (#5867955)

I think it crashes because input type is not specified.

You're shitting me. (0, Flamebait)

piranha(jpl) (229201) | more than 10 years ago | (#5867870)

Mozilla crashes on me. Opera crashes on me. Galeon crashes on me, in some cases (wired.com) consistently. links even crashed on me today (only when exitting).

Browsers crash. Software crashes. How is this news-worthy?

Enough mindless Microsoft-bashing troll articles, please!

Re:You're shitting me. (1)

MrP- (45616) | more than 10 years ago | (#5867883)

It's newsworthy because its a repeatable crash, it isnt just a fluke, post this one line of html on forums and crash everyone (who uses ie)

this could be real annoying. good thing i use opera

Re:You're shitting me. (1)

VanillaCoke420 (662576) | more than 10 years ago | (#5867907)

Actually I've used Opera and it crashed much more often than IE. It's not allowed to say such things, not even if it's true, but it is.

Re:You're shitting me. (1)

MrP- (45616) | more than 10 years ago | (#5867940)

I use Opera for everything now. If a page doesn't work in Opera, then I don't want to see it.

But there is a bug in Opera that annoys me, I seem to notice it started when I went back to dialup from DSL. If I load a bunch of pages, sometimes a page will get "stuck", it'll act like its loading, but will never stop. If I click "Stop", Opera GPFs. It is annoying but at least opera lets you restart where you were before it crashed.

Anyone know what causes that bug and if theres a fix? (using opera 6.05, if opera7 fixes it, i need a diff fix because I dont want to download opera7 yet =P)

Re:You're shitting me. (2, Insightful)

Big Toe (112240) | more than 10 years ago | (#5867912)

I have to disagree, Mozilla, Opera, and Galeon certainly crash, but not consistenly on poor parsing code. Parsing HTML really isn't that difficult, and the five line example isn't anything weird other than the unexpected "crash" keyword. Obviously this was built into IE as a test or something, and if not then their code must look like this...

if (inputType == crash)
{
weReallyRock(); //let's do what we do best!
}

The code should have had a huge #ifdef _DEBUG in front of it or something to prevent a crash.

Re:You're shitting me. (0)

Anonymous Coward | more than 10 years ago | (#5867954)

I've found lynx to be a very stable web browser. You should stop bitching and do some research on your own.

Is this really true? (1)

hkon (46756) | more than 10 years ago | (#5867872)

... or is it just planted by CmdrTaco to stress-test slashcode's troll-filtering capabilites

No bugs here (4, Funny)

Fastball (91927) | more than 10 years ago | (#5867874)

There no bugs here. The infidels are committing suicide on the logic gates of ActiveX. Lies! The stupid infidels...

input type _____ (3, Funny)

BoBathan (166436) | more than 10 years ago | (#5867876)

Seconds after reading this, I tried this out on my own, slightly modified.

input type giveBoBathan$1,000,000USD

Unfortunatly, Microsoft must have known of this potential exploit. :(

--Travis

That explains alot.. (1)

Lord Fren (189373) | more than 10 years ago | (#5867879)

I knew it! IE is just a bunch of smoke and mirrors that makes you think you are surfing the web. In actuality it is just a viewer for a big snapshot of the web, downloaded with each 'patch' from MS.

Now if they can just prove that Word, Excel, and Access are nothing more than a specialized viewer for .txt files..

Browser List (1)

aarondyck (415387) | more than 10 years ago | (#5867886)

Well, it would seem that there are a number of people who would like to post regarding this bug crashing different versions of various browsers. I guess I'll post mine here:
Crashed IE 5.50.4522.1800CO with SP1 on a WYSE Winterm running Win2K in a Citrix environment.

Does it have to be ``type crash?'' (2, Interesting)

mgrant (96571) | more than 10 years ago | (#5867887)

Does it have to be ``type crash?'' Why would ``crash'' be hardcoded into any library? It is just the lack of the ``='' that's doing it? I'd try it myself, but I don't own a copy if IE. Can anyone confirm?

Re:Does it have to be ``type crash?'' (3, Informative)

MrP- (45616) | more than 10 years ago | (#5867896)

Supposedly anything will do it

<input type mrp- 0wnz j00>

should do it also

Send an error report... (0)

Anonymous Coward | more than 10 years ago | (#5867888)

OK everyone, reboot to Windows and click that crash link until you get bored. Be sure to send Micro$uck an error report every time!

what happens? (3, Interesting)

scubacuda (411898) | more than 10 years ago | (#5867924)

Does anyone actually *know* what happens when you submit these errors to Microsoft?

Wait a minute.... (-1, Redundant)

GrouchoMarx (153170) | more than 10 years ago | (#5867889)

How exactly are Slashdot users supposed to crash their systems by viewing something with IE? Who the hell on Slashdot uses IE? Posers!

Re:Wait a minute.... (0)

Anonymous Coward | more than 10 years ago | (#5867904)

I bet it's > 50%. Not that any of these fanboys will admit it...

Re:Wait a minute.... (-1, Troll)

Anonymous Coward | more than 10 years ago | (#5867951)

im sorry i just come here for the cake and coffee, no need to call names. IE errors are part of the fun and exciting experience that is the internet, I just can't get enough of em.

MSIE 5.1.5 (4719) for MacOS 9 is NOT affected (1)

Tokerat (150341) | more than 10 years ago | (#5867890)


Just tried it. I get a plain TYPE=TEXT style input on the page, and View Source works correctly, too.

Ahh, for once it feels so good to be obsolete. :-D

Re:MSIE 5.1.5 (4719) for MacOS 9 is NOT affected (1, Insightful)

Tokerat (150341) | more than 10 years ago | (#5867916)


Well then I RTFA'd... bug in a DLL under XP. I wouldn't call that "almost any version of MSIE past 4", but hey, this is Shashdot. At least I know it's not a fundemental problem with IE's rendering engine and it's simply an accidental thing that happened to a new Windows version. Windows with a bug, who'd have thought? ;-)

I tried it.. (0)

Anonymous Coward | more than 10 years ago | (#5867894)

..and my Konquerror didn't crash. Somehow I'm not suprised.

A new way... (1, Offtopic)

Fuzzle (590327) | more than 10 years ago | (#5867897)

To enforce web standards. Just have the browser crash when the code isn't up to the standards.

bah (5, Interesting)

chadamir (665725) | more than 10 years ago | (#5867899)

people are up in arms over this because it's an ms blunder. It does nothing more than simply halt your browser. As many can testify, halted browsers happen with any of the many browser flavors available.

I heard someone suggest they hire better testers? How was anyone supposed to test for this. I know this is /. and trolling about MS is ok, but I mean come on, how could anyone see that coming.

The fact remains though that this crash isn't really that big of a deal. Sure it crashes IE, but it's not like most content webpages want their reader's browsers crashing when they reach the page. Who do we have to worry about? HTML enabled web boards? I have to worry about someone linking c:\con\con as an image everytime I click a link. You just go on with your life. If they are stupid enough to have html enabled then it's their problem, not MS's.

Re:bah (1)

Fuzzle (590327) | more than 10 years ago | (#5867917)

Yeah, I have to say I agree with you. This seems to be a problem that shouldn't be a huge issue, if the coders of the world are producing valid, standard code. It's not MS's job to ensure that this happens (regardless of their own spotty record of producing HTML). I have had Phoenix and Camino and Mozilla all crash at points on random pages, so I can't jump all over IE for this in the spirit of fairness. Sorry, it's just not that big of a deal.

Re:bah (5, Insightful)

gerardrj (207690) | more than 10 years ago | (#5867953)

People are up in arms over this because Bill Gates made it priority one in the company to make their software more secure and more reliable. This is just another blatent example of how they are failing in that mission. (This and the almost daily security updates).
Here we have a simple bug that should be a test case. The word "crash" is not required, just that the type directive has a null value since it is not followed by an equal sign.
The code would not hang the browser. The code would crash it just the same as it is again missing the equal sign. It's completely concievable that a developer that hand codes HTML would accidentally omit the character.

This is simple buffer underflow checking: "does the thing I just recieved have the minimum expected size/value?" and just like all the buffer overflow issues, they don't bother checking the untrusted input before sending it off for critical processing.

Re:bah (1)

shepd (155729) | more than 10 years ago | (#5867960)

>people are up in arms over this because it's an ms blunder. It does nothing more than simply halt your browser.

Well, I don't know about anyone else, but if you believe Microsoft, this bug doesn't crash your browser. It's crashes your OS.

That's REALLY bad when a single line of HTML code can crash your OS. I can think of no other OS that has this problem, where a simple text file can crash your system.

Simpler repro (1)

zook (34771) | more than 10 years ago | (#5867901)

Try the page:

<input type crash>

Looks like the bug has something to do with an <input> tag not inside a <form> tag. Curious.

Re:Simpler repro (1)

Galvatron (115029) | more than 10 years ago | (#5867922)

No, it's inside <form> tags, at least that's what I'm getting when I check the page source (and the example code given in the article also has <form> tags). Could it just be the fact that the input type is "crash?" That's such an absurd vunerability, it borders on parody. Anyone have a good explanation of what's going on?

why it crashes (5, Informative)

mejh (564536) | more than 10 years ago | (#5867902)

Just one line is really required:

According to a post on bugtraq:
IE tries to compare the type of the input field to "HIDDEN", to see if it
should be rendered. When there is no type string, a null-pointer is used.
mshtml.dll calls shlwapi.dll#158 @ 0x636f0037 with a pointer to a static
unicode string "HIDDEN" and a null-pointer.
shlwapi.dll#158 does a case-insensitive comparison of two unicode strings:
it reads from address 0x0 because of the null-pointer and thus causes an
exception.
This is not exploitable, other then a DoS because there is no memory mapped
@ 0x0 and even if you could load something there, you could only compare it
to "HIDDEN" which gets you nowhere.

Re:why it crashes (1)

mejh (564536) | more than 10 years ago | (#5867914)

Doh! That's lack of previewing for you...

Here's the one line required:
<input type hello>

Hah! I've got something that will crash IE also.. (5, Interesting)

[PF] Lurch (47956) | more than 10 years ago | (#5867906)

Ran into this while doing some website design, simplified the problem down to this. Note, the green background is just so you can see the cell a little better.



<html>
<head>
<style>
.header
{
position: fixed;
background-color: green;
}
</style>
</head>

<body>
<table border=1>
<tr>
<td class="header">sdf</td><td>sdfsdfsdf</td>
</tr>
</body>
</html>

You have to mouseover the table cells and you will get a gpf. Should work on IE 5.5 and 6.0.

note: there is a bogus semicolon after the /td when I preview this post... it shouldn't be there, but I can't get rid of it.

It's not a bug.... (1, Interesting)

yeoua (86835) | more than 10 years ago | (#5867909)

There were some NES games (and i think even some SNES games) in the past that had various codes and such (like the famous Konami code), and some games even had a reset code. This basically just reset the game by giving a specific key sequence (usually just hold every button down) and boom, the game resets with out you needing to walk up to the console.

Perhaps the ms ie engineers were just too lazy to hit the x button on ie so they developed this nifty little "feature" to make restarting ie that much easier. How?

Simple... make an htm doc on the desktop, put in these 5 lines, make it your homepage (obviously this prevents loading ie to begin with, but you can just load some other page first) and since home can be gotten to with some keypresses, this means it can be bound to the mouse buttons in some of the newer models.

And there you have it. Instant ie restarting from your mouse! You don't have to waste time clicking the x and then double clicking the ie icon. Genius!

(BTW, perhaps ms can be /.'d through too many users sending in bug reports?)

Yep... (0, Redundant)

scubacuda (411898) | more than 10 years ago | (#5867913)

Just tried it, and it DOES crash on the latest fully patched version of IE.

Anyone actually *look* at those lines of code? It's just:

<html>

<form>

<input type crash>

</form>

</html>

I'm surprised that the /. crowd hasn't yet embedded these 5 lines into the slash code!

Let the circlejerk begin! (-1, Flamebait)

Anonymous Coward | more than 10 years ago | (#5867915)

Ooooh, a BUG! Linux and Mozilla have NONE of those! Enjoy that false sense of superiority, children, because the numbers continue to mock you in return.

Opera (1)

toriver (11308) | more than 10 years ago | (#5867920)

does what any decent browser should do, and treat it as <input type=type crash=crash> and substitute the default type=text for the unknown type, and ignore the unknown attribute "crash".

Reproducible in 1 line. (1)

LightwaveNet (229843) | more than 10 years ago | (#5867925)

For the lazy you can reproduce the problem with just the one "input type something_invalid_here" line.

The HTML and FORM tags are just a little more proper :P

Re:Reproducible in 1 line. (1)

LightwaveNet (229843) | more than 10 years ago | (#5867965)

It should be stated tho that you would need to JUST use the 1 "input type crash" line putting anything else before it would just draw a blank textbox input field.

So if you wanted to imbed it in the beginning of a useable webpage (to non exploitable browsers) you'd want to include the crash line before your body tag.

Where is this IE you speak of? (5, Funny)

westyvw (653833) | more than 10 years ago | (#5867928)

I have looked all over my computer for this IE thingy you all speak of. I cant find it anywhere. I typed "whereis ie" in the console but nothing turned up. I typed find / -name IE and again nothing. I looked for a man page found none. I clicked on the gear icon thing and looked though the programs installed I dont have it. So I typed apt-get IE. No luck. Must be some obscure piece of software that I cant find. Guess I am better of WITHOUT IT!

Its now my new homepage!! (2, Funny)

stonezone (460503) | more than 10 years ago | (#5867929)

what fun, just set it to your homepage, then have it restart explorer automatically once you send in the error report. Hours of fun for the bored slashdotters....

Pretty simple bug really (3, Interesting)

JanusFury (452699) | more than 10 years ago | (#5867934)

If you skip over the assembly instruction that causes the exception in a debugger, everything works fine. So if anyone pulls this trick on you, just open the debugger and skip the instruction. :) That, or get a better browser.

So.... (4, Insightful)

The Bungi (221687) | more than 10 years ago | (#5867935)

It's not a vulnerability. It's a bug. It's a stupid bug, but a bug nonetheless. I used to consistently crash Mozilla on some Hotmail pages. But I didn't submit it to /. as a great story to hysterical giggles from the peanut gallery.

Slow news night, eh?

Re:So.... (0)

Anonymous Coward | more than 10 years ago | (#5867949)

Hmm, kinda weird, but I was trying to read the story and comments, and Phoenix crashed... no, really it did. I thought it was pretty ironic.

not only crash (-1, Redundant)

Anonymous Coward | more than 10 years ago | (#5867936)

In fact, the word "crash" doesn't really make any difference; you can put "calamari" or "IE sucks" in there and it will still go belly up.

Come on... (0)

KoolDude (614134) | more than 10 years ago | (#5867938)


...you can't blame IE for obeying the user's input. Just take a look at the source:

<html>
<form>
<input type crash>
</form>
</html>

you are basically asking it to crash at input and it obeys like a puppy. What's wrong with that ? Just becos Mozilla doesn't have this crash at input feature doesn't mean...

me rushin 4 HTML101 labs... byeee

Bill! Get it together, Bill! (2, Interesting)

fm6 (162816) | more than 10 years ago | (#5867945)

The ease with which Microsoft software manages to generate invalid pointers has bothered me for a long time. But for the web brower to crash in the face of such a god damned simple HTML error is just plain scary. Here's the entire web page:
<html>
<form>
<input type crash>
</form>
</html>
I mean, does anybody in Redmond do any QA work at all? Or are they all too busy writing white papers, fighting lawsuits, and babbling about "freedom to innovate"?

Not just IE any application that uses its stuff (0)

Anonymous Coward | more than 10 years ago | (#5867947)

Yahoo? MSN? How about embedding that code in the chat rooms :D or IM windows, and more.

Lots of applications DEPEND on IE COM Components to do web stuff. ALways a good reason to update IE even if you dont use it, other apps do.

Light-weight alright ;o) (2, Interesting)

maharg (182366) | more than 10 years ago | (#5867950)

The error is invalid page fault in shlwapi.dll

DLL Name: Shell Light-weight Utility
Library Description: Contains utility functions for handling paths, urls, strings, registry entries and color settings

Interesting that this dll can also 'handle' registry entries....

In fact, the 5 lines of html can be reduced down to one:

<input type>

..although placing this in the middle of a page doesn't always work:

<html>
<head>
<title>foo</title>
</head>
<body>
<h1>foo</h1>
<input type>
</body>
</html>

type seems to be the only attribute that has the desired effect

hot air! (0)

MavEtJu (241979) | more than 10 years ago | (#5867967)

Lots of hot air. Where is the time when, if you found a problem, just mailed the author saying "if you do this and this it will break." instead of writing a hundred line advisory?
Load More Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Sign up for Slashdot Newsletters
Create a Slashdot Account

Loading...