Google announced its plans of removing support for all Netscape Plugin Application Programming Interface (NPAPI) plug-ins from Chrome.
The Mountain View, Calif.-based company's decision to pull out NPAPI plug-ins by the end of 2014 in its web browser first came out in Sept. 2013.
Now, Google has extended the older plug-in's life once more and moved the termination to Sept. 2015.
Google has urged web developers to replace NPAPI with a much newer technology, Google's own Pepper Plugin Application Programming Interface (PPAPI) instead in order to improve Google Chrome's security features, The Register reports.
NPAPI has been the most used plug-in standard and is still being used by several web browsers including Firefox, Safari and Opera.
However, NPAPI has security flaws, as it has been hacked several times over the past years, prompting Google to develop its own plug-in. According to the tech giant, PPAPI has better security and an improved technology that prevents hackers from inserting malware into the system, PC World reports.
As of the moment, Opera and Google Chrome are the only two browsers that support the new plug in.
Google has already started to block NPAPI plug-ins automatically in Chrome, with the exception of a few plug-ins that users have to manually authorize in order for them to run on certain web sites.
Furthermore, the newer version of Chrome coming April next year will no longer support NPAPI at all, though "advanced users" can still override this using the "chrome://flags" feature.
However, on Sept. 15, users will no longer be able to use or override Chrome to use Netscape plugins simply because they won't run at all.
Although the move won't hurt majority of Chrome users because Adobe Flash comes with Chrome and does not require a separate plug-in, Google software engineer Justin Schuh is wary that the transition might be too abrupt.
Schuh expressed his senitments in his blog post, saying: "Although plug-in vendors are working hard to move to alternate technologies, a small number of users still rely on plug-ins that haven't completed the transition."
One user commented on Schuh's blog, arguing that other web developers might resort to using other web browsers like Firefox or Safari in order to view the web sites using older technology.
"What about Web pages, like most-if not all-banks in Brazil, that need Java?" the user wrote.