W3C Set To Publish HTML 5.1, Work Already Started On HTML 5.2 (softpedia.com)

An anonymous reader quotes a report from Softpedia: Members of the World Wide Web Consortium (W3C) are getting ready to launch the HTML 5.1 specification and have already started work on the upcoming HTML 5.2 version since mid-August. The HTML 5.1 standard has been promoted from a "Release Candidate" to a "Proposed Recommendation," the last step before it becomes a "W3C Recommendation," and officially replaces HTML 5 as the current HTML standard. As a Proposed Recommendation, HTML 5.1 is practically locked against major changes, and outside small tweaks here and there, we are currently looking at a 99.99 percent version of the upcoming HTML 5.1 standard. The vote to promote HTML 5.1 from RC to PR was approved in unanimity, a clear sign that major browser makers have reached a general consensus on what the standard should look like, and what they should be implementing in their browsers in upcoming versions. You can read more on HTML 5.1 here, the changes and support table here, and the HTML 5.2 specification draft here.

Comments

Re:Funny

[Narcocide]

I don't see anything funny about that. Get ready for the bad old days of massive browser implementation incompatibilities to come back with full force when Google and Apple inevitably turn on each other and start playing tug-of-war with the standard while trampling Mozilla in the process.

Fuck the spec

[Snotnose]

I wanna know how to reliably turn off auto-play video/audio under the current version of chrome and html5. Yeah, I've googled it and set the settings. The settings are routinely ignored.

I don't know anyone who likes autoplay video/audio, which is why the marketers love it so much. Fuck them all, poke their eye out and fuck them in the skull.

Html5 is making me miss flash, something I never thought would happen.

Re:Fuck the spec

[tlhIngan]

This is absolutely the case. Autoplay is a static attribute to the HTML5 video tag and can be set to be ignored by browsers, but there is also a Javascript API for HTML5 video playback and it is trivial to start playback from there. Technically that is not "autoplay", it is just, "play" that happens to be triggered on page load via Javascript.

And what happens is that the play command gets lumped in with the popup blocker commands that get ignored on page loads, which lets the play command work AFTER the page loads, but it doesn't start if it's part of the page load.

An alternative is to ignore the play command if the tab isn't visible. And just in case, we can have a right-click menu option to send the play command as well in case someone tries to be tricky and assume the video start playing immediately.

Firefox does respect your settings

[Anonymous Coward]

I don't know anyone who likes autoplay video/audio, which is why the marketers love it so much. Fuck them all, poke their eye out and fuck them in the skull.

Launch Firefox, browse about:config, find media.autoplay.enabled and set to false. No video autoplay anymore, on every site.

On the flip side, you have to click play every video of every page of every video site, news site, sport site, gaming site etc. Your choice.

Re:Firefox does respect your settings

[secretsquirel]

And get weird behavior where you need to click play, which sets it to pause, then play again to get it to play, and sometimes messes up animated gif.

All in all works great though, fuck autoplay.

Teased, burned

[Tablizer]

I had read that HTML 5 supported form-input date checking and had a pop-up calendar doo-dad. But the only format supported across browser brands is YYYY-MM-DD format, which is NOT what most customers in USA want.

You can twiddle with CSS etc. per brand and version, but one then might as well go back to time-tested JavaScript shit...

I'm tired of fiddling with piddly grunt UI issues, I wish I could focus on domain logic. It gets really boring seeing 25-year-old GUI idioms get both re- and mis-implemented 20 different ways over the years.

Forget keeping up with the damned Fadjoneses, just make a GUI standard that fucking works! Who cares if it looks like Windows 95, as long as its normal and works. Fuck the slidy animated throbbing doo-dads; they'll look "outdated" in 2 years anyhow to be replaced by mutant neon polkadots or whatnot and all the fanboys will chase yet another pot of UI gold beyond the horizon.

and git off my lawn!

Re:Teased, burned

[kbg]

Yes it is unbelieve that standard input fields are currently not available. What I would like to see as standard input fields on the web.

