Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #22164
| Newsgroups | comp.lang.javascript |
|---|---|
| Date | 2013-11-23 14:30 -0800 |
| References | (1 earlier) <528deb24$0$6627$9b4e6d93@newsspool2.arcor-online.net> <d9447e08-8851-4a86-9199-1cf7aeaf1faf@googlegroups.com> <528fab87$0$6560$9b4e6d93@newsspool4.arcor-online.net> <968fdaae-78db-4459-9002-e84089099aad@googlegroups.com> <l6p0v7$1qr$1@dont-email.me> |
| Message-ID | <d17e583d-16c1-4348-86cd-2a648fcde264@googlegroups.com> (permalink) |
| Subject | Re: How to determine and to prevent javascript being hacked? |
| From | justaguy <lichunshen84@gmail.com> |
On Friday, November 22, 2013 8:38:47 PM UTC-5, Denis McMahon wrote: > On Fri, 22 Nov 2013 14:50:18 -0800, justaguy wrote: > > > > >> I rather guess, that there was some change in Chrome 31 that breaks > > >> your code. > > > > > Probably you're right. If so I might not be the only who has been > > > adversely affected. Do you have a link or email handy to report it to > > > Google Chrome team? > > > > First of all, you need to verify that your code is not the problem. > > > > Things that might cause your code to be the problem: > > > > 1) Browser specific code. If you're doing any form of browser or feature > > sniffing in your code, then you need to check that the result of that > > browser or feature sniffing is valid. > Not in this case. > > 2) Any errors in markup that might affect the dom that it presents to the > > javascript, especially if the javascript is then making assumptions about > > the dom element tree that are invalid due to an inconsistency between > > (for example) the declared dtd and the actual markup. > As said, Console indicates no errors. > > 3) A change in a non ratified "standard" such as html 5 that means that > > something that used to work doesn't any more. It's not HTML5 code. > > > I doubt that a chrome update would break previously working javascript > > unless that javascript and / or the dom it was manipulating were in some > > way flaky to begin with, and it's very unlikely that it would happen in a > > manner that only broke your system (I haven't noticed widespread > > complaints of broken chrome javascript, nothing seems to have been > > prominent on eg slashdot) unless the underlying issue was with your > > system. > > > > So this brings us back to: > > > > Please provide a url for a publicly accessible web page that contains the > > minimal html and javascript required to demonstrate the problem. Too bad. It's a simple web app that runs locally, hence, it's 127.0.0.1 URL. In the meantime, here's the essence. The main server side script/template includes two scripts, one for the left panel and the other for the right panel, and the main script has a javascript function, say, ed, that accepts a parameter of obj_id. So, loading of the main script, this js function becomes available. And the right panel list different objects, upon clicking it would trigger the js function (from the main script) and pass obj_id to it, so that it loads the content of the object into the left panel. It's really simple stuff. Also, if you guys are willing to try it a try I can provide a link to download it the small app (but it may take up quite a bit of your time... hence, my hesitation of such a request, but if you think it's not too much hassle please email me don at knowledgenotebook dot com) Thanks. > > > > -- > > Denis McMahon, denismfmcmahon@gmail.com
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How to determine and to prevent javascript being hacked? justaguy <lichunshen84@gmail.com> - 2013-11-20 17:56 -0800
Re: How to determine and to prevent javascript being hacked? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2013-11-20 18:42 -0800
Re: How to determine and to prevent javascript being hacked? Denis McMahon <denismfmcmahon@gmail.com> - 2013-11-21 02:57 +0000
Re: How to determine and to prevent javascript being hacked? John Harris <niam@jghnorth.org.uk.invalid> - 2013-11-21 10:50 +0000
Re: How to determine and to prevent javascript being hacked? Christoph Michael Becker <cmbecker69@arcor.de> - 2013-11-21 12:14 +0100
Re: How to determine and to prevent javascript being hacked? justaguy <lichunshen84@gmail.com> - 2013-11-21 20:25 -0800
Re: How to determine and to prevent javascript being hacked? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-22 15:18 +0100
Re: How to determine and to prevent javascript being hacked? Christoph Michael Becker <cmbecker69@arcor.de> - 2013-11-22 20:08 +0100
Re: How to determine and to prevent javascript being hacked? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-22 22:15 +0100
Re: How to determine and to prevent javascript being hacked? justaguy <lichunshen84@gmail.com> - 2013-11-22 14:50 -0800
Re: How to determine and to prevent javascript being hacked? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-11-23 00:16 +0100
Re: How to determine and to prevent javascript being hacked? Denis McMahon <denismfmcmahon@gmail.com> - 2013-11-23 01:38 +0000
Re: How to determine and to prevent javascript being hacked? justaguy <lichunshen84@gmail.com> - 2013-11-23 14:30 -0800
Re: How to determine and to prevent javascript being hacked? (Resolved) justaguy <lichunshen84@gmail.com> - 2013-11-28 11:22 -0800
csiph-web