Pages:
Author

Topic: The bitcoin wiki crash the browser (Read 2680 times)

donator
Activity: 1218
Merit: 1079
Gerald Davis
November 24, 2011, 09:48:02 PM
#35

IE9 isn't that bad.  With IE9 Microsoft browser teams seems to have actually cared about standards compliance, security, and scripting performance.  Sadly I have no idea why then didn't do that for the last decade (IE6... grrr).  Of course the OP isn't using IE9, if he was there likely would be no issue.

To OP:
If a webpage crashes a browser any browser for any reason that is a flaw in the browser.  Period.
The browser should be designed to ASSUME that any scripts and markup are inherently insecure.

Think about it this way.  IF something in wiki is accidentally crashing IE then that can be exploited by someone with malicious intent.
sr. member
Activity: 322
Merit: 251
FirstBits: 168Bc
November 24, 2011, 09:34:58 PM
#34
Deslok, out of curiosity, do you see shadows under the text in both of these renderings?

good catch netrin, well let me remove this utter rubish from every pc i come in contact then and replace it with something better like googles spyware

I cheated. It was only because IE opened a tunnel to your video driver.
sr. member
Activity: 462
Merit: 250
It's all about the game, and how you play it
November 24, 2011, 09:21:34 PM
#33
Deslok, out of curiosity, do you see shadows under the text in both of these renderings?

http://acid3.acidtests.org/
http://acid3.acidtests.org/reference.html


good catch netrin, well let me remove this utter rubish from every pc i come in contact then and replace it with something better like googles spyware

EDIT: full disclosure I have IE9 Chrome and FF on the system for checking cross compatibilty and because each one has it's own quirks.
sr. member
Activity: 322
Merit: 251
FirstBits: 168Bc
November 24, 2011, 09:13:37 PM
#32
Deslok, out of curiosity, do you see shadows under the text in both of these renderings?

http://acid3.acidtests.org/
http://acid3.acidtests.org/reference.html
sr. member
Activity: 462
Merit: 250
It's all about the game, and how you play it
November 24, 2011, 09:09:02 PM
#31
legendary
Activity: 882
Merit: 1000
November 24, 2011, 09:07:05 PM
#30
sr. member
Activity: 462
Merit: 250
It's all about the game, and how you play it
legendary
Activity: 1918
Merit: 1570
Bitcoin: An Idea Worth Spending
November 24, 2011, 08:55:26 PM
#28
I run BitcoinStats.org and here are the browser statistics for this month:



Take a word from the wise and upgrade away from IE!

That's interesting! Two people using BlackBerry. Barrack Obama and I wonder who's the other person.
legendary
Activity: 1036
Merit: 1002
November 24, 2011, 05:32:14 PM
#27
Man, seriously, I hope this isn't serious.

A browser should never crash. Websites are not trusted in general, and any crash is the browser's fault. Always. Even Silverlight, Java, JavaScript and Flash code should not be able to crash the browser even if this is the intention of the code running in them. Every exception is a security flaw, and any browser developer should be thankful to have it pointed out.

There is no reason to make any assumption on the conditions causing the crash. Since it's an error of Internet Explorer anyway, it might also be happening on a valid page.
hero member
Activity: 784
Merit: 1000
bitcoin hundred-aire
November 24, 2011, 04:21:53 PM
#26
We should launch a campaign for Microsoft Windows to support the IBM System/360.  Who's with me?
legendary
Activity: 1148
Merit: 1008
If you want to walk on water, get out of the boat
November 24, 2011, 03:50:16 PM
#25
Lol html 3.2

I have windows 3.1, why almost no software run on it??? This is madness! All broken programs!
hero member
Activity: 784
Merit: 1000
bitcoin hundred-aire
November 24, 2011, 03:05:24 PM
#24
About web development, it is in fact easy to do web pages that works in most browsers, including IE.
Validate your pages against HTML 3.2, no CSS and no JS, and your pages will work wonderfully in most browsers including old versions of IE like IE 4.0.
Grin
sr. member
Activity: 249
Merit: 251
November 24, 2011, 02:26:48 PM
#23
I run BitcoinStats.org and here are the browser statistics for this month:



Take a word from the wise and upgrade away from IE!
sr. member
Activity: 308
Merit: 250
November 24, 2011, 01:10:44 PM
#22
I agree with the robustness principle....
[snip]
....And what I say, is that if a software fail due to bad input, and the programmer forgot to implement error checking, is still the fault of whoever that provide the bad data, not the fault of the programmer or the software in question.

These two statements contradict each other. The purpose of the robustness principle, in terms of things that work on the internet, is that you pretend the network is a goddamn warzone. That means the blame lies on the receiving app that crashes, and it's programmer - because they should have expected users to do naughty, impolite things.

Quote
About web development, it is in fact easy to do web pages that works in most browsers, including IE.
Validate your pages against HTML 3.2, no CSS and no JS, and your pages will work wonderfully in most browsers including old versions of IE like IE 4.0.