1) Date field where you can specify how the date is displayed to the user and how the date field is actually sent to the server.
2) Time field with same option as the date field.
3) Timestamp field with date time.
4) Date range field.
5) Integer number field with max min values but not with incremental buttons, and that display only number input on mobile.
6) Currency field with specified currency and max min values.
7) Country selector field with flag display that submits country code.
8) Credit card number field, max min size and with optional LUHN check before submit.
9) Phone number field with country selector.
10) Email field with validation
11) Simple HTML editor field with simple formatting like bold, italics, numbered lists e.t.c
12) Image attachment field. Where you can select an image on your hard disk and it displays as an image in the browser before you submit.
13) Video attachment field. Where you can select a video on your hard disk and it displays as a video in the browser before you submit.
14) Audio attachment field. Where you can select an audio on your hard disk and it displays as audio in the browser before you submit.
15) Simple table editor field. Where you can specify the table data as input in CSV and the result as are sent as CSV.

All of these input fields are possible today but with a lot of kludges and hacking and very specific custom HTML. As it is now everybody in the world has to implement all of these types again and again.

Re:Bloat

[Tablizer]

Is it just me or HTML spec start to be a f***ing mess? Google, Apple, Microsoft, .... please leave HTML markup standard alone!

The HTML stack (HTML/CSS/JS/DOM) has jumped the shark so many times, the shark got carpal tunnel of the eyes.

Real features..

[CptLoRes]

Where are the new features that people actually need? Like for example being able to watch a live video stream in a browser without being a web guru and relying in complex server infrastructure. Instead of a simple [img src="rtsp://videoserver/live1/"] being part of the standard, we have all these big players pushing complex "trying to solve everything" systems that nobody but a select few have the time and resources to get up and running properly.

Partialy Answered

[bussdriver]

HTML 5.0 draft (before W3C got into their stupid versioning) contained some of your request already.

1-2) ISO date format needs to be forced upon everybody. like the metric system. However, the spec doesn't require the browser display with it. Browsers are free to display the date in a localized format while submitting the proper ISO format. This wouldn't be much different than how Options display different values. Perhaps the spec should mention this so nobody fears doing this...

3) HTML5 is good enough already; doubt you'll get them going further anytime soon. I can imagine from my experience with them that is how it'll go. I agree with you that it would be convenient.

5) Initially, integer didn't suggest a incremental button (that I recall) but later the spec showed an example. The problem with presenting suggestions or screenshots of implementations is that every literal minded developer will copy it. The CSS groups are slow as hell and not in sync with HTML5 like it should be; could be how they create lots of tiny CSS working groups with narrow focuses and that doesn't respond to HTML5's requirements well enough yet. HTML5 tries to define appearances in CSS but that becomes a chicken/egg problem. Turning on the incremental buttons needs to be CSS... a slider presentation would also make sense (there is a big bias towards minimalism. Yet METER is creating quite the CSS challenge for them... which will be much more complex if they just begin to address all the requests out there for it.)

6) Would be nice; however almost everything has either 2 decimals or 0. Just a few have 3. So an integer with step=0.01 would work well enough. Don't expect that to happen. Currency conversion or selection won't happen; that is too complex - you implement it. It would need to know what currencies you support so then you are somehow using a bunch of option tags or creating some odd list attribute.

7) Country selector would also be nice. possible issues are related to constantly changing flags and countries in less stable places. If you implement it then you are in charge of handling those situations. You can do a Select with country flags already before HTML5.

8) Credit cards - update related issues long term. similar issues as country listings but worse. Perhaps you can gain traction with the working group if you team up with a browser and aim towards CHIP and RFID support --- maybe we could finally get an encryption input !! It's not a new issue and they never handled the 2-way communication that is involved with an encryption input. (nobody even touches the cert authentication features in the browsers already except http://startssl.com/

9) HTML5. has it. no validation possible. But it SHOULD use the proper keypad on a phone. I investigated this; it's crazy to go global with it which is why it was left open. Implementing is way too much work. With VOIP it seems that it would be pointless long term because any kind of phone number could be used anywhere; restricting this will become an issue in addition to keeping up with global changes in format. The only standard is the international prefix... except I found a few places where that didn't even apply within their country.

10) HTML5 did it already. Has the best RegEx for email too- it's in the spec. check it out!

11) HTML5 doesn't handle editors; however W3C is trying to standardize kludges. the groundwork on roles helps slightly but yes, it's all kludges. There are so many options on this one that it is highly unlikely to standardize. They really don't like taking something with a million options and standardizing on 1 simple solution.

12-14) Yes, that would be nice. However they have added groundwork to make that much easier for you to do in HTML5. drag-n-drop files; local file access; AJAX file upload. The old "accept" attribute does work even though it's use is optional.

15) never. same as 11. but 11, 12-14 related features make it easier to implement (because