Please leave your sense of logic at the door, thanks!

WHATWG Weekly: <time> police!

by Anne van Kesteren in Weekly Review

You can now put a fullscreen in your fullscreen. Brought to you by Fullscreen. This is the WHATWG Weekly, not quite weekly, but you are still welcome.

<time> police

Revision 6827 introduced the new time element. The one that also allows for years, yearless dates, durations, and so on. It is based on extensive research by Tantek Çelik. That same Tantek is now battling the <time> police HTML WG co-chairs to get everything synchronized again. I am not privy of what is going on, as it happens behind closed doors.

find() and findAll()

Half a decade later we finally might get the short names for querySelector() that we actually wanted. Or not, it remains to be seen how compatible they are. In any event, Jonas Sicking started a thread on findAll()'s return value. An ECMAScript Array with some extra features.

WHATWG email

Ojan Vafai proposed a tabindexscope attribute for better control of tabbing behavior in a widget that is part of larger application. A little before James Graham suggested constructors for HTML elements. new HTMLButtonElement(), you name it. Michael A. Puls II briefly explains the difference between plugins and native support when it comes to attributes. Gavin Kistner found an oversight in data URL origin determination due to added support for CORS.

Kinuko Yasuda started a long thread on how drag-and-drop of folders is to be supported in the platform. Jonas Sicking suggested nothing much new is needed for that, though Glenn Maynard foresees problems reusing the current API. And on it goes.

Rafael Weinstein suggested a template element that would have special parsing behavior. Basically making the nested elements not do anything (e.g. not fetch images, execute scripts).

Comments are closed.