Roll back to the original script injection policy

In fact that the double tab-getting policy can not ensure a tab is ready
to be injected ...
It seems no method to ensure that... I really hate asynchronized API
like chrome.
Get a new way to judge if a tab can be injected
v0.2.1 release

Still can not deal with those "connect error" page... sigh...