wpt | Test suites for Web platform specs — including WHATWG | Automation library

https://wiki.whatwg.org/wiki/Parser_tests

This question on the whatwg mailing list from 2013:

Hello everyone.

I was wondering if there is some sort of tests for the Tokenizer along with the correct output of tokens as well as a way of representing tokens.
What I have in mind is running the tokenizer on some HTML input and printing the tokens in the same way the correct output is written.
I will then be comparing the result I have with the correct one provided character by character. :)

Which led to the answer:

http://code.google.com/p/html5lib/source/browse/#hg%2Ftestdata%2Ftokenizer

http://wiki.whatwg.org/wiki/Parser_tests has some documentation of the format.

The Google Code link is obviously dead, but the wiki page does explain it:

Parser tests

html5lib-tests is a suite of unit tests for use by implementations of the HTML spec. The aim is to produce implementation-independent, self-describing tests that can be shared between any groups working on these technologies. The parser tests live in the tokenizer and tree-construction directories, both of which contain README files describing the test format.

Which links to the (current) GitHub page, and the tokenizer folder of test cases:

The test cases are a series of JSON files, each containing an array of test cases:

Per the very informative answer of UninformedUser:

It looks like you probably want to use ZipFile to first load a zip archive, then call the extractall method on that instance. Something like:

The answer is exactly what I knew it would be.

• i started with headers translated by Franck Soranio
• where some definitions were packed records
• when that didn't work, I tried adding $ALIGN 8 - the ABI required by Windows
• when that didn't work, I tried adding packed to all records

When that didn't work, i asked Stackoverflow.

In the meantime, i spun up Visual Studio C++, and compared the sizeof of the original structures, and the Delphi translations.

They didn't match.

The problem was the packed records.

• sizeof(EVENT_TRACE_LOGFILEW): 416 bytes (was 404)
  • sizeof(EVENT_TRACE): 88 bytes (was 80)
    • sizeof(EVENT_TRACE_HEADER): 44 bytes (was 40)
  • sizeof(TRACE_LOGFILE_HEADER): 272 bytes

Removing the record packing fixed it.

It looks like I've managed to work it out.

I needed to:

• JOIN to wp_posts

With the link keys:

• TABLE : wp_postmeta
  • column : meta_key
• TABLE : wp_posts
  • column : ID

Not sure what software you're using to do the transformation, so I'll assume you're restricted to XSLT 1.0.

Here's how I would do it:

Regex is a whole world by itself. There are usually several approaches to reach the same result. Here is one of these approaches:

From the CSSOM specification:

If the value is internally represented as an integer between 0 and 255 inclusive (i.e. 8-bit unsigned integer), follow these steps:

1. Let alpha be the given integer.
2. If there exists an integer between 0 and 100 inclusive that, when multiplied with 2.55 and rounded to the closest integer (rounding up if two values are equally close), equals alpha, let rounded be that integer divided by 100.
3. Otherwise, let rounded be alpha divided by 0.255 and rounded to the closest integer (rounding up if two values are equally close), divided by 1000.
4. Return the result of serializing rounded as a . Otherwise, return the result of serializing the given value as a .

Assuming that the color opacity is stored as a binary value:

From https://web.dev/nfc/#security-and-permissions

Web NFC is only available to top-level frames and secure browsing contexts (HTTPS only). Origins must first request the "nfc" permission while handling a user gesture (e.g a button click). The NDEFReader scan() and write() methods trigger a user prompt, if access was not previously granted.

I guess you are running from a file:// URL as you said "locally" which is not supported.
You need to host it from a local web server using a https:// URL

Once in the right scope trying to scan or write should trigger a user prompt.

You can also check permissions see https://web.dev/nfc/#check-for-permission

Update:
So I tried the sample page https://googlechrome.github.io/samples/web-nfc/

And this works for me on Android Chrome 87 with "Experimental Web Platform features" enabled

When you hit the scan button A dialog asking for permission pops up.

Comparing the code in this sample to yours I notice that does:-