@_minego links with the
rel semantic can be used both in human-visible markup for improved back-compatibility and quick error-spotting (as well as layering on top of existing solution) and also in HTTP headers for machine-only use
I thought I understood what the Shadow DOM was. Then I read w3.org/TR/shadow-dom
Any element in a shadow tree can be a shadow host, thus producing nested shadow trees. A shadow tree is nested when its shadow host is itself a part of a shadow tree. Conversely, a shadow tree A is said to be nesting the shadow tree B if B is nested by A. If a shadow host is declared in the document, the document is the nesting tree of its shadow trees.
One case that deserves special consideration is the situation when an insertion point is a child node of another shadow host. In such situations, the nodes distributed into that insertion point must appear as if they were child nodes of the shadow host in the context of distribution within the shadow tree, hosted by said shadow host. Thus, the nodes distributed to a shadow tree could have already been distributed by the nesting tree. The effect of a node being distributed into more than one insertion point is called reprojection.
While pondering if his company should start looking for a new designer
Well done, Bob! With the cup of coffee still half-full, the work is complete. Recognizing his awesomeness, Bob returns to teaching n00bs the ways of WoW.
// TODO(alice): Check designer's desk for hallucinogens.
takes the cake for using shadow tree composition in such a cool way.
@jkphl hm that’s an interesting case —
href is technically a url-potentially-surrounded-by-spaces, question is whether or not it’s php-mf2’s responsibility to strip out the spaces in
u- properties. I’d say it is, as those spaces are never going to be useful data which we’re throwing away, so opened an issue.
The medium with which you choose to express a message shapes that message — be careful it doesn’t contradict it.
articlemarkup — even js-generated markup is predictably disgusting
Everything about this is anti-web, practically screaming “ignore me”.
Finally found official name enwp.org/False_dilemma for when people see N options when in fact there are at least N+1, of which the unconsidered options may be superior and considering only N options creates boxed-in thinking.
Examples: ATOM vs RSS (unconsidered: HTML), Tíu Dropar multiple tipjars, where competing tipjars blot out the option of not tipping.
”standard output formats such as RSS… …(and plain HTML, of course)”
Emphasis mine. From Motivation - Atom Wiki
From now on I am framing all web standards-type discussions with the question “what is it reasonable to demand that authors do”
For example, it’s not reasonable to demand authors publish content in more than one format. It’s not reasonable to demand that authors learn how RDF works. It is reasonable to require authors to publish HTML. It is reasonable to require authors to add some simple microformats like rel-author, h-entry or h-card.
I’m having trouble figuring out whether my complete inability to understand why RDF is useful is caused by my own stupidity, or if my brain has a built-in nonsenseguard which blocks out unproductive, overcomplicated technology
id attribute isn’t good enough for RDFa ‘lite’, apparently it needs the new
But if you need compatibility with older browsers, a table might still be the best tool for the job.
Oh practicaltypography.com, you were doing so well. Table styling via CSS, yes. Table markup, never apart from data tables.
Looks like google isn’t just counting items in data tables, lists too:
/cc Tantek Çelik
Does @mozilla webapp installation actually work? In FF Nightly I see the install, confirmation check, confirmation notification and “launch” button on-page, but then I can’t actually launch anything. It’s also stated that I can launch the application from my Applications folder — but it’s not there.
@thatEmil yet another reason not to read dead-tree books about HTML5 :/
#microformats2 wild examples list growing quickly, will your site be the next? microformats.org/wiki/microformats2#Examples_in_the_wild
I’m thinking the time might have come to write a wrapper around #php DOMDocument which actually makes it usable. Thoughts:
querySelectorAllare implemented for both the document and individual elements via Symfony XPath → CSS converter and relative XPath queries