The Uncertain Web

Spis treści książki

• The Uncertain Web
• Preface
  • A Word on the Web Today
  • Who Should Read This Book
  • Navigating This Book
  • Online Resources
  • Conventions Used in This Book
  • Using Code Examples
  • Safari Books Online
  • How to Contact Us
  • Acknowledgments
• 1. Embracing Uncertainty
  • Embrace Uncertainty
  • From Microsofts Monoculture to Todays Healthy Chaos
  • Where We Are Right Now
    • Browsers
    • The Open Web Platform
      • Web standards, Flash, and the rebirth of the Open Web Platform
      • The WHATWG
      • Ajax
      • Tracking the Open Web Platform today
    • Connection Speeds and Quality
    • The HumanComputer Interface
    • Screen Resolution and Orientation
    • Pixel Density
    • Whats 2% Anyway?
    • This Is What We Wanted
• 2. Navigating the Uncertain Web
  • Dont Blame the Web for Being the Web
  • Identify and Embrace Your Audience
  • Test and Pray for the Best
  • Focus on Optimal, Not Absolute Solutions
  • Embrace Accessibility
    • Provide Text Alternatives for All Non-Text Content
    • Ensure Information and Structure Can Be Separated from Presentation
    • Make All Functionality Operable via a Keyboard Interface
    • Content Can Be Paused by the User Unless the Timing or Movement Is Part of an Activity Where Timing or Movement Is Essential
    • Provide Mechanisms to Help Users Find Content, Orient Themselves Within It, and Navigate Through It
    • Help Users Avoid Mistakes and Make It Easy to Correct Mistakes
    • Support Compatibility with Current and Future User Agents (Including Assistive Technologies)
    • Dont Stop There
  • Lose Your Technology Biases
    • The iPhone Is the Only Mobile Experience
    • Closed. Wont Fix. Cant Reproduce.
    • Contrary to Popular Opinion, Internet Explorer Does Exist
    • Embrace Empathy
  • Lose Your Stack Biases
    • jQuery
    • MVWhatever
  • Keep at Least One Eye on the Cutting Edge
  • Spread Your Wings (and Question Your Assumptions)
• 3. Lay a Foundation for the Future with Feature Detection and Polyfills
  • Feature Detection
    • Looking at a More Complicated Feature Detection
  • Using Modernizr
    • Old IE: The One Thing Modernizr Does Modernize
    • Using (and Not Using) Modernizr
    • Feature Detection with Modernizr
    • Customizing Modernizr
    • Using Modernizrs Tests
    • Cross Browser Polyfills
    • Additional Modernizr Methods
      • Modernizr.prefixed()
      • Modernizr.mq()
    • Managing the Undetectables
      • You can browser sniff
      • You can limit your use of these features to safe implementations
      • Design robust systems that work in many different configurations
      • Forgo the feature entirely
    • Common Feature Tests and Associated Polyfills
      • Modernizr.touch
      • Modernizr.input
      • Modernizr.csstransitions, Modernizr.csstransforms3d, and Modernizr.csstransforms
      • Modernizr.inputtypes
      • Modernizr.canvas and Modernizr.svg
      • Modernizr.fontface
      • Modernizr.video
  • Frontend Development Done Right
