![]() ![]() Wilson Page over at Mozilla has an excellent overview of some of the technical issues that we have discussed recently in meetings with other vendors. The right questions and difficult problems are being raised and discussed by browser vendors and other participants. We are happy with the direction that current discussions around specific web components technical issues are trending. In our standards involvement, we also see it as a great way to foster community experimentation and help guide the direction of future standards. We’re excited about the potential for the technology to dramatically simplify large-scale web development while simultaneously reinforcing good declarative patterns that are already familiar in HTML. Many people ask us: “What does Microsoft think about Web Components?” Web components have a lot to offer the community. What does Microsoft think about Web Components? We’re excited about the potential of these technologies, and today we’re excited to announce that we’re beginning development on the HTML Template element, one of the core Web Components technologies and the #3 UserVoice request from developers. In this post, we’ll answer a couple of recurring questions we get about the technology, including our implementation roadmap and how we currently think about its priority in regards to other related platform work. Yesterday, we shared our thoughts on the promise of Web Components. ![]() ![]() To read more about our viewpoint and background on web components, please see part one, “ Bringing componentization to the web: An overview of Web Components.“ Editor’s note: This is part two of a two-part series on Web Components by Microsoft Edge engineers Travis Leithead and Arron Eicholz. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |