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
nfc_recordType_text-manual.https.html 
<!DOCTYPE html>
<meta charset=utf-8>
<title>Web NFC Test: push and watch text records</title>
<link rel="author" title="Intel" href="http://www.intel.com"/>
<link rel="help" href="https://w3c.github.io/web-nfc/"/>
<meta name="timeout" content="long">
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="resources/nfc_help.js"></script>
<meta name="flags" content="interact">

<p>Tap an NFC tag to the test device with NFC support.</p>

<p>Note: All the actions need to be done in 60 seconds, otherwise it will get TIMEOUT.</p>

<div id="log"></div>

<script>

"use strict";

setup({ explicit_timeout: true });

let desc = "Test that nfc.push and nfc.watch succeed when recordType is set to 'text'."
let watchOptions = {
  recordType : "text",
  mediaType : "text/plain",
  url : ""
}
let message = createMessage([createTextRecord(test_text_data)]);

testNFCMessage(message, watchOptions, desc);

</script>
back to top