screenshot from ‣ (now since fixed with first workaround)