Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Does this mean that webkit and mozilla are going to drop the prefix? What's the point of the prefixes to begin with?


The point is that those things are/were still in "draft" specification and so it's asking for trouble to implement them in a way that will prevent changes to the final spec. I'm sure once the standards are finalized the prefixes will be dropped (or really, deprecated).


Because you get yelled at for doing a blink tag, but it's fine to do a moz-blink tag.

The problem is when browser #2 wants to implement blink. They shouldn't use your prefix, so they now have webkit-blink. And the HTML writer now needs to sniff the browser.

Progress?


These are CSS properties, not HTML elements. There is no need to sniff; you just provide multiple properties.

p.wibble { -moz-blink: slowly; -webkit-blink: 10%; -ie9-blink: "Microsoft.XML.Autocompositor(alpha=99,blinkrate=14692,emulate-old-ie-versions=false,true,true,false)#ie9" }

or whatever. (In practice everyone who provides these properties does so in a very similar manner, so it's easier than the above pseudosnippet suggests.)




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: