Guillaume Grossetie ggrossetie

Page-based counters

Page counter instances

If a counter is reset or incremented within the page context, it is in scope for all page-margin boxes and obscures all counters of the same name within the document.

— https://www.w3.org/TR/css-page-3/#page-based-counters

This sentence in the specification is unclear. What "obscures" means in this context? Does it mean that if a counter named "page" is reset or incremented within the document it has no effect on the page counter within the page context?

Keybase proof

I hereby claim:

I am ggrossetie on github.
I am ggrossetie (https://keybase.io/ggrossetie) on keybase.
I have a public key whose fingerprint is B9F7 CFC8 FFE1 4C0D 9A9B AEA9 76FE 1782 2EE4 C889

To claim this, I am signing this object:

Image target path auto-completion

Introduction

This feature is designed to help authors quickly find images in their workspace and reference them in their AsciiDoc document.

Scope

Applies to both image:: and image:.

	str1 = 'white chocolate'
	str2 = 'a1'
	str3 = 'dog'

	regex2 = /\d/
	regex3 = /\w+/

	benchmark 'gsub-string' do
	r1 = str1.gsub('white', 'dark')
	end

	class Invoker {
	async invoke() {
	// we need to add "await" otherwise "convertFromStdin" will not be completed when we "do something"
	Invoker.convertFromStdin()
	}

	static async convertFromStdin() {
	console.log('>>> convertFromStdin')
	const data = await Invoker.readFromStdin()
	console.log('<<< convertFromStdin', data)

	.doc .admonitionblock .icon {
	border-radius: 1rem;
	}

	i.fa[class^='icon-'],
	i.fa[class*=' fa-']::before,
	i.fa[class*=' icon-']::before {
	content: "";
	height: 1.25rem;
	width: 1.25rem;

	Acacia
	Agana
	Arum
	Aster
	Beam
	Bibemus
	Bora
	Brume
	Broma
	Blossom

	const Benchmark = require('benchmark')
	const process = require('process')

	Object.setPrototypeOf(Array.prototype, {})

	function arrayUnshift (list, elems) {
	for (var i = elems.length - 1; i >= 0; i--) {
	list.unshift(elems[i]);
	}
	}