Front-end technology HTML5 future development direction

As the main player in the open web platform, the HTML 5 standard is undergoing gradual, improved, and even fundamental changes. HTML 5 was officially released in October 2014, but as early as many years ago, the technology has started to rise and develop in the field of software development. It has reduced people's reliance on proprietary, rich Internet technologies, such as Adobeflash and Microsoft Silverlight. HTML 5 video elements, as embedded video files, become an important turning point in supporting rich Internet. When the internet evolves from a single browser to a distributed application, HTML 5 technology and design powerfully support this evolutionary process.

Tracking the evolution of HTML 5, although still a common web search, tax-free version of the video codec, but also made some progress, h.265 also made a patent. In addition to the Google VP9 codec, other participating companies are reluctant to provide technical support to their competitors by the consistent web standard. Nonetheless, HTML 5 has built its own set of open, multimedia rich Internet applications. Jeffjaffe, chief executive of the World Wide Web Consortium with technical jurisdiction, said: "HTML 5 is quickly accepted as an HTML version that is used today in browsers and Web sites." "

incremental and improved HTML 5

The HTML 5 specification is updated periodically. You can see general minor feature improvements and bug fixes, such as last year's 5.1 release, modify canvas 2D elements, and further clean up HTML 5. Next comes the 5.2 release, which has some new features, such as a menu element that represents a set of commands that can be activated. The 5.2 release also focuses on Web content security policies, providing developers with access control methods for their resources. The upgraded version can also handle e-mail addresses that are not Latin. However, version 5.2 is still a minor upgrade.

Over the last decade, 15 years ago, the HTML version basically didn't keep up with the speed of web development, but today, the world of the Internet requires more frequent updates of the HTML core specification. However, these major upgrades do not lead to an overall upgrade, such as from HTML 5 to HTML 6 or even HTML 7.

what will be the successor of HTML 5?

Do we never see HTML 6 as I said earlier? Jeffe that online payments could lead to a series of changes that provide a consistent way to pay online. "If we go straight to the definition of HTML 6, online payment may be the case." While online shopping is nothing new, the mobile Web advantage adds to the reason why people abandon their shopping carts. Because of its complexity, different methods may be required to design new HTML. There is a working group dedicated to discussing this issue. It is also dedicated to Web components that define reusable site components and service personnel in a framework that makes it easier to run multiple functions within a browser, including offline functionality. Perhaps they will actually witness the advent of HTML 6.

Open Web page to incorporate HTML 5 into new areas

While HTML 5 is already targeting an open web platform, the platform itself is becoming richer and more than just the HTML stage. So the consortium is studying security, performance, and streaming media. Streaming media related work involves the encryption Media extension (EME) standard, which extends the html5.1 version of the media elements provided by the API to control the playback of encrypted content and to connect to a digital rights management system. The EME provides a set of standards for playing video through a browser. Previously, Jaffe said, there was no interaction. The advent of this set of standards is a huge improvement on the non-standardization of video playback today. This is often the Netscape controversial NPAPI plugin technology.

Timberner-lee, a director and Web founder of the company, endorsed the EME proposal of February this year, suggesting it provides a relatively safe way to watch online movies, but some oppose the proposal. Bernerslee notes the existence of DRM for developers, future generations, and legal issues.

Finally, let's take a look at the main projects that are under way for Web security:

1. network authentication Framework. The current state is in progress, and our goal is to support security through multi-factor authentication. "We really want to get rid of the code," Jaffe said.

2. Network Encryption API. Was completed earlier this year. You can implement JAVASCRIPTAPI basic cryptographic operations in a network application.

3. The best Practices for network development security are now complete. The purpose of this practice is to prevent the information in the application from being shared from one user to another, thus violating user privacy.

Source: Technology House

Front-end technology HTML5 future development direction