Oh, "Aw, Snap!" does not necessarily mean that it is a malicious page. There are yet to be implemented stuff in the browser, or edge cases the engine (WebKit, V8, others) is not ready for, or not bound yet in Chrome specifically. I even think in most cases, it does not mean it is a malicious page. A malicious page would simply be blocked from doing the malicious things, rather than crashing the renderer.
☆PhistucK On Tue, Sep 8, 2009 at 19:25, John McCabe-Dansted <[email protected]> wrote: > > On Tue, Sep 8, 2009 at 11:55 PM, alexandrojv<[email protected]> wrote: > > If there was an option to open in another browser in the developer > > version, then every time it gets upgraded to a stable version, that > > code would have to be removed right? making it slower to release a > > Why? If the stable version never gives an "Aw, snap" the user will > never see the link. > > But if the user does get an "Aw, snap" on a stable version, then > AFAICT they are just as likely to find the link useful as in the > developer version. > > In any case you don't need to remove the code manually. It is trivial > to nest the code within something like an "#ifdef DEBUG". > > > stable version. If you do not like the fact that it is really buggy, > > then wait until a stable version comes out, in order to not have all > > these problems. Same goes to people using the developer version n > > windows, if they are using it as a Developer, then it is given that > > the product is not ready to be useful for everything, and may > > encounter problems, if you do not like, then do not use. > > When did I give you the idea I didn't like the Developer version of Chrome? > > I do like it. Thats why I only switch to another browser for pages it > can't render, such as ones that "Aw, Snap!" every time I try to load > them. > > One thing I just realized though: one reason a page could "Aw, Snap" > is if it was trying to break your system. If the page is intentionally > trying to exploit a hole in webkit then loading the page in a > sandbox-less browser may not be a good idea, particularly if that > browser is also webkit based like Safari. > > -- > John C. McCabe-Dansted > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