And there it is, full-retard. Everyone should just go back to lynx and Mosaic because one douchebag, one of all seven people on the planet who claims to be a programmer yet is still retarded enough to use MSIE, doesn't like it when his browser crashes on some mal-formed markup. Smiley

Quote
The browser CRASH when visiting bitcoin wiki thats a unacceptable fault of the wiki! The wiki are sending something that causes the browser to CRASH, be it something in SSL handshake, be it something in HTML code, be it whatever. But please fix it!

For sites that care about their audience, it would be prudent for the webmaster to sort out what the issue is. That doesn't mean it's the webmaster's fault, make no mistake about it the blame lies entirely with your browser, but to maximize your audience you have to decide how much time is worth it supporting older versions of software. Bitcoin's target audience is, for the most part, IT security-conscious people, who normally wouldn't be caught dead using a version of MSIE that crashes on malformed input.
hero member
Activity: 518
Merit: 500
November 24, 2011, 12:20:24 PM
#21
I just tested it with IE8 (first time I used it lol), it works fine. The wiki also loads fine in Chrome, firefox, opera, opera mini, and android browser. I dont know what your problem is, but its your problem. Id hazard a guess its corrupted cache or some malware.
full member
Activity: 184
Merit: 100
Feel the coffee, be the coffee.
November 24, 2011, 11:58:06 AM
#20
what is Internet Explorer?

It's the Internets icon.
sr. member
Activity: 322
Merit: 251
FirstBits: 168Bc
November 24, 2011, 11:54:52 AM
#19
But what I also say, is that those inputting things into software should make sure to not input bad data.

That's the user's prerogative -- such as the author of a virus.

if a software fail due to bad input, and the programmer forgot to implement error checking, is still the fault of whoever that provide the bad data, not the fault of the programmer or the software in question.

No. No og nej! Inte ens lite rätt.

About web development, it is in fact easy to do web pages that works in most browsers, including IE.

No again. Developers have gotten used to it and command high salaries because of IE's 'creative' use of standards. But dude, you are turning a fun little thread into an exposition of your programming ineptitude. You are wrong.

Whoever is responsible for the wiki may give a shit and 'fix' YOUR BROWSER'S problem, but I wouldn't recommend that you hold your breath waiting, unless others also experience this problem. After two hundred views, have you seen one person say, "Oh, yeah I have the same problem with my "?

If you want to be helpful and support your lovable dinasaur of a browser, why don't you deconstruct the web site, eliminate pieces until you isolate the problem. Perhaps you'll find something interesting. Until then, I doubt it's worth anyone else's trouble.
full member
Activity: 129
Merit: 119
November 24, 2011, 11:46:19 AM
#18
I agree with the robustness principle, that programmers (like me) should implement error checking and handle all errors gracefully, which most, like me, do. But what I also say, is that those inputting things into software should make sure to not input bad data.

And what I say, is that if a software fail due to bad input, and the programmer forgot to implement error checking, is still the fault of whoever that provide the bad data, not the fault of the programmer or the software in question.


About web development, it is in fact easy to do web pages that works in most browsers, including IE.
Validate your pages against HTML 3.2, no CSS and no JS, and your pages will work wonderfully in most browsers including old versions of IE like IE 4.0.


bluefirecorp: 23/100 and a big "FAIL" and the text "You should not see this at all" behind FAIL.

-----

But now we are not talking about badly rendered pages, which can be acceptable in most cases.
What im talking about now is:
The browser CRASH when visiting bitcoin wiki thats a unacceptable fault of the wiki! The wiki are sending something that causes the browser to CRASH, be it something in SSL handshake, be it something in HTML code, be it whatever. But please fix it!
full member
Activity: 185
Merit: 100
November 24, 2011, 04:56:50 AM
#17
Rebuild your client with debug symbols and post the stack tra... Oh. Format and reinstall should do.

2009 called and wanted their platform back. They also kept going on about this bitcoin thing. Not falling for that one.
sr. member
Activity: 308
Merit: 250
November 24, 2011, 01:37:20 AM
#16
Okay, so you say, that if the wiki is sending bad data to the browser, that the browser does not expect, and the browser crash, its the browsers fault?

Yes.

The Bitcoin wiki could probably be edited to figure out why and stop it, but make no mistake: it's your browser's fault.

I am a programmer, so I can explain:

Lets say I write a custom bitcoin client that allows you to share 10 bitcoins to Y people evenly.
And a stubborn user/client are writing 0 as Y, the application take 10/0, it don't compute and the application crash.

Its not the application's fault that you/the client wrote 0 as Y. Its the fault of whoever that sent the erronous data. The application didnt expect you to write 0 people to share your 10 bitcoins between, it tries to compute it, OS returns "Cannot divide by 0", the app croaks and gets a runtime error -> crash.

Get a different job, you should not be programming if you don't understand the concept of "Be liberal in what you accept, and conservative in what you send." Particularly when dealing with something that operates on a public network, if a user can reliably trigger a divide by zero error, you are terrible at your job. Error checking, bitches.
Pages:
Jump to: