Will CSS3 browser-implementations be removed?

[Shamil]

Right now in the CSS, I am seeing horrible things, such as:



border-radius: 5px; -webkit-border-radius: 5px; -moz-border-radius: 5px; -khtml-border-radius: 5px;


Will they be removed, and standardised to

border-radius: 5px;

soon?

I just like standards and non-proprietory implementations.

 

[Floren]

Right now in the CSS, I am seeing horrible things...
I just like standards and non-proprietory implementations.

I think the current CSS is proper and based on current browser technology. Plus, I'm positive that Kier&Mike will improve their code, while browsers evolve. What is more important: you are focusing on issues that can be addressed very easy by yourself, at admin level. After all, is your choice if you don't want your users to browse your website with a specific browser. The devs provided you a code platform compatible for all popular browsers. There is nothing wrong with that, right?

I've never used Konqueror, so that's acceptable.

I know plenty of people who use Konqueror. Not using specific tags for that browser would put them out of the game. I believe they have the right also to enjoy a pleasant Xen user experience.

 

[Grover]

I am currently eating the people/businesses still using IE 6.

Cannibalism isn't an approach that had occurred to me. What are you doing with all the bones?

They're going to be burned, as further punishment for not upgrading earlier.

This guy is just...

 

[Jeremy]

Right now in the CSS, I am seeing horrible things, such as:



border-radius: 5px; -webkit-border-radius: 5px; -moz-border-radius: 5px; -khtml-border-radius: 5px;


Will they be removed, and standardised to

border-radius: 5px;

soon?

I just like standards and non-proprietory implementations.

Since Kier said it is done via a CSS rendering class, you could in theory create a program that fetches the browser string (I forget the name right now) and checks for what browser and version. If it supports border-radius: 5px, have it display that. If it doesn't support it at all, don't display it, and if it needs a specific one, figure that out (say -webkit-border-radius: 5px; ) and display strictly that.

 

[Disjunto]

Since Kier said it is done via a CSS rendering class, you could in theory create a program that fetches the browser string (I forget the name right now) and checks for what browser and version. If it supports border-radius: 5px, have it display that. If it doesn't support it at all, don't display it, and if it needs a specific one, figure that out (say -webkit-border-radius: 5px; ) and display strictly that.

As Floris said earlier, that probably takes more time than it saves

 

[Jeremy]

As Floris said earlier, that probably takes more time than it saves

I know, I would never do such a thing myself, but if someone really wants to shave it off, it can be done via a modification.

 

[welshstew]

I am currently eating the people/businesses still using IE 6. It's a pie that's not getting any smaller.

You make them into a pie? Taste?

For businesses, some times they have no choice but to stick with an outdated browser due to products they use not working correctly in a modern browser - so they are willing, just unable.

 

[Shamil]

You make them into a pie? Taste?

For businesses, some times they have no choice but to stick with an outdated browser due to products they use not working correctly in a modern browser - so they are willing, just unable.

IF they made products, i.e. intranets and such that worked properly, following modern standards in the first place. Oh well.

 

[welshstew]

IF they made products, i.e. intranets and such that worked properly, following modern standards in the first place. Oh well.

I was talking about legacy systems that businesses are tied into. As I stated, if the businesses had the choice of software, and the time / resources to upgrade they would.

Unfortunately, due to these legacy systems, it makes it too costly to upgrade.

 

[welshstew]

What people don't realise is that we can use the later technologies and support the fallbacks.
Example:
HTML5 video... we can use the video element to display HTML5 video, then we can use the object/embed fallback inside the video tags. Browsers that don't render the video will render the object/embed.

Absolutely, progressive enhancements and graceful degradation = WIN

 

[Enigma]

Since Kier said it is done via a CSS rendering class, you could in theory create a program that fetches the browser string (I forget the name right now) and checks for what browser and version. If it supports border-radius: 5px, have it display that. If it doesn't support it at all, don't display it, and if it needs a specific one, figure that out (say -webkit-border-radius: 5px; ) and display strictly that.

Doable, but overkill IMO.

 

[welshstew]

Since Kier said it is done via a CSS rendering class, you could in theory create a program that fetches the browser string (I forget the name right now) and checks for what browser and version. If it supports border-radius: 5px, have it display that. If it doesn't support it at all, don't display it, and if it needs a specific one, figure that out (say -webkit-border-radius: 5px; ) and display strictly that.

why bother when you can target browsers with the appropriate CSS prefix ??

 

[Jeremy]

Doable, but overkill IMO.

I agree. Some might be crazy enough to think it required.

why bother when you can target browsers with the appropriate CSS prefix ??

Like now. Its just fine the way it is for me.

 

[Floris]

It's not like you see the additional css when you load a page

 

[Shamil]

It's not like you see the additional css when you load a page

I'm obsessed with the little bytes.

 

[Kier]

I'm obsessed with the little bytes.

Why not have a single character username then?

 

[Shamil]

Why not have a single character username then?

Then I'd make posts with 1 character

 

[Erik]

Why not have a single character username then?

Zing!

In all seriousness, I think it's silly that we're discussing a mere dozens of bytes when you could probably save many more in other, less-necessary areas.

 

[Floris]

Why not have a single character username then?

Even better, why not accept these extra bytes, so the web server doesn't have to work three times as hard creating 16 times the amount of bytes, just to remove them for the various types of sessions due with various types of browsers and their versions. Not processing them afterwards saves bytes, saves times, and since it's 8000 cached bytes, on a 25,000+ page site, it's a 10,000 fold of bytes saved by just having 8000 extra bytes. It's just another non-discussion about an interesting topic ct2k7 doesn't know enough about. Interesting question, but has been answered: the answer is no.

 

[Shamil]

In all honestly, I just hate proprietary extensions in CSS/HTML.

 

[Floris]

In all honestly, I just hate proprietary extensions in CSS/HTML.

So it's about you, and not about the general public. I find it an invalid argument to fight this topic any further.