Skip to main content

Browse the archive

Revision 8d877aacda3215c8ef53f1bb787c7c1d1b5d2fe5 authored by Fredrik Söderquist on 07 November 2018, 09:00:38 UTC, committed by Chromium WPT Sync on 07 November 2018, 09:00:38 UTC 
Recognize 'optimizespeed' and 'optimizequality' for 'image-rendering'
 
In css_properties.json5 we list these keywords but we didn't recognize
them when parsing. Synchronize the two lists.

CSS Images L3 says the following about these two values:

  "This property previously accepted the values optimizeSpeed and
   optimizeQuality. These are now deprecated; a user agent must accept
   them as valid values but must treat them as having the same behavior
   as pixelated and auto respectively, and authors must not use them."

(https://drafts.csswg.org/css-images-3/#propdef-image-rendering)

Bug: 901669
Change-Id: Iecc4f38e711b14fa7b6fd4beb550abdaf99d5b46
1 parent e0e8196
Raw File
nav2_data_uri.html 
<!DOCTYPE html>
<title>data URL source for navigation-timing/nav2_test_open_data_uri.html</title>
<!-- NB: this file isn't actually used any where! -->
<link rel="author" title="Google" href="http://www.google.com/" />
<script>
var observer = new PerformanceObserver(
    function (entryList) {
        parent.postMessage("observed", "*");
        observer.disconnect();
    });
observer.observe({entryTypes: ["navigation"]});
</script>
back to top