Slashdot Mirror
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.
When HTML5 came out, they said HTML 5.1 would come in 2016. Is there a date for HTML 5.2?
> You can read more on HTML 5.1 here, the changes and support table here, and the HTML 5.2 specification draft here.
Oh yeah I'll get right on that, ummhmm..
W3C specs read like stereo instructions. They read like The Handbook for the Recently Deceased.
DRAW A DOOR
Funny how the standard is signed by Google and Apple representatives. No wonder Mozilla is crying about big corporates. They had almost no input in this and they're lagging on a lot of features.
Whatever happened to HTML 5 would be the last version and forever after HTML would be a living spec that's just called "HTML"?
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.
Google and Mozilla have similar features in general. Safari does not. It lags seriously behind. And since Safari on the iPhone is almost all the iphone browser share, you can't just ignore it like Internet Explorer or whats that shit called? Spartan? Edge. Edge actually has way more features to almost match chrome and firefox.
To be blunt, Safari is holding the web back.
It lacks so many features I won't even bother trying to list them all. Some of them are really important like webRTC, Full Screen (on mobile) and Orientation Lock (on mobile)
Is it just me or HTML spec start to be a f***ing mess? Google, Apple, Microsoft, .... please leave HTML markup standard alone!
Will $CURRENT_YEAR be the year of the Linux Desktop?
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.
of iPhones. You can't just skip iPhones. Very important demographic. $$ Mac users also. $$
what is safari's market share on macs? a lot more than %14. and on the iphone? Almost all of it. Not to mention that Chrome on the iPhone has to play by Safari's shitty standards with regards to a lot of things. Its not really like chrome on android.
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!
Table-ized A.I.
Uhm, browser vendors do not implement W3C's HTML... They follow the WHATWG instead.
Browser vendors got fed up with the W3C during the XHTML days and started a new organization. Also, WHATWG's variant does not have versions, instead of "HTML 5.1" it is just called "HTML".
Have you seen the "<iframe allowfullscreen>" tag? Seems to be a marketeers wet dream. And every web users nightmare.
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.
Whatever happened to those? Maybe I'm suffering from good-old-day-ism or simply misremembering, but I seem to remember a point where videos could be put in their own floating, resizable window.
Now they're either a much-too-small region on a web page window or the entire thing fills the screen.
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
Democracy Now! - uncensored, anti-establishment news
You do realize that the W3C is irrelevant, right? The standard that the browsers actually use is developed by the Web Hypertext Application Technology Working Group (WhatWG).
mozilla has a new CEO? awesome. you know who I was talking about though.
See, told you you i've been busy.
the "rhetoric??" lol
Share of users, share of traffic, and share of revenue differ.
Safari has a 4.28% market share on the desktop
Among people willing to buy products and services from Internet businesses, the market share is probably bigger than 4.28%.
and a 14% share on mobile.
Among people willing to buy products and services from Internet businesses, the market share is probably bigger than 14%. Tim Stenovec of Tech Insider summarized a report from IBM Commerce stating that iPhone and iPad users outspent Android users over 3 to 1 on Black Friday 2015. The average iOS user also spends over 9 times as much on paid apps and IAPs than the average Android user.
Assume for a moment that the average iOS user spends 20 times as much money online as the average Android user. If that's the case, then 14% of the users represent 14*20/(14*20+86)*100 = 77% of the money. I don't remember where I read this 20-to-1 figure, but it at least appears consistent with the IBM Commerce report.
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.
Have you even looked at the "video" tag? It is exactly that simple.
W3C's description of the <video> element states:
A Google search for HTTP 1.1 progressive streaming led to this page, which equates it with seeking in a prerecorded stream using HTTP range requests. But CptLoRes was referring to live streams, not prerecorded streams. The same page also states that not all non-Apple browsers support Apple's HTTP Live Streaming spec.
It stops some autoplays, but many still play.
Sent from my ENIAC