Weikiat.NET

Like many others I was very thrilled by the release of Google Chrome, and download it right away to test it out. The user experience was simply wonderful and clean, and I especially like the icongito mode that allows me to view porn shop for online gifts without letting my girlfriend knowing. I also like the fact that the title bar is done away with totally, replacing it with tabs, giving the web alot more screen area. Loading is very fast, and it supposedly will not crash the entire program even if one of the tabs freeze or crash, as each tab is actually a program by itself. However, one day of using it and I have already experienced various problems.

Despite promise, it freezes and all the tabs become unaccessible
I have around 5 tags open and I was visiting the Ultimate Ears website in one of the tabs, where the menu is made in flash. The entire site became frozen. Thinking that other tags will work, I click on the other tabs, and to my surprise, I couldn’t switch to them. ALL THE TABS froze. The same thing happened when I was watching a video on youtube. It seems that the shockwave plugin is not that stable yet, and when it freeze, the entire browser including all its tabs become frozen. This sets me to wonder, when more plugin support is implemented, will one single plugin freeze the entire browser?

Tab caption did not update itself
See this screenshot:

Even though I was at the Jaben Forum page, the caption of the Tab belongs to the tab on its right.

Source viewable on the “New Tab” page
I like the “New Tab” page very much, which lead me to do abit of investigation. When I try to right click and view source the page, it doesn’t work as the menu for viewing source is disabled. However, they forgot to disable the view source option from the “Developer” menu, and I was able to view the source of the “New Tab” page in its full glory:

Notice also the very interesting comment:

This page is optimized for perceived performance. Our enemies are the time
taken for the backend to generate our data, and the time taken to parse
and render the starting HTML/CSS content of the page. This page is
designed to let Chrome do both of those things in parallel.

1. Defines temporary content callback functions
2. Fires off requests for content (these can come back 20-150ms later)
3. Defines basic functions (handlers)
4. Renders a fast-parse hard-coded version of itself (this can take 20-50ms)
5. Defines the full content-rendering functions

If the requests for content come back before the content-rendering functions
are defined, the data is held until those functions are defined

The guys behind chrome has resorted to “dirty tricks” to make Chrome seem faster than it really is when loading the “New Tab” page which contains a hell lot of javascript.

View-Source: Exploit
If you are using Chrome right now, click on this link. You will notice that I can actually create links that when you click on it, will cause Chrome to launch its source viewer instead of the regular browser window. While this by itself is not a big deal (may even be the intention of the developers to work this way), there is a chance that this may eventually lead to bigger problems (maybe a bug in the source viewer), and you get infected with viruses or malwares.

That is all I have for now, but who knows more problems/bugs may surface. Granted, Chrome is only a Beta, but this beta, despite its many innovations, has lower quality than many other betas from Google.

Rate this post: (No Ratings Yet)

 Loading ...