• 4. Selecting Responsive Design or Another Mobile Experience
  • Boston Globes RWD Redesign
  • Really? RWD for Every Site?
  • Mobile First, RESS, and the Rest of the Mobile Development Universe
    • Dedicated Mobile Experience
    • Mobile First
    • Progressive Enhancement
    • RESS
  • Choosing a Development Path
    • The Size and Skills of Your Team
    • The Requirements of Your Site or Application
    • Your Demographics
    • Your Budget
    • Benefits of RWD
      • Simplified server side
      • Easier maintenance
      • Lower overall application complexity
      • One entry point for search engines
      • Support for future and unknown devices
    • Downsides of RWD
      • Performance
      • Limited application flexibility
    • Benefits of a Dedicated Mobile Experience
      • Performance optimized for specific devices
      • Heightened application flexibility
    • Downsides of a Dedicated Mobile Experience
      • More complexity on the server side
      • Tougher maintenance
      • Not as good for search engines
      • Link management
      • You can miss detection of new and unknown devices
      • Detection schemes that use the user agent string can be spoofed
    • If Facebook Jumped Off a Bridge, Would You Jump Off a Bridge, Too? Or: What Do the Biggest Sites in the United States Do?
    • Choose the Architecture That Makes Sense for Your Project
      • Frontend developers and small teams
      • Content sites
      • Applications
      • Big teams and big budgets
  • Redirects Should Resolve Logically
  • Redirect Options
    • Simple Redirection
    • Options for More Complicated Queries
  • Always Offer an Escape from the Mobile Version
  • Be Fluid and Design for Your Design
    • Feel Free to Abuse Minor Breakpoints
    • On Relative Units
  • Accepting the Ebb and Flow of Things
• 5. Working with User Input
  • The State of User Input on the Web
    • The Conceptual Problem with Touch Detection
    • The Technical Problem with Touch Detection
      • Using touch APIs to detect touch is faulty
      • Small screen might not be touchlarge screen might be
      • The future isnt here yet
  • What It Means to Get It Wrong
    • You Can Fail Completely
    • You Can Fail Just a Little
  • Design for a Spectrum of Potential User Inputs
    • Lean Toward Finger-Friendly Interfaces for All Interfaces
    • Dont Rely on Hover
    • Embrace Clarity
  • Working with the Full User Input Spectrum
    • The Current State of Touch and Mouse Event Handling
      • You dont have to do anything new
      • One major catch: Theres a 300ms delay on compatibility click events
      • Working with the *move events
      • Pointer events: One event model for mouse, touch, and more
  • Assume Nothing and Accommodate Everyone
• 6. The Surprisingly Complex World of Images on the Web
  • While We Werent Paying Attention, Images Got Complicated
    • We Want to Serve the Smallest Possible File Size
    • We Need to Take Advantage of the Browser Preloader
    • We Want to Serve Correctly Sized Images to Multiple Resolutions
    • We Need to Serve the Correct Image for Multiple Pixel Ratio Devices
    • We Want to Choose Different Sizes/Images at Different Breakpoints
    • We Want to Use Design Breakpoints
    • Serving the Correct Format
    • Images Are Easy, and They Should Stay Easy
  • Optimizing Images for the Web
    • JPEG
      • Progressive JPEGs
      • GIF
      • PNG
      • SVG
      • WebP
    • Choosing the Right File Format
    • Look for a CDN Solution
  • Responsive Images
    • The Option of Doing Nothing (or Nothing New, at Least)
    • srcset
    • picture
    • Picturefill, the picture Polyfill
  • Embrace SVG
  • On the Server Side
  • A Practical Developers Guide to All of This Complexity
    • Identify How Important Images Are to Your Site
    • Get the Basics Right
    • Use the Simplest Possible Solution
    • Learn to Love SVG
    • Test!
  • Conclusion
• 7. The Horribly Complex World of Web Video
  • The Core Technology
    • The HTML video Element
    • The Flash Fallback
    • Containers and Codecs
    • Video.js
    • Mime Types and Adaptive Bitrate Streaming
      • Mime types
      • Progressive download versus streaming and a performance dead-end for most mortals
  • Letting the Pros Handle It
    • YouTube
    • Vimeo
  • Make the Best of a Complicated Situation
• 8. The Web We Want
  • Things Can Get Better (But They Do Occasionally Get Worse)
    • Firefox Announced Support for h.264
    • Picture Comes Back from the Dead
    • Pointer Events Might Be Dead
    • I Knew Something Like This Would Happen
  • Lets Push Things Forward
    • A Web Built By Developers, Browser Vendors, and Standards Bodies
    • A Web That Is Fast, Widely Available, and Reliable
    • A Web Where Theres Nothing to Win
  • The Web We Want Starts with Us
• Index
• Colophon
• Copyright

pokaż cały spis treści

ukryj recenzje