DOCSLIB.ORG

Using Property-Based Testing, Weighted Grammar-Based Generators and a Consensus Oracle to Test Browser Rendering Engines and To

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

USING PROPERTY-BASED TESTING, WEIGHTED GRAMMAR-BASED GENERATORS AND A CONSENSUS ORACLE TO TEST BROWSER RENDERING ENGINES AND TO REPRODUCE MINIMIZED VERSIONS OF EXISTING TEST CASES by JOEL DAVID MARTIN Presented to the Faculty of the Graduate School of The University of Texas at Arlington in Partial Fulfillment of the Requirements for the Degree of DOCTOR OF PHILOSOPHY THE UNIVERSITY OF TEXAS AT ARLINGTON December 2019 Supervising Committee: Farhad Kamangar, Supervising Professor David Levine, Supervising Professor Manfred Huber Gergley Zaruba Copyright by Joel David Martin 2019 The copyright of Chapter2 was transferred to the IEEE as part of publication in COMPSAC 2018 (\Property-Based Testing of Browser Rendering Engines with a Consensus Oracle") [1]. Please refer to the IEEE for information about licensing the content from Chapter2. Chapter3 is a manuscript that is intended for separated publication. All copyrights on Chapter3 are currently reserved to Joel Martin. The remainder of this work, excluding Chapter2 and Chapter3, is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. ACKNOWLEDGMENTS Thank you to the members of my Supervising Committee for their support and guidance. In particular, I would like to thank David Levine who spent many long hours with me discussing the research and helping with the numerous large and small details that were necessary to complete my thesis. Many thanks to my employer, Viasat, for the financial investment toward my education. Thank you to my supervisors at Viasat, Ingolf Krueger and Markus Kaltenbach, for their support and encouragement throughout my graduate education. I would like to apologize for the harm done to numerous figurative trees during the completion of this research. As a thank you to the reader(s) of this dissertation, I offer you a gift. Contact me with proof that you have read this work and I will send you a prize (limited quantities available). Thank you to Aaron Brooks for being a sounding board for many of the ideas that were explored in this research. Thank you to Matt Oquist, Ingolf Krueger, and Rebecca Martin for their detailed reviews and the valuable feedback that they provided. DEDICATION I dedicate this work to my brilliant and beautiful wife, Dr. Rebecca Martin. She worked hard to ensure that I would be successful in this endeavor. Let it be noted, for posterity, that she received her doctorate 8.5 years prior to me receiving mine. ABSTRACT Using Property-Based Testing, Weighted Grammar-Based Generators, and a Consensus Oracle to Test Browser Rendering Engines and to Reproduce Minimized Versions of Existing Test Cases Joel David Martin, Ph.D. The University of Texas at Arlington, 2019 Supervising Professors: Farhad Kamangar and David Levine Verifying that a web browser rendering engine correctly renders all valid web pages is challenging due to the size of the input space (valid web pages), the difficulty of determining correct rendering for any given web page (the test oracle problem), and the degree to which normal variation in browser rendering behavior can obscure other differences (fonts, bor- ders, input controls, etc). These challenges lead to manual human involvement during the testing process. We propose a new Property-Based Testing (PBT) approach that addresses these challenges in order to enable automated web browser render testing. Our approach is composed of the following modules: a system for translating HyperText Markup Lan- guage (HTML) and Cascading Style Sheets (CSS) specification data into grammar-based generators; a grammar weighting system that controls test case generation along with mul- tiple methods for automatically adjusting those weights; and a consensus oracle of multiple rendering engines to identify failing test cases. Our approach increases the practicality of real-world testing. It has the ability to re- produce existing test cases from external sources, is able to shrink test cases to assist with root-cause analysis, and supports generic test specifications. We validated and characterized the effectiveness of our approach with a constrained markup grammar developed for this purpose. Applying our approach while testing Mozilla Firefox and Google Chrome revealed 1695 unique test cases that yield rendering differences. Testing of Mozilla's new Servo web vi browser revealed multiple bugs including eleven crashes and resource leaks. We reported these issues to Mozilla developers and are working together to develop and verify solutions. vii Contents 1 Introduction1 1.1 Motivation and Objectives............................1 1.1.1 Browser Testing Challenges.......................1 1.1.2 Solving the Limitations of PBT with Instacheck............3 1.1.3 Use case: a New Web Browser Engine.................4 1.1.4 Objectives.................................5 1.2 Modules and Document Structure........................7 1.2.1 Modules..................................7 1.2.2 Document Structure...........................9 2 \Property-Based Testing of Browser Rendering Engines with a Consensus Oracle" (COMPSAC, July 2018) 11 2.1 Abstract...................................... 12 2.2 Introduction.................................... 12 2.3 Property-Based Testing (PBT)......................... 13 2.3.1 Test Generation using Clojure test.check................ 14 2.3.2 Test Shrinking............................... 15 2.4 Test System Architecture............................. 16 2.5 Grammar-based Input Generators........................ 18 2.5.1 HTML5 Grammar............................ 18 vi 2.5.2 CSS3 Grammar.............................. 20 2.6 Generator Tuning................................. 21 2.7 Consensus..................................... 22 2.7.1 Challenges................................. 22 2.7.2 Calculating Consensus.......................... 23 2.8 Results....................................... 24 2.9 Related Work................................... 27 2.10 Conclusion and Future Work........................... 27 3 \Instacheck: An Automated Property-based Testing Model to Increase Coverage and Enable Directed Testing using Weighted Grammars" 28 3.1 Abstract...................................... 29 3.2 Introduction.................................... 29 3.3 Property-based Testing (PBT).......................... 30 3.3.1 PBT Input Properties.......................... 31 3.3.2 PBT Test Shrinking........................... 32 3.3.3 Limitations of PBT............................ 33 3.4 Instacheck..................................... 34 3.4.1 Instacheck Grammars........................... 34 3.4.2 Grammar Weights............................ 36 3.4.3 Grammar Paths, and Treks....................... 38 3.4.4 Grammar Weight Reduction and Propagation............. 41 3.4.5 Reproducing and Shrinking Existing Test Cases............ 44 3.5 Results....................................... 45 3.5.1 Test Grammars.............................. 45 3.5.2 Controlling Coverage........................... 48 3.5.3 Increasing Coverage with Weight Reduction.............. 52 3.5.4 Shrinking................................. 54 vii 3.5.5 Reproducing Existing Test Cases.................... 55 3.5.6 Case-study: Detecting Browser Rendering Differences......... 59 3.6 Related Work................................... 61 3.7 Conclusion..................................... 62 3.7.1 Future Work................................ 62 4 Instacheck In Greater Depth 63 4.1 Clojure test.check PBT Example........................ 63 4.2 Clojure test.check Generators.......................... 67 4.3 Extended Backus-Naur form (EBNF) Generators and Weight Tuning.... 71 4.3.1 MG4 and MG8 Grammars........................ 76 4.4 Translating EBNF Grammars to Clojure Generators.............. 82 4.5 Instacheck Command Line and Library Usage................. 85 4.5.1 Generate Random Test Cases...................... 86 4.5.2 Test and Shrink.............................. 89 4.5.3 Reproduce and Shrink an existing Test Case.............. 94 4.5.4 Translate EBNF Specification into Clojure Generators........ 98 5 HTML and CSS Grammars (html5-css3-ebnf) 101 5.1 Backus-Naur form (BNF) and EBNF Background............... 101 5.2 Hypertext Markup Language version 5 (HTML5) Grammar.......... 103 5.2.1 HTML5 Background........................... 103 5.2.2 Parsing and Translating HTML5.................... 103 5.3 Cascading Style Sheet Level 3 (CSS3) Grammar................ 107 5.3.1 CSS3 Background............................. 107 5.3.2 The CSS3 Value Definition Syntax (VDS) Grammar.......... 110 5.3.3 Parsing and Translating CSS3...................... 113 5.4 Parsing Challenges................................ 117 viii 5.5 html5-css3-ebnf Usage.............................. 119 5.5.1 Generate EBNF Parsing Grammars................... 119 5.5.2 Parse Web Pages............................. 121 6 Bartender: Browser Automated Render TestiNg DrivER 125 6.1 The State of Browser Render Testing...................... 125 6.2 Bartender System Architecture......................... 128 6.2.1 Optimizing and Translating EBNF Grammars to Clojure Generators 130 6.2.2 Bartender Testing Process........................ 133 6.3 Consensus..................................... 135 6.3.1 Consensus Algorithms.......................... 136 6.3.2 Consensus Challenges and Solutions................... 139 6.3.3 Consensus Example............................ 145 6.4 WebDriver Browser Automation......................... 157 6.5 Monitoring and Reporting Applications..................... 159 6.5.1 Runtime Monitoring Application...................
Recommended publications
  • Browser Wars

    Browser Wars

    Uppsala universitet Inst. för informationsvetenskap Browser Wars Kampen om webbläsarmarknaden Andreas Högström, Emil Pettersson Kurs: Examensarbete Nivå: C Termin: VT-10 Datum: 2010-06-07 Handledare: Anneli Edman "Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of read- ing a document written on another computer, another word processor, or another network" - Sir Timothy John Berners-Lee, grundare av World Wide Web Consortium, Technology Review juli 1996 Innehållsförteckning Abstract ...................................................................................................................................... 1 Sammanfattning ......................................................................................................................... 2 1 Inledning .................................................................................................................................. 3 1.1 Bakgrund .............................................................................................................................. 3 1.2 Syfte ..................................................................................................................................... 3 1.3 Frågeställningar .................................................................................................................... 3 1.4 Avgränsningar .....................................................................................................................
  • Using Replicated Execution for a More Secure and Reliable Web Browser

    Using Replicated Execution for a More Secure and Reliable Web Browser

    Using Replicated Execution for a More Secure and Reliable Web Browser Hui Xue Nathan Dautenhahn Samuel T. King University of Illinois at Urbana Champaign huixue2, dautenh1, kingst @uiuc.edu { } Abstract Unfortunately, hackers actively exploit these vulnerabil- ities as indicated in reports from the University of Wash- Modern web browsers are complex. They provide a ington [46], Microsoft [61], and Google [49, 48]. high-performance and rich computational environment Both industry and academia have improved the se- for web-based applications, but they are prone to nu- curity and reliability of web browsers. Current com- merous types of security vulnerabilities that attackers modity browsers make large strides towards improving actively exploit. However, because major browser plat- the security and reliability of plugins by using sandbox- forms differ in their implementations they rarely exhibit ing techniques to isolate plugins from the rest of the the same vulnerabilities. browser [62, 33]. However, these browsers still scatter In this paper we present Cocktail, a system that uses security logic throughout millions of lines of code, leav- three different off-the-shelf web browsers in parallel to ing these systems susceptible to browser-based attacks. provide replicated execution for withstanding browser- Current research efforts, like Tahoma [32], the OP web based attacks and improving browser reliability. Cock- browser [36], the Gazelle web browser [59], and the Illi- tail mirrors inputs to each replica and votes on browser nois Browser Operating System [58] all propose build- states and outputs to detect potential attacks, while con- ing new web browsers to improve security. Although tinuing to run.
  • Internet Explorer 9 Features

    Internet Explorer 9 Features

    m National Institute of Information Technologies NIIT White Paper On “What is New in Internet Explorer 9” Submitted by: Md. Yusuf Hasan Student ID: S093022200027 Year: 1st Quarter: 2nd Program: M.M.S Date - 08 June 2010 Dhaka - Bangladesh Internet Explorer History Abstract: In the early 90s—the dawn of history as far as the World Wide Web is concerned—relatively few users were communicating across this Internet Explorer 9 (abbreviated as IE9) is the upcoming global network. They used an assortment of shareware and other version of the Internet Explorer web browser from software for Microsoft Windows operating system. In 1995, Microsoft Microsoft. It is currently in development, but developer hosted an Internet Strategy Day and announced its commitment to adding Internet capabilities to all its products. In fulfillment of that previews have been released. announcement, Microsoft Internet Explorer arrived as both a graphical Web browser and the name for a set of technologies. IE9 will have complete or nearly complete support for all 1995: Internet Explorer 1.0: In July 1995, Microsoft released the CSS 3 selectors, border-radius CSS 3 property, faster Windows 95 operating system, which included built-in support for JavaScript and embedded ICC v2 or v4 color profiles dial-up networking and TCP/IP (Transmission Control support via Windows Color System. IE9 will feature Protocol/Internet Protocol), key technologies for connecting to the hardware accelerated graphics rendering using Direct2D, Internet. In response to the growing public interest in the Internet, Microsoft created an add-on to the operating system called Internet hardware accelerated text rendering using Direct Write, Explorer 1.0.
  • University of Camerino Computer Science (LM 18) Browser Evolution

    University of Camerino Computer Science (LM 18) Browser Evolution

    University of Camerino Computer Science (LM 18) Browser Evolution Project of Web 2.0 Autor: Luciani Alex Prof: Vaccari Carlo License This material is distributed under the Creative Commons "Attribution - NonCommercial - Share Alike - 3.0", available at http://creativecommons.org/licenses/by-nc-sa/3.0/ . What is a Browser? A browser is a software application, it retrieves and shows elements of the web. Story Prehistory 1963: Ted Nelson: Hypertext. 1987: John Bottoms: Silversmith, SGML. 1989: Tim Berners-Lee: WWW, HTML, HTTP, W3C. 1994: Mosaic → Netscape. Story Mosaic screenshot Story First Browser War (1996 - 2004) Story Second Browser War (2004 - ...) Story January 2010, Firefox passed IE Story The Actual Situation (2011) Data from statcounter.com Browser Market Share % Browser Version Market Share % Apr 11 Apr 11 IE 44.52 IE 8.0 30.24 Firefox 29.67 Firefox 3.6 18.91 Chrome 18.29 Chrome 10.0 16.03 Safari 5.04 IE 7.0 7.82 Opera 1.91 Firefox 4.0 7.59 IE 6.0 4.14 Safari 5.0 3.83 IE 9.0 2.32 Firefox 3.5 1.99 Tech Evolution Web Browser Engines They paint the web pages interpreting the client-side scripts. Layout Engine License Main Browser Gecko Free and OpenSource Firefox Presto Proprietary Opera Trident Proprietary Internet Explorer WebKit Free (GNU LGPL) Safari, Chrome Tech Evolution Protocols Connection: HTTP. Security: SSL, HTTPS Languages and Client Side HTML, HTML5 Javascript, Ajax CSS XML, SVG WebGL Tech Evolution Ajax Example Tech Evolution Google Body Browser uses WebGL Tech Evolution GUI Evolution Google 10 Firefox 3.6 Firefox 4 Tech Evolution GUI Evolution Explorer 8 Explorer 9 Tech Evolution Browser Testing Acid Test: testing client side script languages.
  • Webkit and Blink: Open Development Powering the HTML5 Revolution

    Webkit and Blink: Open Development Powering the HTML5 Revolution

    WebKit and Blink: Open Development Powering the HTML5 Revolution Juan J. Sánchez LinuxCon 2013, New Orleans Myself, Igalia and WebKit Co-founder, member of the WebKit/Blink/Browsers team Igalia is an open source consultancy founded in 2001 Igalia is Top 5 contributor to upstream WebKit/Blink Working with many industry actors: tablets, phones, smart tv, set-top boxes, IVI and home automation. WebKit and Blink Juan J. Sánchez Outline The WebKit technology: goals, features, architecture, code structure, ports, webkit2, ongoing work The WebKit community: contributors, committers, reviewers, tools, events How to contribute to WebKit: bugfixing, features, new ports Blink: history, motivations for the fork, differences, status and impact in the WebKit community WebKit and Blink Juan J. Sánchez WebKit: The technology WebKit and Blink Juan J. Sánchez The WebKit project Web rendering engine (HTML, JavaScript, CSS...) The engine is the product Started as a fork of KHTML and KJS in 2001 Open Source since 2005 Among other things, it’s useful for: Web browsers Using web technologies for UI development WebKit and Blink Juan J. Sánchez Goals of the project Web Content Engine: HTML, CSS, JavaScript, DOM Open Source: BSD-style and LGPL licenses Compatibility: regression testing Standards Compliance Stability Performance Security Portability: desktop, mobile, embedded... Usability Hackability WebKit and Blink Juan J. Sánchez Goals of the project NON-goals: “It’s an engine, not a browser” “It’s an engineering project not a science project” “It’s not a bundle of maximally general and reusable code” “It’s not the solution to every problem” http://www.webkit.org/projects/goals.html WebKit and Blink Juan J.
  • HTML5 and Java Technologies

    HTML5 and Java Technologies

    HTML5 and Java Technologies Peter Doschkinow Senior Java Architect The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. Agenda . Motivation . HTML5 Overview – Related Java Technologies . Thin Server Architecture . Demo Motivation . Need for clarification Gartner’s 2012 Emerging Technologies Hype Cycle – What is behind the hype . Architectural consequences of new trends . What does the Java platform offer to meet the new challenges . Building of common understanding Web Technology History . 1991 HTML . 1995 JavaScript @ Netscape . 1994 HTML2 . 1996 ECMAScript 1.0, 1.1 . 1996 CSS1 . 1997 ECMAScript 1.2 . 1997 HTML4 . 1998 ECMAScript 1.3 . 1998 CSS2 . 2000 ECMAScript 3 . 2000 XHTML1 . 2010 ECMAScript 5 . 2002 Tableless Web Design . Next: ECMAScript 6 Harmony . 2005 AJAX . 2009 HTML5: as of Dec 2012 W3C CR HTML5 Features W3C / Web Hypertext Application Technology Working Group(WHATWG) . Markup – Semantic markup replacing common usages of generic <span>, <div> . <nav>, <footer>,<audio>, <video>, ... API – Canvas 2D (for immidate mode 2D drawing),Timed media playback – Offline Web Applications, Local Srorage and Filesystem, Web Storage – Geolocation, Web Storage, IndexedDB – File API, Drag-and-Drop, Browser History – ... HTML5 Features Offloaded to other specs, originally part of HTML5 . WebSocket API, Server-Sent Events(SSE), Web Messaging, Web Workers, Web Storage (Web Apps WG ) .
  • X41 D-SEC Gmbh Dennewartstr

    X41 D-SEC Gmbh Dennewartstr

    Browser Security White PAPER Final PAPER 2017-09-19 Markus VERVIER, Michele Orrù, Berend-Jan WEVER, Eric Sesterhenn X41 D-SEC GmbH Dennewartstr. 25-27 D-52068 Aachen Amtsgericht Aachen: HRB19989 Browser Security White PAPER Revision History Revision Date Change Editor 1 2017-04-18 Initial Document E. Sesterhenn 2 2017-04-28 Phase 1 M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 3 2017-05-19 Phase 2 M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 4 2017-05-25 Phase 3 M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 5 2017-06-05 First DrAFT M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 6 2017-06-26 Second DrAFT M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 7 2017-07-24 Final DrAFT M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 8 2017-08-25 Final PAPER M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER 9 2017-09-19 Public Release M. VERVIER, M. Orrù, E. Sesterhenn, B.-J. WEVER X41 D-SEC GmbH PAGE 1 OF 196 Contents 1 ExECUTIVE Summary 7 2 Methodology 10 3 Introduction 12 3.1 Google Chrome . 13 3.2 Microsoft Edge . 14 3.3 Microsoft Internet Explorer (IE) . 16 4 Attack Surface 18 4.1 Supported Standards . 18 4.1.1 WEB TECHNOLOGIES . 18 5 Organizational Security Aspects 21 5.1 Bug Bounties . 21 5.1.1 Google Chrome . 21 5.1.2 Microsoft Edge . 22 5.1.3 Internet Explorer . 22 5.2 Exploit Pricing . 22 5.2.1 ZERODIUM . 23 5.2.2 Pwn2Own .
  • Moving to the Client – Javafx and HTML5 Stephen Chin (@Steveonjava) Kevin Nilson (@Javaclimber)

    Moving to the Client – Javafx and HTML5 Stephen Chin (@Steveonjava) Kevin Nilson (@Javaclimber)

    Moving to the Client – JavaFX and HTML5 Stephen Chin (@steveonjava) Kevin Nilson (@javaclimber) 1 The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 2 Meet the Presenters Stephen Chin Kevin Nilson @steveonjava @javaclimber just.me VP of Engineering Family Man Author Web 2.0 Fundamentals § User Groups Motorcyclist § Silicon Valley Web JUG § Silicon Valley JS Meetup § Silicon Valley Google Developer Group 3 History of the Web • 1991 HTML • 1994 HTML 2 • 1996 CSS 1 + JavaScript • 1997 HTML 4 • 1998 CSS 2 • 2000 XHTML 1 • 2002 Tableless Web Design • 2005 AJAX • 2009 HTML 5 4 What is HTML5 • Web Hypertext Application Technology Working Group (WHATWG) • HTML5 ! = HTML + CSS + JavaScript • HTML5 = Next Generation Features for Modern Web Development • Offline Storage, Web SQL Database, IndexedDB, Application Cache, Web Workers, WebSocket, Notifications, Native Drag & Drop, File System, GeoLocation, Speech Input, Form Types, Audio, Video, Canvas, SVG 5 HTML5 Rounded Corners • http://slides.html5rocks.com/#rounded-corners HTML5 No HTML5 6 HTML5 Canvas 3D (WebGL) • http://oos.moxiecode.com/js_webgl/fish/index.html 7 Prefixes • -webkit-text-fill-color: black; • -webkit-column-count:
  • Web Standards Web Standards: Mastering HTML5, CSS3, and XML Gives You a Deep Understand- Ing of How Web Standards Can Be Applied to Improve Your Website

    Web Standards Web Standards: Mastering HTML5, CSS3, and XML Gives You a Deep Understand- Ing of How Web Standards Can Be Applied to Improve Your Website

    BOOKS FOR PROFESSIONALS BY PROFESSIONALS® Sikos, Ph.D. RELATED Web Standards Web Standards: Mastering HTML5, CSS3, and XML gives you a deep understand- ing of how web standards can be applied to improve your website. You will also find solutions to some of the most common website problems. You will learn how to create fully standards-compliant websites and provide search engine-optimized Web documents with faster download times, accurate rendering, lower development costs, and easy maintenance. Web Standards: Mastering HTML5, CSS3, and XML describes how you can make the most of web standards, through technology discussions as well as practical sam- ple code. As a web developer, you’ll have seen problems with inconsistent appearance and behavior of the same site in different browsers. Web standards can and should be used to completely eliminate these problems. With Web Standards, you’ll learn how to: • Hand code valid markup, styles, and news feeds • Provide meaningful semantics and machine-readable metadata • Restrict markup to semantics and provide reliable layout • Achieve full standards compliance Web standardization is not a sacrifice! By using this book, we can create and maintain a better, well-formed Web for everyone. CSS3, and XML CSS3, Mastering HTML5, US $49.99 Shelve in Web Development/General User level: Intermediate–Advanced SOURCE CODE ONLINE www.apress.com For your convenience Apress has placed some of the front matter material after the index. Please use the Bookmarks and Contents at a Glance links to access them. Download from Wow! eBook <www.wowebook.com> Contents at a Glance About the Author................................................................................................
  • Webkit and Blink: Bridging the Gap Between the Kernel and the HTML5 Revolution

    Webkit and Blink: Bridging the Gap Between the Kernel and the HTML5 Revolution

    WebKit and Blink: Bridging the Gap Between the Kernel and the HTML5 Revolution Juan J. Sánchez LinuxCon Japan 2014, Tokyo Myself, Igalia and WebKit Co-founder, member of the WebKit/Blink/Browsers team Igalia is an open source consultancy founded in 2001 Igalia is Top 5 contributor to upstream WebKit/Blink Working with many industry actors: tablets, phones, smart tv, set-top boxes, IVI and home automation. WebKit and Blink Juan J. Sánchez Outline 1 Why this all matters 2 2004-2013: WebKit, a historical perspective 2.1. The technology: goals, features, architecture, ports, webkit2, code, licenses 2.2. The community: kinds of contributors and contributions, tools, events 3 April 2013. The creation of Blink: history, motivations for the fork, differences and impact in the WebKit community 4 2013-2014: Current status of both projects, future perspectives and conclusions WebKit and Blink Juan J. Sánchez PART 1: Why this all matters WebKit and Blink Juan J. Sánchez Why this all matters Long time trying to use Web technologies to replace native totally or partially Challenge enabled by new HTML5 features and improved performance Open Source is key for innovation in the field Mozilla focusing on the browser WebKit and now Blink are key projects for those building platforms and/or browsers WebKit and Blink Juan J. Sánchez PART 2: 2004-2013 WebKit, a historical perspective WebKit and Blink Juan J. Sánchez PART 2.1 WebKit: the technology WebKit and Blink Juan J. Sánchez The WebKit project Web rendering engine (HTML, JavaScript, CSS...) The engine is the product Started as a fork of KHTML and KJS in 2001 Open Source since 2005 Among other things, it’s useful for: Web browsers Using web technologies for UI development WebKit and Blink Juan J.
  • Building a Browser for Automotive: Alternatives, Challenges and Recommendations

    Building a Browser for Automotive: Alternatives, Challenges and Recommendations

    Building a Browser for Automotive: Alternatives, Challenges and Recommendations Juan J. Sánchez Automotive Linux Summit 2015, Tokyo Myself, Igalia and Webkit/Chromium Co-founder of Igalia Open source consultancy founded in 2001 Igalia is Top 5 contributor to upstream WebKit/Chromium Working with many industry actors: automotive, tablets, phones, smart tv, set-top boxes, IVI and home automation Building a Browser for Automotive Juan J. Sánchez Outline 1 A browser for automotive: requirements and alternatives 2 WebKit and Chromium, a historical perspective 3 Selecting between WebKit and Chromium based alternatives Building a Browser for Automotive Juan J. Sánchez PART 1 A browser for automotive: requirements and alternatives Building a Browser for Automotive Juan J. Sánchez Requirements Different User Experiences UI modifications (flexibility) New ways of interacting: accessibility support Support of specific standards (mostly communication and interfaces) Portability: support of specific hardware boards (performance optimization) Functionality and completeness can be less demanding in some cases (for now) Provide both browser as an application and as a runtime Building a Browser for Automotive Juan J. Sánchez Available alternatives Option 1) Licensing a proprietary solution: might bring a reduced time-to-market but involves a cost per unit and lack of flexibility Option 2) Deriving a new browser from the main open source browser technologies: Firefox (Gecko) Chromium WebKit (Safari and others) Mozilla removed support in their engine for third
  • Web Standards.Pdf

    Web Standards.Pdf

    BOOKS FOR PROFESSIONALS BY PROFESSIONALS® Sikos, Ph.D. RELATED Web Standards Web Standards: Mastering HTML5, CSS3, and XML gives you a deep understand- ing of how web standards can be applied to improve your website. You will also find solutions to some of the most common website problems. You will learn how to create fully standards-compliant websites and provide search engine-optimized Web documents with faster download times, accurate rendering, lower development costs, and easy maintenance. Web Standards: Mastering HTML5, CSS3, and XML describes how you can make the most of web standards, through technology discussions as well as practical sam- ple code. As a web developer, you’ll have seen problems with inconsistent appearance and behavior of the same site in different browsers. Web standards can and should be used to completely eliminate these problems. With Web Standards, you’ll learn how to: • Hand code valid markup, styles, and news feeds • Provide meaningful semantics and machine-readable metadata • Restrict markup to semantics and provide reliable layout • Achieve full standards compliance Web standardization is not a sacrifice! By using this book, we can create and maintain a better, well-formed Web for everyone. CSS3, and XML CSS3, Mastering HTML5, US $49.99 Shelve in Web Development/General User level: Intermediate–Advanced SOURCE CODE ONLINE www.apress.com www.it-ebooks.info For your convenience Apress has placed some of the front matter material after the index. Please use the Bookmarks and Contents at a Glance links to access them. www.it-ebooks.info Contents at a Glance About the Author................................................................................................