Quantcast
Channel: Comments on: Scooby Doo and the proposed HTML5 element
Browsing all 8 articles
Browse latest View live

By: steve faulkner

Hi Bruce, as you said the algroithm kind of works in the gamil case. a few comments: 1. the use of menu wil be problematic if and when implemented as it is meant to provide actual interactive UI not...

View Article



By: Bruce

Hi Steve 1) yeah, is the interactive menu part of the main content or not? Hard to choose. 2) that’s to indicate that each email is an article. I’ve updated the image on Flickr to hopefully reflect...

View Article

By: Alohci

Hi Bruce and Steve, I have two questions. 1. It seems to me that if browsers can compute the “main” landmark reliably, then it’s far better than relying on authors to get it right. Is there a use case...

View Article

By: steve faulkner

Hi Alohci It seems to me that if browsers can compute the “main” landmark reliably, then it’s far better than relying on authors to get it right. In order for the user agent to compute the main...

View Article

By: steve faulkner

while I am here (again) would like to clarify a few inacuricies; <blockquote>regarding a proposed (and rejected) element</blockquote> The proposal for an element has been rejected by hixie,...

View Article


By: On HTML5 and the proposed main element | Ian Devlin

[...] such as nav, footer, aside and so on. This has now become known (by a term originally coined by Bruce Lawson) as the “Scooby Doo [...]

View Article

By: » RE: The main issue Bryan Stedman

[...] is the main main element then we might as well do away with main and just use the awesomely named Scooby Doo algorithm   Basically, if we are making computers figured it out anyway, why even use...

View Article

By: scooby doo algorithm – willnorris.com

[...] I learned, while reading about the new <main> element recently added to HTML5, that the Scooby Doo Algorithm is a [...]

View Article

Browsing all 8 articles
Browse latest View live




Latest Images