Why does HTML5 continue to dominate browsers?

Why does HTML5 continue to dominate browsers? HTML5 triggered a wave of software development before it was officially adopted in June 20 14, which reduced the dependence on proprietary Internet technologies such as AdobeFlash and MicrosoftSilverlight. In 20 15, YouTube, Firefox, Google and Facebook blocked Flash one after another and used HTML instead, gradually devouring the share of Flash and reaching the top. Set off a wave of software development and reduce dependence on proprietary and rich Internet technologies (such as AdobeFlash and MicrosoftSilverlight). HTML5 video elements (used to embed videos in documents) are a major change to support the rich Internet. HTML5 is also designed to support changing web pages and browsing documents from one place to a place where distributed applications are built. However, in the process of standardization of HTML5, video codec has always been an unsolved problem, and there is no suitable royalty-free codec at present. H.265 patent problems are full of thorns. Although Google's VP9 codec is good, other companies participating in Web standards are reluctant to get technical support from competitors. Nevertheless, HTML5 has become the main way to build open multimedia network applications. Jeff Yafei, CEO of the World Wide Web Consortium, said: "HTML5 will soon become the only HTML version that people use in their browsers. Incremental improvement of HTML5. The HTML5 specification is updated regularly, and sometimes there are some minor functional improvements and bug fixes. For example, last year's 5. 1 version modified the 2D elements of canvas to further clean up HTML 5；; Version 5.2 adds menu elements to indicate commands that can be activated. In addition, the security policy of Web content is introduced, which provides developers with a way to control resource access and even supports the use of e-mail addresses with non-Latin characters. Although we have listed so many new features, version 5.2 is considered as a slightly modified version. However, W3C wants to update the core HTML specification more frequently, preferably once a year, instead of updating the main version every ten to fifteen years, which can't keep up with the development of the Web. Who will be the successor of HTML5? So will there be HTML6? Jia Fei said that online payment may promote such a comprehensive revision in order to provide a unified way for online payment. If you call it HTML6, then HTML6 is likely to appear. Although online shopping is nothing new, due to the increase of complexity and the advantages of using mobile Web, the amount of online shopping on PC has decreased, and HTML may need more different methods. The World Wide Web Consortium has also set up a group to discuss these contents. The World Wide Web Consortium also focuses on Web components, using a framework to identify reusable website components and service personnel, making it easier for browsers to run multiple functions and have offline functions. Maybe they won't name the next version of HTML6. The open network leads HTML5 to a new field. Jaffe said that although the goal of HTML5 is to open network platforms, there are more and more platforms, so the World Wide Web Consortium is conducting research on security, performance and streaming media. The work related to streaming media involves the Encrypted Media Extensions (EME) standard, which extends the HTMLMediaElement (in HTML5) to provide an application programming interface for controlling the playback of encrypted content and connecting to a digital rights management system. EME provides a standard way to display video through a browser. There was no intercommunication before. Jaffe said that it is a huge and significant progress from Netscape's controversial NPAPI plug-in technology to standardized video playback mode. Tim Bole-Lee, director of W3C, said that the inventor of the Internet affirmed EME and said that it provided a safe way to watch movies online, but others still opposed it. Berners-Lee pointed out that DRM still has problems in terms of developers and laws. For network security, W3C (World Wide Web Consortium) has made the following three efforts: The network authentication framework currently being developed aims to support security through multi-factor authentication. Jeffa said we really need to stay away from passwords. The WebCryptoAPI completed earlier this year provides a JavaScriptAPI for basic encryption operations in network applications. The project has also been completed to prevent information from being shared from one application to another, thus protecting users' privacy.