(apology accepted)?
Three lives that span an era.
(apology accepted)?
Self Portrait in a Bowler Hat, 1874 ❧ The Bathers, 1874 ❧ The Fishermen ~ Fantastic Scene ❧ Madame Cézanne, La Boule in a Red Dress, 1877 ❧ Leda and the Swan, 1880-82 ❧ Harlequin, 1839 ❧ Pine and Red Earth, 1895 ❧ La Maison Maria, 1895 ❧ Still Life with Carafe, Bottle, and Fruit, 1906
Self Portrait with Bandaged Ear, 1874 ❧ Sunflowers Still Life, 1887 & Sunflowers, 1888-1889 ❧ Van Gogh's Chair, 1888 ❧ Irises, 1889 ❧ A Wheatfield with Cypresses, 1889 ❧ Farms Near Auvers, 1890 & Houses among Auvers Farms, 1890 ❧ Long Grass with Butterflies, 1890 ❧ View of Vessenots near Auvers, 1890 ❧ Landscape with a Carriage and a Train, 1890
Self Portraits, 1896-1972 ❧ The Old Guitarist, 1904 ❧ Les Demoiselles d'Avignon, 1907 ❧ Three Women, 1908 ❧ Portrait of a Lady, 1921 ❧ Bull State VII, 1945 ❧ Mediterranean Landscape, 1952 ❧ Homme a la Pipe, 1969 ❧ Tete d'Hom, 1972
CSS-Play • W3 Schools • Rebecca • W3C • Wikipedia
In a technical nutshell, viewport grid input-label links observe emerging HTML technology.
Viewport Grid: a page containing more than one viewport grid, also called “grid page”, or just “grid”. Access requires a grid menu system ~ attached to a grid layout system.
Grid Scrolling: construction implements secure browser object handling behaviours. However, that security entails restricted control of page objects (content). Secure content restrictions lock out usual hypertext linking protocols. Generating the context of this discussion. How can we link the grid icons to the grid pages, in their exising layout, that is as viewport objects, on the HTML grid, where each grid provides display boundaries of the HTML grid-page?
Usage: page refresh returns browser to the opening page show. However, as long as the browser window page tab remains open, link or scroll position in each input-label virtual page is retained. So that link and/or scroll origin position displays on return to grid menu virtual page, using the top left nav buttons.
Issue: cannot link grid menu A1-A9 to virtual pages using traditional inline link tags and bookmarks, while retaining 'link memory' to re-open links at last visited location on a virtual page.
CSS-Play demonstration presents the same issue. How can we link from one grid ‘virtual page’ to another grid ‘virtual page’?
Solution: each grid ‘page’ is a scrolling div id container, so deploy targetting grid input/label tag relationship to target id in the link structure.
<a href="#grid4">
Return from the linked virtual page to the previously active source virtual page by simply clicking that source page's button in the top left nav (in the example below, click inline link to Grid4 and return here to Grid 3 using nav button A-3).
<input type="radio" name="panel" id="x4">
<label for="y1">
A4 LINK TEXT
</a>
Code:
Working link:
<a href="#grid3">
<input type="radio" name="panel" id="x3">
<label for="x3">
A3 LINK TEXT
</a>
Working link:
<a href="#grid4">
<input type="radio" name="panel" id="x4">
<label for="y1">
A4 LINK TEXT
</a>
Code: construct a grid menu using input tags
<input type="radio" name="panel" id="x1">
<input type="radio" name="panel" id="x2">
<input type="radio" name="panel" id="x3">
<input type="radio" name="panel" id="y1">
<input type="radio" name="panel" id="y2">
<input type="radio" name="panel" id="y3">
<input type="radio" name="panel" id="z1">
<input type="radio" name="panel" id="z2">
<input type="radio" name="panel" id="z3">
and now build lables for each input tag
<div class="labels">
<nav>
<label for="x1">a1</label>
<label for="x2">a2</label>
<label for="x3">a3</label>
<label for="y1">a4</label>
<label for="y2">a5</label>
<label for="y3">a6</label>
<label for="z1">a7</label>
<label for="z2">a8</label>
<label for="z3">a9</label>
</nav>
</div>
and now build each id container, input-label tags will link to container id targets
<div id="wrapper">
<div id="a1">
<div class="inner">
<h1>Pablo Picasso... etc.
note that inside target containers, any input-label link can be deployed using the grid menu link content
<a href="#grid3">
<input type="radio" name="panel" id="x3">
<label for="x3">
A3 LINK TEXT
</a>
<a href="#grid4">
<input type="radio" name="panel" id="x4">
<label for="y1">
A4 LINK TEXT
</a>
</div>
</div>
</div>
CSS now to style grid menu and virtual page content noting that a visible transition from one virtual page area to another virtual page area features the input-label grid menu
a, a label { color: dodgerblue; cursor: pointer; text-decoration: none; }
#wrapper { height: auto; left: 0vw; position: fixed; top: 0vh; transition: left 1s, top 1s 1s; width: auto }
#wrapper > div { background: transparent; height: 100vh; overflow: auto; overflow: x-hidden; position: absolute; width: 100vw; -webkit-overflow-scrolling: touch }
.inner { background: white; border: aliceblue solid medium; border-radius: 1rem; margin: 2vh 15vw; object-fit: contain; padding: 5vh 1vw; text-align: center; width: 70vw; }
* the following input data is required
div[id*="a"] { top: 0; }
div[id*="b"] { top: 100vh; }
div[id*="c"] { top: 200vh; }
div[id*="1"] { left: 0; }
div[id*="2"] { left: 100vw; }
div[id*="3"] { left: 200vw; }
input { display: none; }
input:target { display: table; position: absolute; }
input[id*="x"]:checked ~ #wrapper { top: 0vh; }
input[id*="y"]:checked ~ #wrapper { top: -100vh; }
input[id*="z"]:checked ~ #wrapper { top: -200vh; }
input[id*="1"]:checked ~ #wrapper { left: 0vw; }
input[id*="2"]:checked ~ #wrapper { left: -100vw; }
input[id*="3"]:checked ~ #wrapper { left: -200vw; }
input#x1:checked ~ .labels label:nth-of-type(1),
input#x2:checked ~ .labels label:nth-of-type(2),
input#x3:checked ~ .labels label:nth-of-type(3),
input#y1:checked ~ .labels label:nth-of-type(4),
input#y2:checked ~ .labels label:nth-of-type(5),
input#y3:checked ~ .labels label:nth-of-type(6),
input#z1:checked ~ .labels label:nth-of-type(7),
input#z2:checked ~ .labels label:nth-of-type(8),
input#z3:checked ~ .labels label:nth-of-type(9) { background: rgba(140, 140, 140, 0.8); }
Viewport declarations are required to construct a virtual 'grid' page. The head tag must contain viewport data:
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<meta id="viewport" name="viewport" content="width=device-width, minimum-scale=1.0, maximum-scale=1.0">
Tags <input> and <label> help browsers to display a scrolling space for each page's div-id. An unlimited number of id-defined ‘grid pages’ can be inserted into any viewport grid HTML page. For our Gallery, we group 9 pages (div id="a") in a 3x3 grid (input id="z")
Navigation builds links to grid ‘pages’ with 2 groups of html tags: <input> and <label> tags. At the beginning of <body> tag, 9 <input> tags are used to list 9 <input> items. One <input> item can be made to appear <checked> by default. The default loading page is indicated thus:
<input type="radio" name="panel" id="x1" checked="checked">
However, browser interaction with input and label tags works better without the 'leaky' checked=checked detail. Which may cause unintended nav highlighting of 2 or more pages. And which destabilizes inline grid links.
Linking grid ‘page’ content must be placed after the opening <input> code lines, and after the opening <label> code lines, but within the <a> element that ponits to grids 1-9.
<a href="#grid3">
<input type="radio" name="panel" id="x3">
<label for="x3">
A3 LINK TEXT
</a>
Just before the closing </body> tag, each <input> item is provided with the corresponding <label> tags:
<label for="x1">a1</label>, etc. Within the <Data Input> schema, at the bottom of the page.
The problem with Viewport Grid page linking is that even newer browsers cannot find <div id="link-target"> where the <input>/>label> navigation is active (readable). This would appear to be a Net4 limitation, for as we begin leaking Net5 capacities in early 2018, now the >href> linking on the <input>/<label> Viewport Grid pages is improving.
Note that the <background-image> property is used to avoid conflict with the <label> cacscade that includes many <img> tags in the Gallery style hierarchy. We tried the <content> property (housing the image url), but that conflicted and was ignored. Cascade isolation provided by <content> property is ‘preferred’ by W3Schools.com in the Net4 schema. However, the upcoming Net5 schema would likely return to more robust direct embedded element calls, as this leaves room to isolate multi-interface cascades around the style-object media-hub, in emerging dedicated languages' syntax. In other words, HTML5 Viewport Grid page technology presents hub-input as <input-label> calls, and hub-output as styled <img> object, leaving lots of room for interpretation by complimentary code languages.
Did anyone ever tell you how this site was inspired in the first place by CSS Play? Well it was, you know. And now you know for sure!
CSS Play (http://www.cssplay.co.uk) has been curated by Stu Nichols for decades.
Now, in forums a-plenty and everywhere else we look, the Nichols entity only exists as a collect-on-and-on forever TEACHER persona in Dageurotype-like photos, and nobody online knows who he is. Compare, for example, Michael E, musician ~ check out his video credentials yourself(or download the video here).
One day, beleive-me-or-not a mountain of personal online research narrowed down this STU entity to a United Kingdom Technical University. Have we left Nichols behind, lost in cyberspace? Or do we leave you, our readers, to ponder whatever the "S"may stand for... long string of thoughts here.
Which would explain how the entity whom we know has inspired this rant is factually ever-so-many unique pages and emails over the years and decades. Another fabulously creator of our world wide web. Perhaps the best loved British professors get tossed into a giant STU'ing pot, souped, so-to-speak. Tastey and nutritious cerebral prosperity. Truly!
For solid proof-positive, kindly visit wherein more of CSS Play.
Its always a fascinating circus of odd-balls painting pictures of your actual hunger organ. To make you want to eat more. Check it out. Check the address bars when you RESEARCH those pages.
Because if you see... OF COURSE YOU KNOW
You hit it again... Another "404"
Well, that's it, honey. IT means:
"NOT ALLOWED!"
"NOTHING HERE!"
"NOT SUPPOSED TO KNOW!"
It's actual EXPERIMENTAL PSYCHOLOGY!
Because we found the proof, of course... ONLINE!
((( where else )))
Cougar Charlie's hot-tub Trumpet sociopathic reach out Bucky amerigoround, ship-rat back home Europe not sadly? Game plan, help Lizzy’s Charlie pay 127 trillion Euro debt that jumps from 4% to 8% interest when croppers brexit to loot jobless governmment banks in colony amerigos, Euro vested down to terrra del fuego, hop to baffin island, ausimandius, kiwi-and-everywherelses...
LOOT! LOOT! LOOT! Kids.
Simply explain! Trump wants the FBI removed. Enforcement of law and enforcement professionals not appreciated by Trump and his goons, as they try to insert fake votes to fake Trump goons winning an election for President. But remember... that faking is not an illegal thing to do for Trump (Trump thinks) because he says he is allowed retribution. Which makes anything that Trump wants legal, Trump reminds us all. Because his friends are Proud Boys. And they all say,
"IF YOU COME AFTER ME, I'M COMING FOR YOU".
Every which way Trump turns, he says it exactly like he is, con man and liar.
Candidate?
Do not pass GO. Go directly to Jail.
Grand Mother always did say,
We live in a wacky world
.