Timeline for Is the Web browser status bar always trustable?
Current License: CC BY-SA 3.0
31 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Sep 10, 2013 at 16:19 | history | bounty ended | CommunityBot | ||
| S Sep 10, 2013 at 16:19 | history | notice removed | CommunityBot | ||
| Sep 6, 2013 at 18:11 | comment | added | Terrel Shumway | jsfiddle.net/48KFV/2/show works without javascript. The "statusbar" is fake, and looks fake to the paranoid, but I imagine the average person who just wants to get his work done may not notice the difference. | |
| Sep 4, 2013 at 5:21 | answer | added | Dheeraj Thedijje | timeline score: 1 | |
| Sep 3, 2013 at 11:02 | answer | added | DarkMantis | timeline score: 1 | |
| Sep 3, 2013 at 5:44 | answer | added | curiousguy | timeline score: 11 | |
| Sep 2, 2013 at 15:51 | comment | added | newuser999 | I disabled JavaScript and went to this site: jsfiddle.net/48KFV/2/show it still worked :) so disabling JavaScript can't help (used Firefox). | |
| Sep 2, 2013 at 15:32 | vote | accept | newuser999 | ||
| Sep 2, 2013 at 15:27 | comment | added | demize | To answer the second part of your question, judging from all the answers posted so far, yes, disabling JavaScript would work. But it's not exactly a great solution, as you'd have to disable Javascript completely and break most websites these days. | |
| S Sep 2, 2013 at 14:53 | history | bounty started | newuser999 | ||
| S Sep 2, 2013 at 14:53 | history | notice added | newuser999 | Improve details | |
| Sep 2, 2013 at 14:52 | history | edited | newuser999 | CC BY-SA 3.0 |
added 45 characters in body
|
| Sep 2, 2013 at 13:51 | comment | added | newuser999 | Should I open another questions regarding: "Does disabling JavaScript with ex.: NoScript solves this problem 100%?" or Can I put a bounty on this Question regarding it? | |
| Sep 2, 2013 at 13:51 | history | edited | newuser999 | CC BY-SA 3.0 |
deleted 14 characters in body
|
| Sep 1, 2013 at 15:47 | vote | accept | newuser999 | ||
| Sep 1, 2013 at 15:56 | |||||
| Sep 1, 2013 at 3:15 | comment | added | Abhi Beckert | You can't trust them. There have been a million different cases over the years where browsers have been tricked into doing something other than what the user expected. If you can't absolutely trust the page you have visited, just close the browser window. Don't touch anything. Providing links to past situations isn't very useful, because new techniques are invented regularly. Seriously, just don't trust it. | |
| S Sep 1, 2013 at 2:46 | history | suggested | Simon | CC BY-SA 3.0 |
Grammar, capitalization.
|
| Sep 1, 2013 at 2:46 | answer | added | makerofthings7 | timeline score: 2 | |
| Sep 1, 2013 at 2:25 | review | Suggested edits | |||
| S Sep 1, 2013 at 2:46 | |||||
| Sep 1, 2013 at 2:17 | history | edited | newuser999 | CC BY-SA 3.0 |
added 88 characters in body
|
| Aug 30, 2013 at 11:37 | comment | added | Adi | Example: jsfiddle.net/qn4jF/embedded/result | |
| Aug 30, 2013 at 11:37 | answer | added | Alvin Wong | timeline score: 26 | |
| Aug 30, 2013 at 11:15 | answer | added | BenLanc | timeline score: 19 | |
| Aug 30, 2013 at 9:53 | comment | added | Mat |
<a href="foo.html" onclick="window.location='bar.html';return false;">Go to Foo</a>
|
|
| Aug 30, 2013 at 9:15 | history | tweeted | twitter.com/#!/StackSecurity/status/373373374086795264 | ||
| Aug 30, 2013 at 9:12 | history | edited | newuser999 | CC BY-SA 3.0 |
added 11 characters in body
|
| Aug 30, 2013 at 9:00 | history | edited | newuser999 | CC BY-SA 3.0 |
added 63 characters in body
|
| Aug 30, 2013 at 8:35 | answer | added | bobince | timeline score: 62 | |
| Aug 30, 2013 at 7:19 | answer | added | user10211 | timeline score: 6 | |
| Aug 30, 2013 at 6:53 | review | First posts | |||
| Aug 30, 2013 at 7:16 | |||||
| Aug 30, 2013 at 6:36 | history | asked | newuser999 | CC BY-SA 3.0 |